> 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/click-to-pay/implement-click-to-pay-issuers/enroll-cards-in-click-to-pay/enroll-cards-by-auto-enrollment.md).

# Enroll cards by auto enrollment

Automatic Click to Pay enrollment lets the issuer enable enrollment without calling the explicit Click to Pay enrollment API.

Issuers that do not have specific constraints on the data to enroll (for example, consent management or additional data validation) can enable Click to Pay enrollment directly when consumer and card data is registered in D1.

{% hint style="info" %}
Please note that the auto enrollment option must be chosen by the issuer at the project kickoff.
{% endhint %}

## Auto enrollment during D1 registration

Automatic Click to Pay enrollment is driven by the [Manage end users](/click-to-pay/get-started/manage-end-users.md) and [Manage cards](/click-to-pay/get-started/manage-cards.md) process.

When auto enrollment is enabled, the consumer and card data provided during registration is used to automatically trigger a Click to Pay enrollment request.

As described in the [Manage end users](/click-to-pay/get-started/manage-end-users.md) and [Manage cards](/click-to-pay/get-started/manage-cards.md)  sections, registration can be performed through:

* D1 API
* Batch file (see section [Integrate batch files](/click-to-pay/register-cards-via-batch-file.md) for more details)

## Key points

* Auto enrollment relies entirely on the data sent in the D1 registration flow. If any required consumer details are missing or invalid, the Click to Pay enrollment will fail.
* Auto enrollment is suitable only when the issuer does **not** require additional controls during enrollment (such as explicit consent management or extra data validation).
* The issuer can still use Notifications and the Get Operation APIs to verify the final status of the auto enrollment operation (check [API summary](/click-to-pay/integrate-the-d1-api/d1-api-summary.md) section).

{% hint style="warning" %}
The issuer **must** provide all required consumer details through the D1 API or batch files. Otherwise, the Click to Pay enrollment will fail and the platform may be overloaded with unnecessary retries.
{% endhint %}

{% hint style="warning" %}
**Do not** enable auto enrollment if you are not confident in the quality and completeness of the consumer details, or if you require explicit consent management as part of enrollment.
{% endhint %}


---

# 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/click-to-pay/implement-click-to-pay-issuers/enroll-cards-in-click-to-pay/enroll-cards-by-auto-enrollment.md?ask=<question>&goal=<endgoal>
```

`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.