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

# Get card details

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

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

## Response `200`

Successful get card details

- object
  - `consumerId` string, required — Unique identifier of the end user.
  - `cardId` string, required — Unique identifier of the card.
  - `newCardId` string — Unique identifier of the new card. Provided in case the card is in REPLACED state.
  - `cardProductId` string, required — 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` 'MASTERCARD' | 'VISA' | 'AMEX', required — The card scheme
  - `auxiliaryScheme` 'DANKORT' — The card auxiliary scheme
  - `panSuffix` string, required — Last 4 digits of the PAN
  - `exp` string, required — Expiry date of the card in MMYY format
  - `newExp` string — New Expiry date of the card in MMYY format. Provided in case of ongoing RENEWAL operation.
  - `state` 'ACTIVE' | 'INACTIVE', required — The state of the card.
  - `stateReason` 'CLOSED_ACCOUNT' | 'CLOSED_CARD' | 'CARD_LOST' | 'CARD_FOUND' | 'CARD_STOLEN' | 'CARD_BROKEN' | 'CARD_NOT_RECEIVED' | 'FRAUD' | 'USER_DECISION' | 'ISSUER_DECISION' | 'CVV2_LOCKED' | 'EXPIRY_DATE_LOCKED' | 'PIN_LOCKED' — reason associated to the state
  - `ongoingOperation` 'NONE' | 'RENEWAL', required
  - `creationTime` string, required — 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
  - `accountList` AccountInformation[] — This represent the list of account the card will be attached to.<br/>This list is used for the posting
    - `default` boolean, required — true if the account is the default consumer account
    - `type` 'CHECKING' | 'SAVINGS' — Type of the Account. By default if not provided, it is a 'CHECKING' account.
    - `number` string, required — Account number used for posting to Core Banking System
    - `currencyCode` string, required — Currency Code in ISO 4217 alpha code format
  - `digitalCards` object[] — List of digital cards associated to the card.
    - `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, header, paramters. The below table defines the possible 'Bad request' error: | errorCode | error | Retryable | Comments | | -------------- | ------------| ----------| -----------------------------------| | - | - | yes | No error details available | | FIELD_INVALID_FORMAT | Contains the field in error (first found) | no | One field is not expected format as defined in this documentation |
- `401` — Unauthorized request, the provided Authorization header is missing or invalid. In the table below only the field "error" is provided. | errorCode | error | Retryable | Comments | | -------------- | ------------| ----------| -----------------------------------| | AUTHORIZER_UNAUTHORIZED | Unauthorized message | no | Access token not valid |
- `403` — Forbidden action detected by WAF or the application.<br> The below table defines the possible error: | errorCode | error | Retryable | Comments | | -------------- | ------------| ----------| -----------------------------------| | - | - | no | No error details available | | AUTHORIZER_FORBIDDEN | not authorized error message | no | User is not authorized to access this resource |
- `404` — Ressource not found, Unknown issuerId or consumerId or card id'. The below table defines the possible error: | errorCode | error | Retryable | Comments | | -------------- | ------------| ----------| -----------------------------------| | - | - | no | No error details available | | UNKNOWN_CARD | - | no | Unknown cardId |
- `500` — Internal Server Error. The below table defines the possible error: |errorCode | error | Retryable | Comments | | -------------- | ------------| ----------| -----------------------------------| | - | - | yes | No error details available | | INTERNAL_ERROR | error details if any | no | The server has encountered an error when executing the request. |
- `503` — The service is temporarily unavailable. You may retry your request later.

---

[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)