Card Issuance Flows
Introduction
FinCard Virtual is a card-issuing service built on the FinCard platform. It enables tenants to programmatically issue, manage, and monitor prepaid cards — virtual or physical — for their end customers (B2B or B2C). All endpoints are available for interactive testing athttps://sandbox.finhub.cloud. Each endpoint page includes a Try It panel where you can send live requests against the sandbox.
Architecture Overview
Prerequisites
Before issuing any card, ensure:- Tenant credentials — valid
X-Tenant-IDheader on every request - Account funded — the tenant’s WALLET account has sufficient balance
- Card BINs available — call
POST /card/v2/cardTypesto discover available BINs and their requirements - Cardholder created (if
needCardHolder: trueon the BIN) — cardholder must reachstatus: pass_auditbefore a card can be linked
All API bodies are raw JSON strings (
Content-Type: application/json). The BFF forwards them directly to FinCard Virtual after signature verification.Choose Your Card Type
Common Headers
Every request requires:Four card issuance processes, each with a distinct flow. All share the same API endpoints but differ in required steps and configuration.
1. Virtual Card (PREPAID_CARD)
The standard flow for issuing virtual prepaid cards.Monitor cardholder approval via Cardholder List or Webhooks. Proceed to card creation only when
status=pass_audit.2. Physical Card
Physical cards are purchased offline in bulk, then assigned and activated via API.3. Shared Card (BUDGET_CARD)
Multiple cards share the same wallet. Deposit = allocate credit limit, Withdraw = reduce credit limit.- Deposit on a shared card = allocating credit from the shared pool
- Withdraw on a shared card = reducing the credit limit
- All cards share the same underlying MARGIN account balance