Skip to main content
A card spends from an entity account. You issue it through the API and manage it with a small set of lifecycle actions. Card details such as the number and CVV are read through Get card details, so treat that response as sensitive.

​
Choose a card type

See Card issuing for a request for each type.

​
Lifecycle

​
Rules that affect your integration

  • A fee applies to each card. Creating a card debits a creation fee from the funding account, in the card’s currency. If the account can’t cover it, the request fails with 400 error_card_creation_fee_required. Check the fee first with GET /card-creation-fee/{account_id}.
  • Creation is not idempotent. Sending the same create request twice issues two cards and charges two fees. Don’t retry a request that may have succeeded; list the account’s cards first.
  • The funding account must match the card currency. A card in a different currency returns 400 error_operation_invalid_for_state.
  • Spending uses the account balance. The card’s amount field is a placeholder, not a limit. What the card can spend is the available balance on its account.
  • Reassigning across currencies works. FX conversion is applied at the prevailing rate as the card is used, so no extra step is needed.

​
Next steps