The developer's guide to multi-tenant remittance

If you're building a platform that serves multiple operators — an agent network, a marketplace, a franchise model — you need multi-tenancy from day one. Retrofitting it later means untangling shared pricing logic, shared compliance state and shared reporting across customers who should never see each other's data. Here's how we structure it on NESVRA, and what to think about if you're building it yourself.

Start with isolated sub-accounts, not shared tables

Every tenant on NESVRA gets a fully isolated sub-account: its own ledger, its own KYC state, its own transaction history. Nothing is filtered at the query level — it's structurally separated. This matters the day a tenant asks for a full data export, or the day you need to sunset one tenant without touching another's records.

Pricing engines need their own layer

• Each tenant should be able to set its own markup on the base FX rate without touching your core pricing logic
• Fee schedules per delivery method should be configurable per tenant, not hardcoded globally
• Promotional pricing and volume discounts need an override layer that expires cleanly, not a permanent patch

We built our pricing engine as a rules layer that sits on top of the base rate feed. Tenants configure markup rules through the dashboard or API; the underlying rate calculation never changes. This is the difference between a pricing change taking an engineering ticket versus a five-minute dashboard update.

White-label branding without forking your codebase

The temptation with white-label is to let each tenant customize everything, which quickly becomes unmaintainable. We scope customization to a fixed set of tokens — logo, color palette, sender name on receipts, support contact — applied at render time from tenant configuration. The underlying application code is identical across every tenant; only the presentation layer changes. If you're designing this yourself, resist the urge to let branding requests turn into one-off code branches.