📄 Guide
Whether your customers prefer centralised control or budget isolation, you model their accounts and funds on the same set of endpoints. This page explains the two axes that run through every endpoint — the holder and the funding owner — and how the two funding modes differ.Holder vs funding owner
“Who the card is issued to” and “which account the money leaves” are two independent axes.
The mapping between the two is decided by the card profile,
cardProfileId — the platform guarantees that a given profile always draws on the same funding source:
The funding model
Fund first, spend second: the company pool and dedicated-balance cards are each funded by the customer’s bank transfer to their own receiving virtual account (VA), with arrival notified over webhook. A SHARED card holds no balance of its own — spending debits the company pool directly; a DEDICATED card holds its own balance and stops when it runs out. The balance acts as the real-time authorization gate.
Fund transfers run between the company pool and dedicated-balance cards — same currency, no FX, closed loop within one company: allocate (pool → card) to assign budget, sweep back (card → pool) to recover balance. Cards in company pool mode hold no balance.
Next steps
- The application, entity and card state machines: State machines and freezing
- The operating path for deposits, transfers and reconciliation: Funding and reconciliation