Issuing a Card
UsePOST /cards to generate a new card. You must supply an active funding account (debitAccountId) and the cardHolderId representing the legal owner.
amount, the system will attempt to deduct funds from the associated debit account and provision the available spend limit in a single step.
Funding an Existing Card
If you didn’t fund the card fully on issuance or are running a prepaid continuous funding model, you can explicitly move money into the card balance usingPOST /cards/{cardId}/fund.
Secure Reveal (Tokenization)
Sensitive Primary Account Numbers (PAN) and CVVs are heavily restricted. To display full card numbers to users without taking on immense PCI compliance scope, you must utilize our vault tokens.- Generate Token: Request a short-lived provider token using
POST /cards/{cardId}/token. - Reveal Details: Have your client application pass the generated token via
GET /cards/{cardId}/reveal?token=....
pan, cvv, expiryMonth, and expiryYear, suitable for final rendering.
Managing Lifecycle Changes
Over the life of a card, you can pause, terminate, or modify behavior.- State Transitions: Use
PUT /cards/{cardId}to update the status toactiveorinactive. You can also enforce specific spending controls using this endpoint. - Permanent Deletion: Use
DELETE /cards/{cardId}to terminate the card and effectively purge it. Note that a closed card cannot be re-opened.