Create card on file

Create a card on file - an existing card that has been tokenized and stored in a digital wallet. The token is then used for payment transactions to avoid exposing sensitive data like the card's PAN and CVV.
The card can be a Pismo-issued card or an external card. The card is added to the customer's digital wallet.

This endpoint generates a Card on file created event.

Note: This is a PCI endpoint, use the https://gw-pci.pismolabs.io environment.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
boolean

Skip acquirer and anti-fraud validation? Default is false.

Body Params
string
required

Card alias name. No limit.

string
required

Card Verification Code (CVV) (the three numbers behind the card).

string
required

Card expiration date (mmyy)

string
required

Cardholder printed name. No limit.

string
required
length between 12 and 19

Primary Account Number (PAN) to store. The PAN shown here is a fictional example used for documentation purposes. It does not represent a real card number.

string
length ≤ 50

Acquirer ID.

string

Network card profile identifier or HEX color. A profile or HEX color determines a card's appearance in a mobile payment app or payment system. Issuers are responsible for configuring card profiles with the card network.

string

API-generated card token from registration. This is NOT a field you can change, but it must be passed to identify the card.

boolean

Is this card the default card? Default is false.

string

Cardholder government document number. This can be from any document that identifies the cardholder such as a Tax ID, State ID, or driver's license.

boolean

Is this the issuer's card? Default is false.

boolean

Is card verified? Default is false.

string

Any data object with key/value pairs. No limit on length.

Note: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to Get started with Pismo APIs.

Headers
string
required

Account token - an access token encoded with a Pismo account ID. Tokens can expire quickly, which can result in an Unauthorized message.

Responses

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json