Skip to main content
Cards is available in sandbox only while we finish development. Dakota enables Cards per account. The Cards endpoints are in the API reference, marked Sandbox only. Endpoints, fields, and flows can still change before release.

​
Before you issue

​
Create a card

The response is the card, with status: "pending". last4 can be null until the card is issued; it arrives on a later card.updated. Full request and response: Create a card.
  • spend_limit.amount is in minor units: 250000 is $2,500.00. See Spend limits.
  • nickname is an optional display label, up to 64 characters.
  • external_id is your own reconciliation key. It is not unique.
  • last4 is the only part of the card number the API ever returns. To show the full card, see Secure card data.
Wait for card.updated with status: "active". Until then the card cannot be spent or revealed. Treat pending in your UI as “being issued”, not as an error.

​
Card status

​
Freeze, unfreeze, or close

PATCH /cards/{card_id} with the new status:
Send "active" to unfreeze and "closed" to close. Closing is permanent, so freeze when in doubt. A change applies to the next authorization: it does not release a hold or cancel a purchase that was already approved. A card can be frozen by more than you. freeze_sources lists everything holding the card frozen. manual is a freeze applied through this API, and it is the only one you can lift. Treat any other value, including one you do not recognize, as a freeze you cannot lift. Freezing and closing are refused only for a closed card, or when the customer’s Cards capability is unavailable. Unfreezing can also be refused for these reasons:

​
Rename

A nickname can be replaced, but not removed once set. Nicknames do not have to be unique.

​
Spend limits

A card has at most one spend limit: an interval and an amount in minor units. A card created without spend_limit has no per-card limit: it can spend up to the wallet’s available balance. Set a limit at creation, and replace it with PUT /cards/{card_id}/spend_limit:
  • interval is per_transaction, daily, weekly, monthly, yearly, or lifetime.
  • per_transaction caps each purchase. A purchase exactly at the limit is allowed.
  • daily, weekly, monthly, and yearly are calendar windows that reset at midnight US Eastern Time: every day, every Monday, on the 1st of each month, and on January 1. They count authorized and settled spend in the current window, not a rolling period.
  • lifetime caps everything the card ever spends.
  • The new limit applies from the next purchase. Lowering it below what was already spent in the current window claws nothing back.
  • A limit cannot be removed, only replaced.
  • A limit is not a balance. A card with a $5,000 monthly limit on a wallet holding $200 can spend $200.
  • If Dakota sets a program-wide cap for your account, the lower of the two wins.
  • You can change the limit of a frozen card, but not of a closed one.

​
Read cards