Cards, bank transfers, wallets, and BNPL through one API and one settlement file.
- Methods28
- Markets24
- Settlement Currencies12
Products
Four products writing to one ledger
Accept, pay out, issue, and hold — each product writes balanced entries to the same double-entry ledger, so balances, fees, and FX always reconcile against each other.
Scheduled and on-demand payouts to 40+ countries with maker-checker controls.
- Destination Countries41
- Currencies12
- Cutoff adherence99.98%
Virtual and physical cards with spend controls that write policy into the ledger.
- Issuing Currencies6
- Controlsper-card
- Issuance Timeinstant
Multi-currency balances, mid-market FX, and yield on operating cash.
- Currencies12
- Fx markupfrom 0.45%
- Yield Tiers3
Why one ledger matters
The fees line up with the movements
Products that share a ledger don't need end-of-month stitching. These are the gaps finance teams usually discover between tools.
Balanced by construction
A charge, its fee, its FX conversion, and its payout post as balanced entries. Nothing settles outside the ledger.
One settlement schema
Cards, bank rails, and wallets land in the same file with fees and FX per transaction. Your ERP maps it once.
No manual joins
Dashboard, API, and exports read the same records. There is no reconciliation layer to maintain between products.
See the products against your flows
Bring one processing statement and one payout run. We map both onto the ledger in the demo.