> 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/ecom/get-started/thales-d1-ecom-enablement-overview.md).

# Thales D1 eCom Enablement overview

Thales D1 eCom Enablement platform streamlines the access to domestic network tokenization service by exposing a single API for tokenizing the cards from different issuers.

<figure><img src="/files/2wv9Pxg0ZdOwKZyK0JPO" alt="High-level flow for D1 eCom Enablement"><figcaption><p>D1 eCom Enablement high-level flow</p></figcaption></figure>

### Who should use this

Use D1 eCom Enablement if you operate:

* A merchant gateway that aggregates multiple merchants
* A Payment Service Provider (PSP)

### Supported use cases

* Card-on-file (COF) payments
* One-time purchases
* Recurring payments

### What you build with it

* Request Tokenization for an end user’s card.
* Store the token and use it for CNP transactions.
* Handle token Life Cycle Management (LCM) events, when applicable.

### How it works (high level)

1. Collect the card details with the end user’s consent.
2. Call the D1 API to request Tokenization.
3. Store the token in your system.
4. Use the token for CNP payments.
5. Process LCM events to keep token status in sync.

{% hint style="info" %}
Integration between D1 eCom Enablement and the issuer backend varies by issuer integration model.
{% endhint %}

### Next steps

{% stepper %}
{% step %}

### Understand the Tokenization flow

Start with [Tokenization](/ecom/implement-d1-ecom-enablement/create-a-token.md).
{% endstep %}

{% step %}

### Review API behavior and compatibility rules

Read the [D1 API overview](/ecom/integrate-the-d1-api/d1-api-overview.md).
{% endstep %}

{% step %}

### Set up security prerequisites

* Configure mutual TLS: [Set up mutual TLS (mTLS)](/ecom/integrate-the-d1-api/set-up-mutual-tls-mtls.md)
* Get an access token: [Get an OAuth 2.0 access token](/ecom/integrate-the-d1-api/get-an-oauth-2.0-access-token.md)
  {% endstep %}

{% step %}

### Integrate the D1 API

Use the [D1 API reference](/ecom/integrate-the-d1-api/d1-api-reference.md).
{% endstep %}
{% endstepper %}

If you’re new to the terminology, scan the [Glossary](/ecom/get-started/glossary.md).


---

# 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/ecom/get-started/thales-d1-ecom-enablement-overview.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.