Register and View

Get card details

get

/issuers/{issuerId}/cards/{cardId}

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

Authorizations

AuthorizationstringRequired

A JWT generated by the Get Authorization Token API.
The server checks the validity of the provided token to control access to this protected resource. Please refer to Get OAuth 2.0 access token for more details on the flow and on how to get this JWT.

Path parameters

issuerIdstring · min: 10 · max: 10Required

The id of the issuer

cardIdstring · min: 1 · max: 48Required

Unique identifier of the card.

Pattern: [A-Za-z0-9_-]{1,48}

Header parameters

x-correlation-idstring · min: 1 · max: 64Optional

Random identifier which can be used to correlate the different API calls done as part of a single use-case. This identifier will be the one primarily used for troubleshooting.

Warning: This identifier should not be derived from sensitive personal data, as its value will be logged in clear.

There is no strong guarantee of the uniqueness of this identifier, so please refrain from using it for purposes other than logging and troubleshooting.

Pattern: [a-zA-Z0-9_\-\. ]{1,64}

Responses

200

Successful get card details

application/json

consumerIdstring · min: 1 · max: 64Optional

Unique identifier of the end user.

Pattern: [A-Za-z0-9_-]{1,64}

accountIdsstring[]OptionalDeprecated

List of accountIds associated to the card. accountId pattern : [A-Za-z0-9_-]{1,64}
Note: accountIds is deprecated. This optional response parameter will no more be returned.

cardIdstring · min: 1 · max: 48Optional

Unique identifier of the card.

Pattern: [A-Za-z0-9_-]{1,48}

cardProductIdstring · min: 1 · max: 48Optional

Unique identifier of the type of card (defined during the onboarding of D1)

Pattern: [A-Za-z0-9_-]{1,48}

threeDSsupportbooleanOptional

Determines if the card supports EMV 3-D Secure (3DS) flows.

schemestring · enumOptional

The card scheme

Example: VISAPossible values:

panSuffixstringOptional

Last 4 digits of the PAN

Example: 1234Pattern: \d{4}

expstringOptional

Expiry date of the card in MMYY format

Example: 1022Pattern: (0[1-9]|1[0-2])\d{2}

statestring · enumOptional

The state of the card.

Example: ACTIVEPossible values:

creationTimestring · min: 1 · max: 64Optional

The time the ressource has been created. Format ISO 8601 YYYY-MM-DDThh:mm:ssTZD

Example: 2022-02-16T06:28:02.492Z

lastUpdateTimestring · min: 1 · max: 64Optional

The time the resource has been last updated. Format ISO 8601 YYYY-MM-DDThh:mm:ssTZD

Example: 2022-07-16T06:28:02.492Z

400

Bad Request, Invalid request URI or header, or unsupported non-standard parameter

application/json

401

The provided Authorization header is missing or invalid

application/json

403

Forbidden action, check the state of the linked end user (consumer) or account or digital card

application/json

404

Resource not found

application/json

500

Internal Server Error

application/json

get

/issuers/{issuerId}/cards/{cardId}

GET /banking/v1/issuers/{issuerId}/cards/{cardId} HTTP/1.1
Host: api.d1.thalescloud.io
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*

Register card

put

/issuers/{issuerId}/cards/{cardId}

This request is used by the issuer backend to request the registration of a card that has been already created by the issuer without involving D1. This allows D1 to make this card eligible for card tokenization through the D1 SDK. D1 manages to retrieve useful card information from the Issuing Processor CMS based on the cardId provided.

Authorizations

AuthorizationstringRequired

Path parameters

issuerIdstring · min: 10 · max: 10Required

The id of the issuer

cardIdstring · min: 1 · max: 48Required

Unique identifier of the card.

Pattern: [A-Za-z0-9_-]{1,48}

Header parameters

x-correlation-idstring · min: 1 · max: 64Optional

Random identifier which can be used to correlate the different API calls done as part of a single use-case. This identifier will be the one primarily used for troubleshooting.

Warning: This identifier should not be derived from sensitive personal data, as its value will be logged in clear.

There is no strong guarantee of the uniqueness of this identifier, so please refrain from using it for purposes other than logging and troubleshooting.

Pattern: [a-zA-Z0-9_\-\. ]{1,64}

Body

consumerIdstring · min: 1 · max: 64Required

Unique identifier of the end user.

Pattern: [A-Za-z0-9_-]{1,64}

cardProductIdstring · min: 1 · max: 48Required

Unique identifier of the type of card (defined during the onboarding of D1)

Pattern: [A-Za-z0-9_-]{1,48}

accountIdstring · min: 1 · max: 64OptionalDeprecated

Unique identifier of the account.
Note: accountId is deprecated. You can still pass it but it will be ignored.

Pattern: [A-Za-z0-9_-]{1,64}

statestring · enumRequired

The state of the card.

Example: ACTIVEPossible values:

Responses

204

Successful card registration

400

Bad Request, Invalid request URI or header, or unsupported non-standard parameter

application/json

401

The provided Authorization header is missing or invalid

application/json

403

Forbidden action. At least one of the registration could not be done.

Check the state of the linked end user (consumer).

Check that the cardId does not belong to an existing end user (consumer).

Check that the pair "PAN and EXP" was not already registered with another cardId.

Check that the cardId was not already registered with different data.

application/json

404

Resource not found Unknown issuerId or consumerId or accountId.

application/json

500

Internal Server Error

application/json

put

/issuers/{issuerId}/cards/{cardId}

PUT /banking/v1/issuers/{issuerId}/cards/{cardId} HTTP/1.1
Host: api.d1.thalescloud.io
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 61

{
  "consumerId": "text",
  "cardProductId": "text",
  "state": "ACTIVE"
}

No content

PreviousInbound NextOperations

Last updated 12 days ago

Was this helpful?