D1 API summary

This section provides a summary of the APIs used in the Tokenization service.

The APIs are grouped into:

• Mandatory: must be implemented by the issuer for a proper integration in D1 and compliance with the schemes.
• Conditional: to be implemented according to the integration model chosen by the issuer.
• Optional: to be implemented according to the issuer business needs.

Mandatory APIs

API	Inbound/Outbound	Description
Get Authorization Token	Issuer -> Thales D1	Get an OAuth 2.0 access token to call the D1 backend.
Renew Card , Replace card	Issuer -> Thales D1	Renew the card on D1 and request the TSP to link the existing digital cards. Replace the card on D1 and request the TSP to link the existing digital cards.
Suspend Card , Resume Card	Issuer -> Thales D1	To control the state of the card in D1.
Delete Digital Card , Delete Card , Delete Consumer	Issuer -> Thales D1	Allow to terminate, definitely, the related asset. The request is cascaded to the children resources.
Suspend Digital Card , Resume Digital Card	Issuer -> Thales D1	To control the state of the digital card in D1 and on the TSP.

Conditional APIs

API	Inbound/Outbound	Description
Get Authorization Token	Issuer <- Thales D1	Get an OAuth 2.0 access token to call the issuer backend. It is conditional to the issuer integration model preference.
Register Card or Create Card	Issuer -> Thales D1	To register a card. It is conditional to the issuer decision to support AMEX cards.
Get Card List	Issuer -> Thales D1	Retrieves the list of cards for a given consumer. Required in cases whereas the issuer needs to manage customer service care websites or in any case where the issuer backend needs a sync on the actual state of the consumer.
Verify Card	Issuer <- Thales D1	To allow the card details verification when those are not stored in D1. It is conditional to the integration model chosen by the issuer.
Get Consumer Information	Issuer <- Thales D1	To allow D1 to make decisions on behalf of the issuer based on the consumer details when those are not stored in D1. It is conditional to the integration model chosen by the issuer.
Deliver OTP	Issuer <- Thales D1	In case the issuer decides to manage the messages towards the end user, it must implement this API.
Notify Card Operation or Notify Card Operations, Notify Digital Card Operation	Issuer <- Thales D1	It reports the result of an operation on a card/digital card to the issuer. The issuer must review the different notification types and decide the type of notification to enable.

Optional APIs

API	Inbound/Outbound	Description
Register Consumer	Issuer -> Thales D1	To register a consumer.
Update Consumer Information	Issuer -> Thales D1	In case the consumer details are registered, the issuer must update it accordingly.
Get Card Operation or Get All Card Operations	Issuer -> Thales D1	Allow the issuer to retrieve operation details on the card.
Get Digital Card Operation or Get All Digital Card Operations	Issuer -> Thales D1	Allow the issuer to retrieve operation details on the digital card.
Get card details	Issuer -> Thales D1	To retrieve the card details.
Get digital card details and Get digital card credentials	Issuer -> Thales D1	To retrieve full details of a digital card.
Search digital card	Issuer -> Thales D1	To retrieve digital card information using the digital card PAN.