Collect payments inside your product
A hosted checkout, an embedded iframe or a direct API call. Card and bank transfer in one flow, settling in real time, with a webhook that fires the moment the money arrives.
- Three integration modes
- Real-time settlement
- Sandbox to test
Free to start · No monthly fee · Pay per collection
Checkout
Embedded
Pro Plan — Annual
₦250,000
Billed annually · Renews Aug 2027
Hosted by Niimbu · Your branding · Your domain
A payment page you do not have to build
Most platforms spend weeks building and maintaining a payment page, integrating card and transfer separately, and polling for status. Niimbu's Collections API gives you all three in one call.
Three ways to collect
A hosted checkout page you redirect to, an embedded iframe inside your product, or a direct API call for full control. Same infrastructure, same settlement, different levels of integration.
Settles in real time
The moment the customer pays, the webhook fires and the money is in your account. There is no batch window, no T+1 delay and no manual release.
Card and transfer in one flow
The customer chooses between card and bank transfer. Both settle to the same account, both fire the same webhook, both appear in the same ledger.
From API call to settled, in four steps
Create a collection
Set the amount, currency, reference and customer details. One API call returns a checkout URL.
Direct the customer
Redirect to the hosted checkout, embed it as an iframe, or build your own form and post to the API.
Customer pays
Card or bank transfer, whichever the customer prefers. The checkout handles the flow.
Webhook fires
A signed payload arrives at your webhook URL with the payment details, reference and status.
A payment page you do not have to build
Niimbu hosts the checkout page, carries your branding and handles the payment flow. You redirect the customer, they pay, and a webhook tells you it happened.
- Your logo and colours on the page
- Card and bank transfer in one flow
- Mobile-optimised by default
Checkout
Embedded
Pro Plan — Annual
₦250,000
Billed annually · Renews Aug 2027
Hosted by Niimbu · Your branding · Your domain
Know the moment the money arrives
Every significant event — payment received, payment failed, refund processed — is delivered to your webhook URL in real time. Payloads are signed with a secret you control.
- Signed payloads prevent spoofing
- Automatic retry on delivery failure
- Event types cover every lifecycle stage
Webhooks
Event log
collection.success
ORD-2941
payout.settled
VND-001
account.created
cus_4k9f2
card.activated
crd_9m3k7
All delivered · Retry on failure · Signed payloads
What changes when collection is one API call
The usual way
- Building a payment page from scratch
- Integrating multiple providers for card and transfer
- No webhook — polling a status endpoint every 30 seconds
- Test mode that behaves differently from production
- A payment page that looks nothing like your product
With Niimbu
- One API call returns a checkout URL
- Card and bank transfer in one integration
- Real-time webhooks with signed payloads
- Sandbox identical to production
- Your branding, your domain, your product
The collection detail that real integrations need
No add-on modules and no higher tier to unlock the basics. These are part of collections from the first API call.
Hosted checkout
A payment page hosted by Niimbu, carrying your branding, handling the flow.
Embedded checkout
An iframe you place inside your own product, so the customer never leaves your domain.
Direct API
Full control over the payment form. Post to the API and handle the response yourself.
Card payments
Visa, Mastercard and Verve, settled to your Niimbu account.
Bank transfers
NIP transfers to a dedicated account number, settled in real time.
Idempotency keys
Retry a request safely. The same key returns the same result without creating a duplicate.
Test mode
Test cards and test accounts that behave like production, so you can build without moving real money.
Webhooks
Signed, delivered in real time, retried on failure. Every lifecycle event covered.
Multi-currency
Collect in NGN, USD, GBP or EUR, with the exchange rate recorded on the transaction.
Every platform collects differently
The integration mode, the payment methods and the webhook handling change by product. Pick the closest fit.
SaaS platforms
Collect subscriptions, one-time payments and upgrades inside your own product, without redirecting to a payment page.
Marketplaces
Collect from buyers at checkout, with the reference tied to the order and the seller.
Fintech platforms
Fund wallets, collect loan repayments and process top-ups, all through the same API.
Education platforms
Collect tuition, exam fees and deposits, with the student and term attached to the reference.
Events and ticketing
Sell tickets and collect event fees, with the order reference tied to the attendee.
Collections API
See how Niimbu compares with building on raw bank APIs or integrating multiple payment providers.
Payments inside your product should work the same way whether they come from a card or a transfer.
Per collection, not per call
There is no monthly platform fee. You pay a percentage per successful collection, with lower rates at higher volume. The sandbox is free.
- No monthly platform fee
- Lower rates at higher volume
- Sandbox is free
Frequently asked questions
If your question is not here, the Help Centre goes deeper, or you can talk to someone on the team.
What is the difference between hosted, embedded and direct API?
Hosted checkout is a page Niimbu hosts — you redirect the customer. Embedded checkout is an iframe inside your product — the customer never leaves your domain. Direct API gives you full control — you build the form and post to the API. All three use the same infrastructure and settle the same way.
How quickly does the money settle?
Card payments settle instantly to your Niimbu account. Bank transfers settle via NIP, usually within seconds. The webhook fires the moment the payment is confirmed, regardless of the method.
Can I collect in more than one currency?
Yes. The API supports NGN, USD, GBP and EUR. The currency and exchange rate are recorded on the transaction, so your books stay auditable.
How do webhooks work?
When a payment event occurs — success, failure, refund — Niimbu sends a signed payload to your webhook URL. The signature uses HMAC-SHA256 with a secret you control. Failed deliveries are retried automatically with exponential backoff.
Is there a sandbox?
Yes. A sandbox key gives you access to test cards and test accounts. Every scenario — successful payment, declined card, insufficient balance — can be reproduced in sandbox first.
What does collections cost?
There is no monthly platform fee. You pay a percentage per successful collection, with lower rates at higher volume. The sandbox is free.
Can I customise the checkout appearance?
Yes. The hosted checkout supports your logo, brand colours and custom fields. The embedded checkout can be styled with CSS. The direct API gives you full control over the form.
More from Embed
Build on the same rails your customers already trust. Each API shares accounts, ledgers and verification.
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.