Issue cards from your product
Virtual cards in seconds, physical cards on demand. Every card carries limits, category locks and merchant restrictions enforced at the network level.
- Virtual and physical
- Network-level controls
- Sandbox to test
Free to start · No monthly fee · Pay per card
API
POST /v1/cards
Request
POST /v1/cards
{
"customer_id": "cus_4k9f2",
"type": "virtual",
"spend_limit": 500000,
"categories": ["fuel","transport"]
}
Response
{
"status": "success",
"data": {
"card_id": "crd_9m3k7",
"last4": "4821",
"spend_limit": 500000,
"status": "active"
}
}
Virtual card · Category restrictions applied
200 OK · 95ms
Corporate cards should not take weeks to arrive
Most card issuance involves a bank application, a credit check and a waiting period. Niimbu's Card Issuing API creates a virtual card in one API call.
Issue in seconds
One API call creates a virtual card. Physical cards ship after a separate request. Both carry the limits, restrictions and controls you set at issuance.
Restrictions enforced at the network
Category locks, merchant restrictions and per-transaction limits are enforced by the card network. A card locked to fuel will be declined at a restaurant, regardless of the balance.
Every transaction in real time
A card swipe fires a webhook with the amount, merchant, category and remaining balance. You see it the moment it happens, not when the statement arrives.
From API call to active card, in four steps
Issue the card
POST to /v1/cards with the customer ID, type (virtual or physical), spend limit and any restrictions.
Card is activated
Virtual cards are active immediately. Physical cards activate when they arrive and are registered.
Customer uses the card
The card works at any terminal or online merchant that accepts cards. Restrictions are enforced at the network level.
Webhook fires
Every transaction — and every declined attempt — fires a signed webhook to your URL.
Limits that cannot be exceeded
Set a total limit, a per-transaction limit, category restrictions and merchant restrictions at the moment of issuance. The card network enforces every rule at the point of sale.
- Total and per-transaction limits
- Category and merchant restrictions
- Time window restrictions
API
POST /v1/cards
Request
POST /v1/cards
{
"customer_id": "cus_4k9f2",
"type": "virtual",
"spend_limit": 500000,
"categories": ["fuel","transport"]
}
Response
{
"status": "success",
"data": {
"card_id": "crd_9m3k7",
"last4": "4821",
"spend_limit": 500000,
"status": "active"
}
}
Virtual card · Category restrictions applied
200 OK · 95ms
Know every transaction as it happens
A card swipe, an online purchase, a declined attempt — each one fires a webhook with the full details. Your system can update balances, check budgets and trigger alerts in real time.
- Signed payloads for every event
- Amount, merchant, category and balance
- Automatic retry on delivery failure
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 card issuance is one API call
The usual way
- Ordering corporate cards from a bank, waiting weeks
- No way to enforce spending categories
- End-of-month surprises from unchecked spending
- Personal cards used for business, reimbursed later
- No real-time visibility into card transactions
With Niimbu
- Virtual cards issued in seconds via API
- Category and merchant restrictions enforced at the network
- Every transaction visible the moment it happens
- Cards carry their own limits and rules
- Webhooks deliver transaction details in real time
The card issuing detail that real integrations need
No add-on modules and no higher tier. These are part of card issuing from the first API call.
Virtual cards
Issue instantly for online payments and subscriptions.
Physical cards
Ship to a customer for in-person spending at any terminal.
Spend limits
Total and per-transaction limits enforced at the network.
Category restrictions
Lock cards to fuel, office supplies, transport or any combination.
Merchant restrictions
Allow cards to work only at specific merchants or categories.
Freeze and unfreeze
Disable a card instantly, re-enable with history preserved.
Transaction webhooks
Real-time event delivery for every swipe and online purchase.
Card status control
Active, frozen or cancelled, controlled by your API.
Sandbox
Test cards with test numbers, no real money moved.
Every platform issues cards differently
The card type, the restrictions and the use case change by product. Pick the closest fit.
Fintech platforms
Issue expense cards to your users as a feature of your product, with your branding and your controls.
Marketplaces
Issue cards to sellers for operational expenses, with category locks and spend limits.
SaaS platforms
Offer expense cards as a feature, with per-user limits and real-time transaction feeds.
Logistics platforms
Issue fuel cards to drivers, locked to fuel merchants, with monthly spend limits.
Education platforms
Issue department cards for field trips and supplies, with per-event limits.
Card issuing API
See how Niimbu compares with ordering corporate cards from a bank.
A card that cannot be restricted is a liability, not a tool.
Per card issued, not per transaction
There is no monthly platform fee. You pay per card issued. Transactions, restrictions and webhooks cost nothing extra.
- No monthly platform fee
- No transaction fees
- 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.
How quickly can I issue a virtual card?
One API call. The card details are returned in the response and the card is active immediately. The customer can start using it within seconds.
What is the difference between virtual and physical?
Virtual cards exist in your system and are used for online payments. Physical cards are shipped to a customer and work at any terminal. Both carry the same limits and restrictions.
How do category restrictions work?
You specify allowed categories at issuance. The card network enforces them at the point of sale. A card restricted to fuel will be declined at a restaurant.
Can I change limits after issuance?
Yes. A PATCH request updates the total limit, per-transaction limit or restrictions. The change takes effect immediately.
What events trigger webhooks?
Card activated, transaction approved, transaction declined, card frozen, card unfrozen, card cancelled. Each event includes the full transaction details.
Can I freeze a card?
Yes. A POST request freezes the card instantly. No new transactions will be approved. A separate request unfreezes it.
What does it cost?
There is no monthly platform fee. You pay per card issued, with no charge for transactions, restrictions or webhooks. The sandbox is free.
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.