How a conversion works
Nine steps, each of which produces a record you can read afterwards.
1. Instruction
Your treasury team or your systems instruct a conversion: an amount in cedis, an approved asset and network, and an approved destination. No price is sent, because price is an output.
2. Compliance
Screening and monitoring run before any value moves. A provider that cannot be reached produces an indeterminate result, which holds the transaction. Nothing clears because a check failed to run.
3. Liquidity
We ask every eligible venue to quote. All responses are retained, including declines with their reason and latency, which is the evidence behind the routing decision.
4. Quote
You see the venue's rate, the destination amount, each fee component and an expiry. The quote's pricing is frozen at the database level and cannot be edited afterwards.
5. Acceptance
Nothing is committed until you accept. Expiry is checked at the moment of acceptance, under a lock, so a quote cannot lapse between the check and the execution.
6. Execution
The venue fills. You receive the actual fill, not the quote. A fill below the agreed floor fails the conversion and releases your funds rather than delivering less.
7. Settlement
The venue delivers directly to your approved address and returns the transaction hash. We hold no key and cannot redirect or recall a transfer.
8. Confirmation
We follow the transfer to the confirmation depth agreed for that network. A reorganisation that removes a confirmed transfer raises an exception rather than being ignored.
9. Reconciliation
Our records against the venue against the chain. A difference raises an exception carrying its evidence, and is corrected by a compensating entry rather than by editing history.
For your integration team
- Idempotent instructions. A retry with the same key returns the original result rather than acting twice, which is what makes a timeout safe.
- Signed webhooks with a delivery log, so a missed event is visible rather than silent.
- An execution record per conversion: what was instructed, quoted, filled, charged and delivered, with the chain transaction.
- An execution whose outcome we cannot determine is reported as unknown. It is never retried automatically, and never reported as complete or failed.
Sign in to read the full API reference, which is generated from the platform itself.