A cross-border payments platform pays out in local currency
One funded USD account, converted on demand, paid out to banks and mobile wallets in local currency across its markets.
The chain, in order.
Every call below exists and is documented. Take any line to the reference and check it. That is the point of publishing a scenario rather than a testimonial.
- Create and verify the senderPOST /v1/customers, then POST /v1/customers/kyc/start.
- Open the operating accountPOST /v1/accounts. USD, wallet-backed, with virtual account details for funding.
- Save each payout recipientPOST /v1/external-accounts, typed bank_account or mobile_money.
- Take the ratePOST /v1/fx/quote, then convert on the spot or place an order.
- SendPOST /v1/transfer. The recipient type decides the rail.
- ReconcileSigned events per state change, carrying the operator’s own reference back.
What it assembles.
Fintechs and payment companies · Africa. Three product lines, one customer record, one integration.
Product lines
- Accounts
- FX and Trade Desk
- Payments and payouts
What this is, and what it is not.
Worth stating twice on a page like this, because the convention in this category is to imply the opposite.
This is an illustrative scenario, not a customer story.
No company is named because none has approved being named, and no outcome figure appears because none has been confirmed. What is real is the chain: every endpoint above is documented, and they are in the order an integration would call them.
When a customer approves a named story with a figure behind it, it will replace one of these and it will say so.
The other scenarios.
One per segment. Each one is a different set of lines against the same platform.