Name before payment
Show your customer the account name and let them confirm it before they pay.
Sandbox on request
Look up the name on an account number before you send a payment, so money reaches the person you meant.
WHAT YOU GET
Show your customer the account name and let them confirm it before they pay.
Most misdirected payments start with a mistyped digit. A name check catches it first.
Verify, then Pay, then read the outcome. The same key covers all three.
IN CODE
Send the account number and bank code. You get the name on the account back.
GET /api/v1/verify?account_number=0123456789&bank_code=058
Authorization: Bearer wk_test_... {
"account_number": "0123456789",
"account_name": "Ada Okafor Savings"
}
No match, 404:
{
"error": {
"code": "account_not_found",
"message": "No sandbox account with that account number.",
"requestId": "5f0c2b1e-8d4a-4c1f-9a77-3b2e6d90c4a1"
}
} HOW IT WORKS
Pass the account number and the bank code your customer chose.
Put the name on screen and ask your customer to confirm it.
Only send the payment once the name is right.
WHO BUILDS WITH IT
Show the name before a customer sends money.
Check each employee's account when you add them.
Confirm a seller's payout account before the first sale.
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.
You get a 404 with the code account_not_found. Ask your customer to check the number and the bank.
Every error has the same shape: a code, a message and a request id. Quote the request id when you contact us.
KEEP EXPLORING
Money APIs are available in the sandbox on request. Live access depends on regulatory approval and a banking partnership.