📄 Guide
The balance is both the precondition for spending and the real-time authorization gate. This page covers two things: reading balances (balance), and moving funds between the company pool and dedicated-balance cards (transfer + transfer-query).
The funding model in one sentence: SHARED cards hold no balance and spend straight from the company pool; DEDICATED cards hold their own balance and stop when it runs out. Who holds the balance and who can be a transfer endpoint is in Holders and the funding model; how money comes in is in Deposits.
Query balances
GET /open-api-corp/fund/v1/balance returns a funding owner’s balances per currency.
Request parameters
Response data carries
subjectType, subjectId and the per-currency list balances, one element per currency:
Request example
The balance acts as the real-time authorization gate: a SHARED card spends straight from the company pool, a DEDICATED card from its own balance, stopping when it runs out. The authorization flow is in Authorization and 3DS.
Transfer funds
POST /open-api-corp/fund/v1/transfer moves funds between the company pool and dedicated-balance cards — same currency, no FX, closed loop within one company: COMPANY→CARD funds a card (allocates budget), CARD→COMPANY sweeps the balance back.
Request parameters
Response data
Request example
Query a transfer result
GET /open-api-corp/fund/v1/transfer-query returns the final result of one transfer, looked up by transferRef.
Request parameters
Response data
Request example
Next steps
- Fund the company pool or a dedicated-balance card: Deposits
- How transfers and spending land on statements and in the records (internal allocations count into
totalDebitAmount): Statements and Transactions

