---
title: "Request to check digital card account eligibility"
method: POST
path: "/checkCardAccount"
---

# Request to check digital card account eligibility

`POST /checkCardAccount`

This method is used by wallet server to check that a card account is eligible for provisioning.

## Headers

- `x-pod` string, required

## Request body

- CheckCardAccountReq
  - `requestHeader` RequestHeader, required
    - `requestId` string, required — Unique request identifier
    - `sessionId` string, required — Unique session identifier used to trace the calls across systems during a use case.
    - `generationDateTime` string, date-time — Date time representing when the request or response has been generated.<br/>RFC3339 format.<br/> Examples:<li>"2018-12-24T17:32:28Z"<li>"2019-10-02T10:00:00-05:00"
  - `issuerId` string, required
  - `cardAccountDescriptor` CardAccountDescriptor, required — The Card Account Descriptor.<br/>Depending on cardSource, it shall be formatted as follows: - For ON-FILE:<br/>"cardAccountDescriptor" : {"walletCardAccountId" : "1234"} - For USER-INPUT, CLIENT-SDK and READER-MODE:<br/>"cardAccountDescriptor" : {"opaqueCardAccountData" : "data returned by Issuer backend to Wallet"}
  - `device` Device, required
    - `seId` string, required — Secure Element Identifier
    - `deviceType` number, required — Device type. |value|description| |-------|-------| |1|Phone| |2|Tablet| |3|Watch| |4-99|RFU|
    - `language` string, required — ISO 639-3 three-letter language codes
    - `phoneNumberLastDigits` string — Last digit of the phone number (usually 4 or 5)
    - `deviceName` string — Device name that the device owner may use to identify it
  - `cardSource` 'ON-FILE' | 'CLIENT-SDK' | 'USER-INPUT' | 'READER-MODE'

## Response `200`

checkCardAccount response payload

- CheckCardAccountRes
  - `responseHeader` object, required
    - `responseId` string, required — Unique response identifier
    - `sessionId` string, required — Unique session identifier used to trace the calls across systems during a use case.
    - `generationDateTime` string, date-time — Date time representing when the request or response has been generated.<br/>RFC3339 format.<br/> Examples:<li>"2018-12-24T17:32:28Z"<li>"2019-10-02T10:00:00-05:00"
    - `statusCode` number, required — Status code to the request |Status code | Description| |-------|-------| |0|OK| |111|Missing mandatory parameter| |112|Bad parameter format| |113|Unknown issuer| |115|Unknown product| |116|Unknown card account| |159|Card is blacklisted| |160|Card is deleted| |162|Card has unsufficient balance| |163|Card product not eligible| |911|Operation failed| |921|Unexpected server error|
    - `statusMessage` string — Textual status message
  - `termsAndConditionsId` string — Unique identifier of the T&C to be presented to the end user.</br> If T&Cs are not required, all 0's should be returned.</br> getAsset API will be used to retrieve the T&Cs content.
  - `cardArtManifest` string[] — Array of GUIDs required to build card art.</br> Each cart art can be retrieved using getAsset API with corresponding GUID.

## Other responses

- `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/versions/96089514858c/schema)