One account number per payment.
Create a transaction, show your customer the account number, and get paid the moment the transfer lands. Confirmed by webhook, polling or a live event, and settled to your bank.
How it works
- 1
Create a transaction
Your server sends the amount in kobo and your order reference. You get back a one-time account number reserved for this payment.
- 2
Your customer transfers
Show the account number, bank, account name and exact amount. They pay from any Nigerian bank app; the account name carries your business name.
- 3
The payment is confirmed
The moment the transfer lands you get a signed webhook or a live event, or you read the paid status when you poll.
- 4
Your money is settled
The fee comes off at source and your net amount settles to your verified bank account on a T+0 or T+1 schedule.
Three ways to know the money landed
All three carry the same transaction object. Use webhooks to fulfil orders, the live event to update the checkout page, and polling as a fallback.
One call to create a transaction
Send the amount in kobo, your reference and the customer. The response has everything your checkout needs to show: the account number, the bank, the account name and when it expires. Amounts are integers end to end.
Fees
1.5%
capped at ₦2,000.00 per successful transfer.
No setup fee, no monthly fee, nothing for expired or cancelled transactions. From ₦133,333.34 upwards every transfer costs the capped amount.
Built so money arrives
Payments are recorded in a double-entry ledger, every notification is signed, and every sensitive action leaves a trail.
Current availability is on the status page.
Signed webhooks
Every delivery is signed with HMAC-SHA256 over a timestamp and the raw body. Replays older than five minutes are rejected.
Idempotency keys
Retry a create call with the same Idempotency-Key and you get the original response back. A network blip never makes two accounts.
Two-factor sign-in
Owners and Admins must use two-factor authentication. Secret keys are shown once and stored only as hashes; live keys take IP allowlists.
Encrypted verification files
Business verification documents and sensitive personal fields are encrypted at rest. Traffic is encrypted in transit with TLS.
Append-only ledger
Every payment is booked in a double-entry ledger that is reconciled daily. Nothing is lost, counted twice or settled twice.
Audit log
Key rolls, webhook changes, settings and team changes are written to an audit log you can read in the dashboard.
Start in the sandbox today
Test keys are issued the moment you sign up. Simulate paid, underpaid, overpaid, late and expired transfers, then go live once your business is verified.