1
0 Comments

Billing felt like the part of the architecture we had figured out.

The hard problem wasn't rate cards or VAT rules. It was figuring out which tenant a Mollie webhook belonged to. One endpoint, no tenant ID in the payload — and the naive fix becomes an O(n) scan on every payment event.

The actual fix required one piece of metadata added at subscription creation, not at the webhook handler. Full writeup here — including what we got wrong first and why GDPR erasure constraints shaped the entire data model: https://dev.to/cadensa/how-we-handle-multi-tenant-billing-for-eu-agencies-cpd

Whether that tradeoff is right for every multi-tenant SaaS is a separate question. For a GDPR-first product, it turned out to be the only one that works.

on July 6, 2026
Trending on Indie Hackers
The hardest part isn't building anymore User Avatar 108 comments I sold $6,773 in 2 weeks, with almost no existing community. User Avatar 60 comments The feature you're most sure about is the one you should question first User Avatar 52 comments I let 3 LLMs argue on the famous AI "Car wash: Walk or Drive" problem to prove a point. User Avatar 44 comments Before you build another feature, use this workflow User Avatar 44 comments I spent months chasing clients who already had a webmaster. So I built something that only finds the ones who don't. User Avatar 33 comments