---
title: "Get cards for customer and account"
method: GET
path: "/wallet/v1/customers/{customerId}/accounts/{accountId}/cards"
tags: ["Cards"]
---

# Get cards for customer and account

`GET /wallet/v1/customers/{customerId}/accounts/{accountId}/cards`

## Request

- Base URL: `https://sandbox.pismolabs.io`
- URL: `https://sandbox.pismolabs.io/wallet/v1/customers/{customerId}/accounts/{accountId}/cards`
- Auth: HTTP bearer

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.

## Path parameters

- `customerId` string, required
- `accountId` integer, required

## Query parameters

- `page` string
- `perPage` string
- `format` 'paged'
- `status` string[]
- `modes` string[]
- `types` string[]

## Response `200`

CardInfoResponse object array

- CardInfoResponse[]
  - `id` integer: Pismo card ID
  - `hash` string: Encrypted Primary Account Number (PAN). This field does not exist until the card PCI data is asynchronously created.
  - `status` string: Card status enum. Refer to the [Card lifecycle and statuses](doc:card-lifecycle-and-statuses) guide for more information and a complete list.
  - `printed_name` string: 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.)
  - `name` string: 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 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](https://developers.pismo.io/pismo-docs/docs/cards-overview-1#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.
  - `bin` string: Bank Identification Number (BIN). A 6 or 8 digit number identitying the card network, issuer, and product.
  - `brand` string: Card network, i.e., Visa, Mastercard, ELO, RuPay, Private, GPN
  - `template_id` string: Template ID. Templates are used to implement the BIN override feature. For more information, refer to the [BIN override](doc:bin-override-feature) guide.
  - `program_id` integer: Pismo program ID
  - `issuing_date` string: Date/time when card was issued in RFC3339 format, i.e., 2019-07-03T17:23:18Z
  - `transaction_limit` string: Optional for virtual cards. Maximum amount allowed per transaction. Set up to the approved limit. If not set, account limit is used.
  - `expiration_date` string: Card expiration date (format = yymm). If passed, the card expiration date is not calculated using the "Card expiration (# of months)" program parameter.
  - `last_4_digits` string: Last four Primary Account Number (PAN) digits. This field does not exist until the card PCI data is asynchronously created.
  - `track_number` integer: Sequential counter incremented every time card is reissued.
  - `reissued_card_id` integer: Last issued card ID
  - `password_tries` integer: Number of times the password was tried
  - `contactless_enabled` boolean: 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_enabled` boolean: This field is **DEPRECATED**. For more information, refer to the [ABU documentation](doc:cards-overview-1#mastercards-automatic-billing-updater-option) 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_debit` boolean: 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_field` string: 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&mdash;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](ref:post-v1-combocard-relationship) endpoint. For more information, refer to the [mode documentation](doc:cards-overview-1#create-a-combination-card-with-card-modes) in the Card management guide.
  - `validity_period_hours` integer: 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_until` string: 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`.
  - `metadata` Metadata: Any key-value object. Max length = 3200 bytes. This **must** be valid JSON data. **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](ref:get-started-with-pismo-apis#metadata).

## Other responses

- `401`: Access token is missing or invalid
- `403`: You don't have permission to access this resource
- `500`: Internal server error

---

[API](https://skmtc.dev/pismo/apis/card-issuing-cards.md) - [All operations](https://skmtc.dev/pismo/apis/card-issuing-cards/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/card-issuing-cards/revisions/05611ac051b0?raw)