Cards

/docs/global/cardsGlobal

Issue virtual or physical cards, control spend, and reveal PAN/CVV securely. Every card has its own wallet — either an isolated balance you fund explicitly, or one that draws from the main company balance, depending on category.

Issue a card

POST/cards

Parameter	Type	Required	Description
currency	string	Required	Settlement currency for the card.
category	string	Required	Card purpose — determines default limits and whether it uses an isolated balance.

Requires KYC on the requesting user. For roles below owner/admin, use POST /cards/request instead — it creates a pending application routed through your approval policy

instead of issuing immediately. Calling it twice for the same slot is idempotent — the existing pending application is returned rather than duplicated.

Fund an isolated-balance card

POST/cards/:id/fund

Parameter	Type	Required	Description
amountMinor	string	Required	Amount to move from the source wallet into the card wallet.
sourceWalletId	string	Required	The company wallet to debit.
note	string	Optional	Optional memo stored on the funding ledger entry.

bash

curl -X POST https://api.binkpay.net/cards/card_9a1c2b/fund \
 -H "Authorization: Bearer sk_test_..." \
 -d '{ "amountMinor": "10000", "sourceWalletId": "wal_4f2e1a" }'

POST /cards/:id/withdraw reverses the transfer, moving funds back from the card wallet to the source wallet. Only valid for isolated-balance cards.

Spend controls & security

PATCH /cards/:id/limit — adjust the spend limit.
PATCH /cards/:id/status — freeze, unfreeze, or close a card.
PATCH /cards/:id/controls — merchant-category and geo controls.
GET /cards/:id/security / GET /cards/:id/intelligence — device trust and risk signals for the card.
POST /cards/:id/reveal/request-otp then POST /cards/:id/reveal — reveal the full PAN/CVV, gated behind a one-time code sent to the cardholder.

PAN/CVV never appear in list responses

GET /cards

GET /cards/:id

Was this page helpful?