Thales D1 eCom Enablement overview

Understand what D1 eCom Enablement does, who it’s for, and what to do next.

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.

D1 eCom Enablement high-level flow

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.

Integration between D1 eCom Enablement and the issuer backend varies by issuer integration model.

Next steps

1

Understand the Tokenization flow

Start with Tokenization.

2

Review API behavior and compatibility rules

Read the D1 API overview.

3

Set up security prerequisites

• Configure mutual TLS: Set up mutual TLS (mTLS)
• Get an access token: Get an OAuth 2.0 access token

4

Integrate the D1 API

Use the D1 API reference.

If you’re new to the terminology, scan the Glossary.