> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/tokenization/integrate-the-d1-api/d1-api-summary.md). # 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](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/oauth2-api.md#post-oauth2-token) | Issuer -> Thales D1 | Get an OAuth 2.0 access token to call the D1 backend. | | [Renew Card](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-renew) , [Replace card](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-replace) | 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](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-suspend) , [Resume Card](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-resume) | Issuer -> Thales D1 | To control the state of the card in D1. | | [Delete Digital Card](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/digital-card-api.md#post-issuers-issuerid-digitalcards-digitalcardid-operations-delete) , [Delete Card](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-delete) , [Delete Consumer](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/consumer-api.md#post-issuers-issuerid-consumers-consumerid-operations-delete) | Issuer -> Thales D1 | Allow to terminate, definitely, the related asset. The request is cascaded to the children resources. | | [Suspend Digital Card](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/digital-card-api.md#post-issuers-issuerid-digitalcards-digitalcardid-operations-suspend) , [Resume Digital Card](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/digital-card-api.md#post-issuers-issuerid-digitalcards-digitalcardid-operations-resume) | 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](/tokenization/integrate-the-d1-api/d1-api-reference/outbound-api-from-d1/oauth2-api.md#post-oauth2-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 ](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#put-v2-issuers-issuerid-cards-cardid)or [Create Card](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards) | Issuer -> Thales D1 | To register a card. It is conditional to the issuer decision to support AMEX cards. | | [Get Card List](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/consumer-api.md#get-issuers-issuerid-consumers-consumerid-cards) | 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](/tokenization/integrate-the-d1-api/d1-api-reference/outbound-api-from-d1/card-api.md#post-notifications-d1-v2-issuers-issuerid-cards) | 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](/tokenization/integrate-the-d1-api/d1-api-reference/outbound-api-from-d1/consumer-api.md#get-banking-d1-v1-issuers-issuerid-consumers-consumerid) | 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](/tokenization/integrate-the-d1-api/d1-api-reference/outbound-api-from-d1/consumer-api.md#post-banking-d1-v1-issuers-issuerid-consumers-consumerid-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](/tokenization/integrate-the-d1-api/d1-api-reference/outbound-api-from-d1/card-api.md#post-notifications-d1-v1-issuers-issuerid-cards-cardid-notifications) or [Notify Card Operations](/tokenization/integrate-the-d1-api/d1-api-reference/outbound-api-from-d1/card-api.md#post-notifications-d1-v2-issuers-issuerid-cards), [Notify Digital Card Operation](/tokenization/integrate-the-d1-api/d1-api-reference/outbound-api-from-d1/digital-card-api.md#post-issuers-issuerid-digitalcards-digitalcardid-notifications) | 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](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/consumer-api.md#put-issuers-issuerid-consumers-consumerid) | Issuer -> Thales D1 | To register a consumer. | | [Update Consumer Information](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/consumer-api.md#post-issuers-issuerid-consumers-consumerid-operations-update) | Issuer -> Thales D1 | In case the consumer details are registered, the issuer must update it accordingly. | | [Get Card Operation](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#get-v1-issuers-issuerid-cards-cardid-operations-operationid) or [Get All Card Operations](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#get-v1-issuers-issuerid-cards-cardid-operations) | Issuer -> Thales D1 | Allow the issuer to retrieve operation details on the card. | | [Get Digital Card Operation](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/digital-card-api.md#get-issuers-issuerid-digitalcards-digitalcardid-operations-operationid) or [Get All Digital Card Operations](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/digital-card-api.md#get-issuers-issuerid-digitalcards-digitalcardid-operations) | Issuer -> Thales D1 | Allow the issuer to retrieve operation details on the digital card. | | [Get card details](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#get-v2-issuers-issuerid-cards-cardid) | Issuer -> Thales D1 | To retrieve the card details. | | [Get digital card details](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/digital-card-api.md#get-issuers-issuerid-digitalcards-digitalcardid) and [Get digital card credentials](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/digital-card-api.md#get-issuers-issuerid-digitalcards-digitalcardid-credentials) | Issuer -> Thales D1 | To retrieve full details of a digital card. | | [Search digital card](/tokenization/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/digital-card-api.md#post-issuers-issuerid-digitalcards-search) | Issuer -> Thales D1 | To retrieve digital card information using the digital card PAN. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.payments.thalescloud.io/tokenization/integrate-the-d1-api/d1-api-summary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.