Concepts
The behaviour no single endpoint owns: settlement, money, quotes, idempotency, attribution and limits.
These pages describe behaviour that no single endpoint owns. The first two are the ones that cause a rewrite when they are discovered late.
Asynchronous settlement
An order settles after the call that created it. Read this before you design anything.
Money
Decimal strings on the wire, integer minor units underneath. Getting this wrong loses money quietly.
Balances
What you hold with us, how fresh the figure is, and why it is not a spending check.
Quotes
A locked rate, single-use and short-lived.
Fees
Where the price lives, and why there is no fee field to reconcile. Mechanics, never numbers.
Idempotency and references
What makes a retry safe, on both order creation and webhook handling.
References and attribution
Which identifier attributes a payment to an order, and why.
Caps and limits
Request rate, order ceilings, and the 429 contract.
Products and scopes
Why an endpoint in the reference answers 403 for your credential.
Who does what
Which obligations are yours and which are ours.
Rails
Every rail in the corridor, what the API reaches today, and what each one does to your reference.
Collect in the US, pay out in Kenya
End to end: take USD from US contributors by ACH, FedNow or wire, then convert and pay out KES to M-PESA, a bank account or PesaLink.
Asynchronous settlement
Orders settle after the call that creates them. Model an order that is neither complete nor failed, and let a webhook tell you when it is.