Skip to main content
Issue and manage virtual USD cards for your customers — usable for online purchases and subscriptions anywhere the card network is accepted. You integrate one Numero card API — Numero handles issuing for you.
Full reference: every card endpoint, request, and response is in the API Reference (tags Cards and Cardholders). This page is the orientation.

Card types

We issue two types of USD virtual card. You choose at issue time with the capability field — the issuer is selected for you.
TypecapabilityUse for
Plain USD virtual cardomit, or USDOnline purchases, subscriptions, ad spend.
Wallet-enabled USD card (Apple Pay / Google Pay)APPLE_PAY or GOOGLE_PAYCards your cardholder can add to Apple Wallet / Google Wallet.
Discover which products and capabilities are available to your business with GET /business/card/products (don’t hardcode product codes). The card you get back echoes its capabilities, so you can confirm the type you issued.
Wallet-enabled means the card is eligible to be added to Apple/Google Wallet (the cardholder adds it with the card details). In-app push-provisioning (“Add to Apple Wallet” button) is a separate flow we don’t expose yet.

Two ways to use it

  1. Issue directlyPOST /business/card/issue with the cardholder’s KYC inline. Numero creates (or reuses) the cardholder for you and mints the card.
  2. Customer-first (BaaS) — create a cardholder once (POST /business/cardholders), then issue one or more cards to them (POST /business/cardholders/{customerId}/cards). Best when you manage many end-customers; each cardholder has their own profile, cards, and statement.

Base URL & auth

Card endpoints are part of the standard business API — same base URL and API key as every other /business/* endpoint (there is no separate cards host):
EnvironmentBase URL
Sandboxhttps://api-dev.usenumero.com/numeroaccount/api/v1
Productionhttps://api.usenumero.com/numeroaccount/api/v1
Authenticate with your X-Numero-Api-Key header (same as Balance, Transfers, VAS, etc.). Card endpoints are not signature-gated.

Prerequisites (fund-first + entitlement)

  1. Entitlement — your business must be approved for the card product. Request it in Dashboard → Cards (or it’s provisioned for you); an approved entitlement opens your USD card wallet.
  2. Fund the USD card wallet — card issuance and top-ups debit this wallet (fund-first). Fund it from your dashboard (convert NGN→USD into the card wallet).
If you’re not approved, issue calls return approval_required.

Endpoints

MethodEndpointDescription
GET/business/card/productsList available products + capabilities + entitlement
POST/business/card/issueIssue a card (KYC inline)
GET/business/cardList your cards
GET/business/card/{reference}Get a card (masked)
POST/business/card/{reference}/topupFund a card
POST/business/card/{reference}/withdrawWithdraw from a card
POST/business/card/{reference}/freezeFreeze a card
POST/business/card/{reference}/unfreezeUnfreeze a card
POST/business/card/{reference}/limitsSet daily / per-transaction limits
POST/business/card/{reference}/revealReveal full PAN/CVV (sensitive)
GET/business/card/{reference}/transactionsCard statement
POST/business/cardholdersCreate a cardholder
GET/business/cardholdersList cardholders
GET/business/cardholders/{customerId}Get a cardholder
GET/business/cardholders/{customerId}/cardsA cardholder’s cards
POST/business/cardholders/{customerId}/cardsIssue a card to a cardholder
GET/business/cardholders/{customerId}/transactionsCardholder statement

Balances are mirrored

Cards are prefunded. Numero mirrors each card’s balance from issuer webhooks and shows you our own number (balance on CardView) — never the issuer’s raw figure. Spend, settlement, refund, reversal, cross-border and decline events all update the mirror; a reconcile job corrects any drift.

Statuses

PendingActiveFrozen (reversible) / Terminated (final). Three consecutive insufficient-balance declines auto-terminate a card (configurable in Watchtower).

Reveal is sensitive

/reveal returns the full PAN, CVV, and expiry, fetched live from the issuer — Numero never stores the full PAN. Only call it from a PCI-aware context, and never log it.

Statements & billing

  • Card statement (/{reference}/transactions) = per-card spend (settlement, refund, cross-border…).
  • USD card-wallet statement (your wallet transactions: funding, top-ups, fees) is separate.
  • A monthly card invoice aggregates recoverable processing costs and is auto-debited from your USD card wallet (a deficit is carried if underfunded). View invoices in Dashboard → Cards → Invoices.

Chargebacks

Lodge a chargeback against a card transaction from the Dashboard (Cards → card → Dispute), not via the API. Numero files it with the card network; a chargeback fee applies.