One API, three credentials
There is one reference covering everything your integration can call. What differs between operations is whose authority the call carries — and every operation says which it takes, at the top of its own page.
Your backend, acting as your company
Register customers, open wallets, post transactions, read the ledger, create top-up links.
Your app, acting for one person
Everything under /me — top-ups, withdrawals, payout accounts, notifications. A machine token is rejected.
Both, with different scope
Wallet and transaction reads, transfers. Each says on its own page what changes with the caller.
What is built, and what is not
We would rather you read this here than discover it in an error response. Anything partial says so on its own reference page, on the exact field that behaves differently.
The integration, in order
Each chapter ends where the next begins, and states what is observably true once you finish it — because that is what your tests will assert.