> 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/d1-v1-api/register-end-users-and-cards-in-d1.md).

# Register end users and cards in D1

Register end users, accounts, and cards before you use D1 services.

Registration is an issuer backend to D1 backend flow.\
You can register a card at any time before you use it with a D1 service.

Your issuer backend provides your own identifiers:

* `consumerId` for the end user
* `accountId` for the account
* `cardId` for the card

These identifiers are used to reference resources in the D1 API and during troubleshooting.

{% hint style="info" %}
You may this flow if you use Tokenization v1 only.
{% endhint %}

{% hint style="info" %}
The D1 API uses the term **consumer** for an end user.\
This documentation uses **end user**, and keeps API field names as-is (for example, `consumerId`).
{% endhint %}

## Registration flow

<figure><img src="/files/rkDfolsefT0vuz5ZDeTE" alt=""><figcaption><p>End user and card registration flow (issuer backend to D1 backend)</p></figcaption></figure>

## Choose identifiers

If your issuer backend does not manage accounts (or you do not have a stable `accountId`), use `consumerId` as `accountId`.

{% hint style="warning" %}
Follow these rules for identifiers:

* Ensure `consumerId`, `accountId`, and `cardId` are unique in your D1 tenant.
* Do not include personally identifiable information (PII) in `consumerId` or `accountId`.
* Do not include sensitive card data (for example, PAN) in `cardId`.
  {% endhint %}

## Register an end user with cards

Call [Register Consumer with cards](/d1-v1-api/d1-v1-api-references/consumer-operations/operations.md#put-issuers-issuerid-consumers-consumerid-cards) from your issuer backend.

To add more cards for an existing end user, call the same API again.\
Reuse the existing `consumerId`, and include the new cards in the payload.

<details>

<summary>Legacy v1 registration APIs</summary>

These endpoints remain available if you integrated before `Register Consumer with cards` was released:

* [Register Consumer](/d1-v1-api/d1-v1-api-references/consumer-operations/operations.md#put-issuers-issuerid-consumers-consumerid)
* [Register Account](broken://pages/c22f57896ae746bb155654be3c09b794eb902448#put-issuers-issuerid-accounts-accountid)
* [Register Card](/d1-v1-api/d1-v1-api-references/card-operations/inbound/operations.md#put-issuers-issuerid-cards-cardid)

</details>


---

# 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/d1-v1-api/register-end-users-and-cards-in-d1.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.