Sign in

v1

latestOpenAPI 3.1.0Copyright Pismo2026-07-247702,7523.1 MB
Cards

Get cards for customer and account

Get cards for specified account and customer with paging and filter options.

Accounts can have multiple customers, typically to accommodate primary and additional cardholders, but only one owner. There can only be one physical card per customer. A customer can have multiple virtual cards, but the card names have to be different.

get/wallet/v1/customers/{customerId}/accounts/{accountId}/cards

Path parameters

customerIdstring required

Customer ID

accountIdinteger required

Pismo account ID

Query parameters

pagestring

Page number. Default is initial page - 0. To navigate between pages, set format=paged.

perPagestring

Cards per page. Default is 10. To navigate between pages, set format=paged.

format'paged'

Set to paged to use paging for results.

statusstring[]

Card status filter:

  • If nothing is passed, cards with status CREATED, NORMAL, and BLOCKED are returned.
  • If ALL is passed, all cards, regardless of status, are returned.
  • If one or more specific statuses are passed, cards with those statuses are returned.

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

modesstring[]

Filter results using card mode.

  • If nothing is passed, all cards are returned.
  • If one or more specific modes are passed, cards with those modes are returned.
typesstring[]

Card type filter:

  • If nothing is passed, all cards are returned.
  • If one or more specific types are passed, cards with those types are returned.

Response

CardInfoResponse object array

idinteger

ID of card to create relationship for

hashstring

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

status'ACTIVE' | 'SUSPENDED' | 'PENDING'

Card status

printed_namestring

Printed name on physical card

namestring

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.

type'PLASTIC' | 'VIRTUAL' | 'RECURRING' | 'TEMPORARY'

Card type

binstring

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

brandstring

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

template_idstring

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

program_idnumber

Pismo program ID.

issuing_datestring

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

transaction_limitstring

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

expiration_datestring

Card expiration date (format = yymm). If passed, the card expiration date is not calculated using the "Card expiration (# of months)" program parameter.

last_4_digitsstring

Last 4 PAN digits

track_numberinteger

Sequential counter incremented every time card is reissued.

reissued_card_idinteger

Last issued card ID

password_triesinteger

Number of times the password was tried

contactless_enabledboolean

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.

abu_enabledboolean

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.

dual_message_debitboolean

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.

embossing_custom_fieldstring

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'CREDIT' | 'DEBIT' | 'COMBO' | 'MULTIPLE'

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.

validity_period_hoursinteger

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.

valid_untilstring

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.

metadatastring

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.

Example response

[
  {
    "id": 6743052,
    "hash": "WEPvOQuZvjfYEd0iBmr43bhWyOsylIsW95ebYrLD89App2iEq9IizP+8w73pxKQ4mI47EdhzYHF9RfXjrBOyug==",
    "status": "ACTIVE",
    "printed_name": "Sarah Toga",
    "name": "Vacation card",
    "type": "PLASTIC",
    "bin": "87634277",
    "brand": "Visa",
    "template_id": "EAFA693A-57B2-4029-97F3-D20D6F06D79B",
    "program_id": 1010,
    "issuing_date": "2019-07-03T17:23:18Z",
    "transaction_limit": "500.00",
    "expiration_date": "2803",
    "last_4_digits": "5684",
    "track_number": 1,
    "reissued_card_id": 123456,
    "password_tries": 1,
    "abu_enabled": true,
    "embossing_custom_field": "Tracking ID = 5859930",
    "mode": "CREDIT",
    "validity_period_hours": 240,
    "valid_until": "2021-07-03T17:23:18Z",
    "metadata": "{ \"key\": \"value\"}"
  }
]