> 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/secure-card-display/get-started/manage-cards/register-cards-via-api.md).

# Register cards via API

Card registration is a backend-to-backend flow between your **issuer backend** and the **D1 backend**.

You can run it 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 registration, your issuer backend provides:

* `cardId`: A unique technical identifier used in the D1 API and D1 SDK. It must not be the PAN or derived from the PAN.
* `cardProductId`: The identifier of the card product.
* PAN and expiry date: Encrypted using JWE.
* `consumerId`: Your issuer backend identifier for the end user who owns the card.

{% hint style="info" %}
If the end user is not registered in D1, D1 can implicitly register the end user from the provided `consumerId`. When D1 needs personal information, it calls your issuer backend using [Get consumer information](https://thales-dis-dbp.stoplight.io/d1-caas/branches/mergeV1V2/80c02eb3c9adf-get-consumer-information).
{% endhint %}

Unlike card creation, card registration does not require an account list.

### Sequence diagram

<figure><img src="broken://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 the card across other D1 services, for example:

* [Transaction control](https://thales-dis-dbp.stoplight.io/docs/d1-caas/25aregsmz7a2q-transaction-control)
* [Secure Card Display](https://thales-dis-dbp.stoplight.io/docs/d1-caas/3c8a7e6f0a81a-secure-card-display-introduction)
* [Tokenization](https://thales-dis-dbp.stoplight.io/docs/d1-caas/ad6a9b717d3b9-introduction)
* [Push provisioning](https://thales-dis-dbp.stoplight.io/docs/d1-caas/294f33eaf2378-push-provisioning-introduction)

### API endpoint

Register the card using:

* [Register card](/secure-card-display/integrate-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#put-v2-issuers-issuerid-cards-cardid)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.payments.thalescloud.io/secure-card-display/get-started/manage-cards/register-cards-via-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.