Create a new card
Creates a new virtual or physical card for a user. User must have approved application; account must be active. The phone number used for OTP verification is taken from the user record; the card is issued against the user’s verified identity.
Authorizations
API key as Bearer token
Headers
API version (YYYY-MM-DD)
2025-02-14 "2025-02-14"
Unique key for safely retrying this request. Up to 255 characters; we recommend a UUIDv4. The first request executes and its response is cached; subsequent requests with the same key replay the cached response (24h retention).
1 - 255Unique key for safely retrying this request. Up to 255 characters; we recommend a UUIDv4. The first request executes and its response is cached; subsequent requests with the same key replay the cached response (24h retention).
1 - 255Body
Request body for creating a new card
ID of the user to create the card for
ID of the account to link the card to
Card type (VIRTUAL or PHYSICAL)
VIRTUAL, PHYSICAL "VIRTUAL"
3DS challenge verification method. Defaults to SMS if not specified.
SMS, WEBHOOK "SMS"
Response
Card resource
Unique card identifier
ID of the account the card belongs to
ID of the user the card belongs to
Card type (VIRTUAL or PHYSICAL)
VIRTUAL, PHYSICAL "VIRTUAL"
Current card status
ACTIVE, FROZEN, BLOCKED, EXPIRED "ACTIVE"
Block reason details (only present when status is BLOCKED)
Cardholder name displayed on card
Last 4 digits of the card number. Use reveal endpoint for full details.
3DS challenge verification method
SMS, WEBHOOK "SMS"
Physical lifecycle of the card (production + shipping + activation rollup). Defaults to NOT_ORDERED for newly created physical cards. null for virtual cards, which have no physical lifecycle.
NOT_ORDERED, REQUESTED, IN_PRODUCTION, PRODUCTION_COMPLETED, IN_TRANSIT, OUT_FOR_DELIVERY, DELIVERED, ACTIVATED, CANCELED, DELIVERY_FAILED, EXCEPTION "NOT_ORDERED"
ISO 8601 timestamp of creation
ISO 8601 timestamp of last update