Get non-PCI card information

Pismo card ID

Encrypted Primary Account Number (PAN). This field does not exist until the card PCI data is asynchronously created.

Card status enum. Refer to the Card lifecycle and statuses guide for more information and a complete list.

Printed/embossed card name.

Currently, you have 3 ways to populate this field:

1. During account creation via the application.applicant.personal.social_name field.
2. During account creation via the application.applicant.personal.name field when the field in #1 is not set.
3. Passing the printed_name field during card creation, updating a card, or when reissuing a card. This takes priority over #1 and #2.

No letters with accents, numbers, or special characters - only letters (a-z|A-Z) and space, as specified in the <a href="https://emvlab.org/emvtags/show/t5F20/" target="_blank">ISO EMV tag 5F20</a> for cardholder name.

REQUIRED for an UNNUMBERED card (Card created without PIN or PAN that issuer defines at some point in the future.)

Card alias name for a VIRTUAL card.

This field is REQUIRED to be unique for each VIRTUAL card a customer owns.

No matter what is passed for a PLASTIC card, the value is always PLASTIC.

Card type enum:

• PLASTIC - Physical card - plastic or metal.
• VIRTUAL - Digital card with fixed PAN and dynamic CVV.
• TEMPORARY - Virtual card with a fixed PAN and CVV meant for short-term use, typically 24 hours. For more information, refer to Configuring temporary cards in the Cards management guide.
• RECURRING - Virtual card with a fixed PAN and CVV originally meant for use with recurring subscriptions. This type is being DEPRECATED and it is recommended you use VIRTUAL instead.

Bank Identification Number (BIN). A 6 or 8 digit number identitying the card network, issuer, and product.

Card network, i.e., Visa, Mastercard, ELO, RuPay, Private, GPN

Template ID. Templates are used to implement the BIN override feature. For more information, refer to the BIN override guide.

Pismo program ID

Date/time when card was issued in RFC3339 format, i.e., 2019-07-03T17:23:18Z

Optional for virtual cards. Maximum amount allowed per transaction. Set up to the approved limit. If not set, account limit is used.

Card expiration date. RFC 3339 format

Last four Primary Account Number (PAN) digits. This field does not exist until the card PCI data is asynchronously created.

Sequential counter incremented every time card is reissued.

Last issued card ID

Number of times the password was tried

For physical cards. Is card enabled for contactless transactions?

With contactless transactions, you hold or tap the card on contactless-enabled card reader to complete a transaction. This requires that both the card and the terminal have Near Field Communication (NFC) technology. Most embossers can create plastic contactless cards.

Default is true.

This field is DEPRECATED. For more information, refer to the ABU documentation in the Cards overview guide.

When a card is created or reissued, or its account credentials change, Mastercard is notified if this feaure is enabled. Notification updates are sent to Mastercard on a daily basis.

For more information, refer to Mastercard's <a href="https://developer.mastercard.com/product/automatic-billing-updater-abu/" target="_blank">ABU</a> documentation.

For Mastercard - if card is DMC, where the debit has authorization and confirmation at different times, base I and base II, respectively. Unlike Mastercard's Maestro debit, where authorization and confirmation take place at the same time (base I).

Default is false.

For physical cards. Additional information for embossing company. For example: tracking number or whether the card should be plastic or metal.

You can use this field for any embossing needs specific to your business. Whatever is sent must be agreed upon with the embosser—what to send, what values to send, what format to send, what size to send for each value, and so on.

Mode enum: CREDIT - Single credit card DEBIT - Single debit card COMBO - Card has both a credit and debit mode, meaning it is associated with both a credit and debit program and account. MULTIPLE - Combination card created with the DEPRECATED Create combo card endpoint.

For more information, refer to the mode documentation in the Card management guide.

How long, in hours, the card is valid. Cannot exceed the card's expiration_date. Once this period is exceeded, and the card has a NORMAL, BLOCKED, PENDING, WARNING or REISSUED status, its status becomes INOPERATIVE.

This field is used to calculate the datetime value for valid_until.

For VIRTUAL and PLASTIC cards. Setting this field for TEMPORARY or RECURRING cards returns a 400 Bad request error.

Card is valid until this datetime. ISO 8601 format. Once this time is exceeded, and the card has a NORMAL, BLOCKED, PENDING, WARNING or REISSUED status, its status becomes INOPERATIVE. This field's value is calculated using the validity_period_hours.