crypto_card capability is active. You fund it
with crypto and manage it through the API.
Before you start
- Authenticate as an integrator and act on behalf of a verified user. See Authentication and Onboarding.
- Confirm the user’s
crypto_cardcapability isactive. Cards are provisioned automatically once it is, so there’s no create call (see capabilities).
Find the user’s card
status is active, frozen, not_activated, or cancelled, and
its type is physical or virtual. Note that the values you send to change a card’s
state are slightly different (active, locked, canceled); see
Manage the card below.
Fund the card
Load a card with crypto through the same quote-based flow as an off-ramp, with the card as the destination and thecard_deposit rail:
Manage the card
Freeze, unfreeze, or cancel
Freeze, unfreeze, or cancel
locked to freeze a card and active to unfreeze it. canceled is permanent.Set a spend limit
Set a spend limit
interval is daily, weekly, monthly, yearly, all_time, or
per_transaction.List transactions
List transactions
PIN and card details
PIN and card details
Card PINs and full card details are handled with end-to-end encryption so sensitive
data never touches your servers: set a PIN with
POST /v1/cards/{cardId}/update_pin,
retrieve the encrypted PIN with POST /v1/cards/{cardId}/pin, and render the full
number and CVV using the card’s renderSecret with Spritz’s secure card-rendering
component.Related
Off-ramp
The quote-and-settle flow card funding builds on.
Onboarding
Activate the crypto_card capability for a user.