---
title: "Get card details"
method: GET
path: "/issuers/{issuerId}/cards/{cardId}"
tags: ["Register and View"]
---

# Get card details

`GET /issuers/{issuerId}/cards/{cardId}`

This request is used by the issuer backend to request card details.

## Response `200`

Successful get card details

- object
  - `consumerId` string — Unique identifier of the end user.
  - `accountIds` AccountId[] — List of accountIds associated to the card. accountId pattern : `[A-Za-z0-9_-]{1,64}` <br/>**Note**: accountIds is deprecated. This optional response parameter will no more be returned.
  - `cardId` string — Unique identifier of the card.
  - `cardProductId` string — Unique identifier of the type of card (defined during the onboarding of D1)
  - `threeDSsupport` boolean — Determines if the card supports EMV 3-D Secure (3DS) flows.
  - `scheme` 'VISA' | 'MASTERCARD' | 'PAGOBANCOMAT' | 'AMEX' — The card scheme
  - `panSuffix` string — Last 4 digits of the PAN
  - `exp` string — Expiry date of the card in MMYY format
  - `state` 'ACTIVE' | 'INACTIVE' — The state of the card.
  - `creationTime` string — The time the ressource has been created. Format ISO 8601 YYYY-MM-DDThh:mm:ssTZD
  - `lastUpdateTime` string — The time the resource has been last updated. Format ISO 8601 YYYY-MM-DDThh:mm:ssTZD
  - `digitalCards` object[] — List of digital cards associated to the card. **Warning**: this digitalCards list will never be filled if the issuer is not configured with **D1 Tokenization** service.
    - `id` string — Unique identifier of the digital card.
    - `state` 'ACTIVE' | 'INACTIVE' | 'DELETED' | 'DEPLOYMENT_ONGOING' | 'PENDING_ACTIVATION' — The state of the digital card (token) N.B. Tokens in DELETED state are included only if the corresponding issuer onboarding flag (i.e. manageDeletedToken) is set.
    - `recommendation` 'NOT_APPLICABLE' | 'GREEN' | 'YELLOW' | 'ORANGE' | 'RED' — Wallet/Digital Card Requestor colour recommended during the card tokenization request Please note that in certain situations a recommendation might be not provided by the wallet.

## Other responses

- `400` — Bad Request, Invalid request URI or header, or unsupported non-standard parameter
- `401` — The provided Authorization header is missing or invalid
- `403` — Forbidden action, check the state of the linked end user (consumer) or account or digital card
- `404` — Resource not found
- `500` — Internal Server Error

---

[API](https://skmtc.net/thalescloud/apis/d1-oauth-api.md) · [All operations](https://skmtc.net/thalescloud/apis/d1-oauth-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/thalescloud/d1-oauth-api/revisions/96089514858c/schema)