Cards

Issue debit cards, decision authorizations in real time, and reconcile transactions against internal accounts.

You can issue debit cards backed by an internal account, decision authorizations in real time against that account’s balance, and reconcile every pull, clearing, and refund against the same ledger you already use for payouts.

Cards have no PIN set by default. Until a cardholder sets one, they can enter any PIN at a payment terminal, or skip PIN entry if the terminal allows it.

Once a PIN is set, the cardholder must enter the correct PIN for transactions that use PIN verification. Setting a PIN does not require PIN entry for every purchase; transactions that do not request a PIN continue to work without one.

See Card PINs to let cardholders set, change, or unblock a PIN.

Card lifecycle at a glance

A card moves through five states:

State	Meaning
PENDING_KYC	Cardholder has not finished KYC; the card cannot transact yet.
PROCESSING	Card has been requested and is being provisioned with the issuer.
ACTIVE	Card is live and can authorize transactions.
FROZEN	Card is temporarily disabled. New authorizations are declined; in-flight settlements continue.
CLOSED	Card is permanently closed. Terminal, irreversible.

Every transition emits a CARD.STATUS_CHANGE webhook so you can mirror state changes into your application.

What’s covered in this tab

Quickstart

Issue your first card, simulate an authorization, and watch it reconcile against an internal account.

Card management

Issue cards, bind a funding source, freeze, unfreeze, and close.

Transactions & reconciliation

The relationship between authorizations, pulls, clearings, and refunds — and how to surface exceptions.

Sandbox testing

Drive deterministic outcomes with the magic-value suffix tables.

Card design guidelines

Specs, templates, and rules for designing a physical card and its digital wallet art.