> 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/transaction-control/get-started/manage-cards/register-cards/register-cards-via-api.md).

# Register cards via API

The registration is a backend-to-backend process between your issuer backend and the D1 backend. It can be done at any time before the card is used in a D1 service. You can also combine card registration with card creation for the same end user.

As part of this registration, the issuer backend must provide the following information:

* `cardId`: A technical unique identifier of the card used to identify the card in the D1 API and D1 SDK, and for troubleshooting. The `cardId` **must not** be the PAN or derived from the PAN (for example, a hash or digest of the PAN).
* `cardProductId`: Identifies the card product definition to which the card is linked.
* PAN and expiry date: Provided encrypted using JWE.
* `consumerId`: The issuer backend identifier for the end user who owns the card.

{% hint style="info" %}
Note : If the End User is not already register to D1 then D1 will automaticaly create and register a End User from the provided consumerId with any personal information associated. Then D1 will call the Get Consumer Info API each time it needs one or serveral personal information.
{% endhint %}

Unlike card creation, card registration does not require an account list, because D1 does not orchestrate calls to the Core Banking system (CBS).

Card registration depends on how you use D1:

* Card can be **Explicitly** register via the D1 API
* Or Card can be **Implicitly** register in some particular cases  (based on `cardId`   and  `consumerId`)**:**
  * If an unregistered card is [Tokenize ](https://docs.payments.thalescloud.io/tokenization/)successfully .
  * If a unregistered card is [Ordered ](/central-issuance/implement-central-issuance.md)from Physical Issuance 

## Sequence diagram

<figure><img src="/spaces/62lLFDcmLCeqqwmy4Fee/files/WDxQFOg3hDK1NXGUdaIW" alt=""><figcaption><p>Card registration flow between the issuer backend and the D1 backend</p></figcaption></figure>

After registration, you can use this card across different D1 Digital services:

* [Transaction Control](https://docs.payments.thalescloud.io/transaction-control/)
* [Secure Card Display](https://docs.payments.thalescloud.io/secure-card-display/)
* [Tokenization](https://docs.payments.thalescloud.io/tokenization/)
* [Push Provisioning](https://docs.payments.thalescloud.io/push-provisioning/)


---

# 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:

```
GET https://docs.payments.thalescloud.io/transaction-control/get-started/manage-cards/register-cards/register-cards-via-api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.