One statement per account
Money in and money out, in order, with the status of each entry.
Sandbox on request
Every payment, collection, direct debit and bill on an account, with the balance beside it. The successful entries always add up to that balance.
WHAT YOU GET
Money in and money out, in order, with the status of each entry.
Successful entries add up to the balance, and our own tests check exactly that.
Your ledger shows only your accounts. Another organisation's data is never visible.
IN CODE
Ask for one account. You get its balance and every entry, newest first.
GET /api/v1/ledger?account_id=7c9e6679-7425-40de-944b-e07fc1f90ae7
Authorization: Bearer wk_test_... {
"account_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
"balance_kobo": 30000000,
"entries": [
{
"type": "collection",
"direction": "credit",
"amount_kobo": 45000000,
"status": "success"
},
{
"type": "pay",
"direction": "debit",
"amount_kobo": 15000000,
"status": "success"
}
]
} HOW IT WORKS
Pass the id of any account your organisation owns.
Payments, collections, direct debits and bills, each with a direction and status.
Add up the successful entries. They equal the balance.
WHO BUILDS WITH IT
Show customers a clear history inside your app.
Match your own records to ours, entry by entry.
Answer a customer's question about any movement.
QUESTIONS
Not yet. Developers build against the sandbox, which uses simulated customers and money. Live access opens after regulatory approval and a banking partnership are in place.
Tell us what you are building. We issue a test key for your organisation, and you can start calling the sandbox straight away.
Payments out, payments in, collections, direct debits and bill payments, each with its status.
No. Every request is scoped to your organisation. Another organisation's accounts, payments and events are never visible to you.
KEEP EXPLORING
Money APIs are available in the sandbox on request. Live access depends on regulatory approval and a banking partnership.