Architecture
Each account is a separate ledger. Transfers between accounts happen synchronously — the balance is final as soon as the API call returns. Key properties:- Single currency denomination (USD currently)
- Real-time settlement between parties
Transaction flow
Every debit has a matching credit (double-entry accounting):- Funding — external money enters through payment processors into consumer accounts
- Consumption — usage triggers instant transfers from consumer to merchant accounts
- Settlement — merchants withdraw accumulated balances to external banks
Sub-cent precision
Balances are stored in the smallest possible unit, so you can charge fractions of a cent accurately. Practical implications:- Charge fractions of pennies for token processing
- No rounding errors in high-volume transactions
- Attribute cost exactly, even for tiny units of usage
Payment methods
Accounts decouple payment sources from consumption. You receive funds regardless of how the customer originally paid — credit card, ACH, crypto, or corporate invoicing. This gives you:- Access to payment methods available in each region
- Compliance obligations kept isolated per account
- Reduced PCI scope
- One reconciliation flow for every payment type
Balance management
Account balances enforce hard spending limits. A customer can’t spend more than their account balance, which prevents:- Debt accumulation
- Invoice disputes
- Collection overhead
- Credit risk exposure
Instant settlements
Card and bank transfers usually take days. Account-to-account transfers settle in milliseconds. Benefits:- Cash flow acceleration for merchants
- No accounts receivable management
- No chargeback window on services already consumed
- Real-time revenue recognition
Multi-party transactions
Accounts support complex fund flows beyond simple bilateral transfers:- Revenue splits — automatic distribution to multiple recipients
- Platform fees — percentage deductions during transfers
- Tax withholding — regulatory compliance deductions
- Affiliate commissions — programmatic partner payouts
Fund withdrawal
You withdraw accumulated balances through payout operations: Prerequisites:- Completed KYC verification
- Linked external bank account
- Minimum balance thresholds
- Batch aggregation for efficiency
- Bank network timing dependencies (1–3 business days)
- Audit trail generation
Future enhancements
Multi-currency support — local currency accounts eliminating FX friction Hierarchical accounts — team budgets and departmental allocations Programmable controls — spending policies and automated rebalancing Interest accrual — yield generation on idle balancesTechnical integration
You don’t need to manage account transfers directly. Sending usage events triggers the correct fund movements automatically.Next steps
- Pricing Overview — structure your billing model
- Usage Events — trigger account transfers