REST API
Resource-shaped endpoints, cursor pagination, and an idempotency key on every write.
Developers
One REST API over the whole platform, with a sandbox that mirrors production behaviour down to the webhook signatures.
How it works
Predictable resources, idempotent writes and replayable events — so an integration written this year still runs next year.
Resource-shaped endpoints, cursor pagination, and an idempotency key on every write.
A full-fidelity environment with seeded accounts and simulated inbound transfers.
HMAC-signed events, replayable for thirty days from the console.
TypeScript, Python and PHP clients generated from the same OpenAPI spec.
The surface
Four resources cover most integrations. The rest of the spec is filters and reporting.
/v1/accountsIssue a virtual or sub-account/v1/transfersMove money to any Nigerian bank/v1/ledger/entriesRead the double-entry ledger/v1/webhooksRegister a signed event endpointQuestions
Tell us your volumes and we will map the rails to them.