Skip to main content
Spritz cards let your users spend their crypto anywhere cards are accepted. A card is issued automatically once the user’s 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_card capability is active. Cards are provisioned automatically once it is, so there’s no create call (see capabilities).

Find the user’s card

A card’s reported 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 the card_deposit rail:
Fetch the transaction parameters, have the user execute on-chain, and the funds land in their card program balance (see the off-ramp guide for the on-chain steps). The program balance is a shared pool across the user’s cards:

Manage the card

Use locked to freeze a card and active to unfreeze it. canceled is permanent.
interval is daily, weekly, monthly, yearly, all_time, or per_transaction.
Results are cursor-paginated and can be filtered by status and date range.
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.

Off-ramp

The quote-and-settle flow card funding builds on.

Onboarding

Activate the crypto_card capability for a user.