Create card
Create a card
Authorizations
Authentication from public API requests
Body
Specify the type of card you'd like to create. At the moment, only virtual cards are supported.
virtual
The ID of the account to create the card under. You can get this by calling GET /account
. This field is required unless you are authenticating via API key, in which case it will default to your first commercial account. We recommend supplying this even if you are authenticating via API key.
The ID of the virtual account to create the card under. Virtual accounts can be retrieved by calling GET /virtual-account
.
A constraint that can be applied to a CardGroupSpendingRule
Defaults to false. When set to true, the card will be automatically closed after a single authorization attempt. Note that the card will be closed even if the authorization declines or drops
Arbitrary information that can be attached to the card. This should be a JSON object and cannot exceed 4kb.
Response
The account that this card is associated with
The last 4 digits of the card number
The name assigned to the card that appears on the user dashboard
The month the card expires formatted as MM (01, 02, ..., 12)
The year the card expires formatted as YYYY (2024, 2025, ...)
The status of the card
active
, paused
, inactive
, closed
When true, a physical card has been issued. Otherwise, this is a virtual card.
The virtual account that this card is associated with
When true, the card will be automatically closed after a single authorization attempt. Note that the card will be closed even if the authorization declines or drops
This field contains the full PAN which will only be sent on a request for a single card when you set the query param "include_pan" to "true"
This field will contain full CVV which will only be sent on a request for a single card when you set the query param "include_pan" to "true"
The card group the card belongs to.
The spending constraint applied to the card
The avs address locked applied to this card
Arbitrary information that can be attached to the card. See the PATCH /card/{cardId}
endpoint for more details on how to add user data.