Embed

The same rails, available as APIs

Build payments into your product with REST APIs. Collections, payouts, accounts, cards, identity and bills — same infrastructure, same behaviour, one integration.

  • Sandbox to test
  • SDKs available
  • Pay per call

Free to start · No monthly fee · Pay per API call

API

POST /v1/collections

Request

curl -X POST https://api.niimbu.com/v1/collections

-H "Authorization: Bearer sk_..."

-H "Content-Type: application/json"

-d '{

"amount": 50000,

"currency": "NGN",

"customer_email": "[email protected]"

"reference": "ORD-2941"

}'

Response

{

"status": "success",

"data": {

"reference": "ORD-2941",

"amount": 50000,

"checkout_url":

"https://pay.niimbu.com/...",

"status": "pending"

}

}

Sandbox mode · No real money moved

200 OK · 42ms

Why it matters

Payments inside your product, not beside it

Most platforms bolt payments on as a redirect to a third-party page. Niimbu's APIs let you collect, disburse, issue and verify inside your own product, on the same rails the dashboard uses.

One integration, every capability

Collections, payouts, accounts, cards, identity and bills share the same API design, the same authentication and the same webhook format. Learn one, use all.

Same rails as the dashboard

Every API call moves through the same NIP, NIBSS and card network infrastructure as the Niimbu dashboard. There is no separate integration path with different behaviour.

Built for your product

White-label the checkout, issue accounts in your customer's name, cards with your branding. The API is designed to disappear inside your product, not to carry ours.

How it works

From sandbox to live, in four steps

There is no integration project and no minimum volume. The longest part is building the checkout or the disbursement flow in your own product.

01

Get your keys

Sign up, verify the business and generate a sandbox key. The sandbox behaves like production with test data, so you can build without moving real money.

02

Integrate the APIs

REST endpoints, JSON payloads, standard HTTP. SDKs for Node, Python, PHP and Go. Copy a cURL command and paste it into your terminal to see it work.

03

Test in sandbox

Test cards, test accounts, test billers. Every scenario you need to handle in production can be reproduced in sandbox first.

04

Go live

Switch the key from test to live. Same API, same behaviour, real money. Webhooks deliver events in real time, signed with a secret you control.

< 150ms

Typical API response time

99.98%

API uptime

6

APIs, one integration

₦0

To start testing

Checkout

Collect payments without building a payment page

A hosted checkout page that carries your branding, supports card and transfer, and settles to your account. Embed it as an iframe, redirect to it, or call the API directly for full control.

  • Hosted checkout with your branding
  • Card and bank transfer in one flow
  • Webhook confirms payment in real time
See collections
Developer integrating Niimbu checkout into a product
Identity

Verify a customer before the account is opened

A BVN check confirms the name, date of birth and phone number against NIBSS records. A CAC check confirms the business exists. Both happen in under a second, so the customer never waits.

  • BVN, NIN and CAC verification
  • Name and DOB match in real time
  • Photo returned for visual confirmation
See identity verification
User completing identity verification on a mobile device
CTO reviewing API integration dashboard
The idea behind it

The best payment experience is the one your user never notices.

Pricing

Priced per transaction, not per seat

Opening an account is free and there is no monthly platform fee. You are charged when money moves, so a quiet month costs you nothing. Add as many staff as the business needs.

  • Free to open, no setup fee
  • No charge for extra users
  • Volume rates for higher throughput
See pricing
Questions

Frequently asked questions

If your question is not here, the Help Centre goes deeper, or you can talk to someone on the team.

What does Embed include?

Six APIs on one platform: collections (payments), payouts (disbursements), account issuing (dedicated accounts), card issuing (virtual and physical cards), identity verification (BVN, NIN, CAC) and bill payments. They share the same authentication, webhook format and dashboard.

Do I need to integrate all six APIs?

No. Most developers start with collections or payouts and add the others as their product grows. Each API works independently, and there is no minimum number of APIs you must use.

Is there a sandbox for testing?

Yes. A sandbox key gives you access to test accounts, test cards and test billers. Every scenario you need to handle in production can be reproduced in sandbox first, without moving real money.

How quickly can I go live?

Most teams integrate collections or payouts in a few days. The sandbox behaves like production, so the switch from test to live is a key change, not a code change.

What SDKs are available?

Official SDKs for Node.js, Python, PHP and Go. The API is standard REST with JSON payloads, so any language that can make HTTP requests can integrate directly.

How do webhooks work?

Every significant event — payment received, payout settled, account created, card activated — is delivered to your webhook URL in real time. Payloads are signed with a secret you control, and failed deliveries are retried automatically.

What does it cost?

There is no monthly platform fee. You pay per API call — per collection, per payout, per account issued, per card issued, per verification, per bill payment. The sandbox is free.

The simpler way to scale your business!

Start free and see it working today, or talk to us about pricing for teams and higher volumes.