Overview

D1 orchestrates the Tokenization flows with payment network TSPs on behalf of the issuer, simplifying the integration effort of the issuer towards the different TSPs available in the market.

The orchestration is possible thanks to the fact that the issuer registers the consumers and cards data in D1, see the following sections for details.

Which payment networks supports D1?

D1 supports Tokenization through the TSPs of the following payment networks:

• American Express
• Mastercard
• Visa

What is Tokenization?

Tokenization is defined by EMVCo. It replaces a card’s PAN (also called the FPAN) with a payment token (a DPAN) for use in a digital channel.

A Tokenization flow is always initiated by a token requestor—for example:

• xPay Wallets (such as Apple Pay, Google Pay, and Samsung Pay)
• An e-commerce merchant

Tokenization flow

Tokenization in D1 is split into three main steps:

1

Check card eligibility

D1 verifies that the card is eligible for Tokenization.

A card is eligible when the issuer has provided the required card-product metadata (such as card artwork and terms and conditions) to the payment network TSP.

To support this check, the issuer must provide D1 with the mapping between:

• The card product BIN range
• The card product identifier used by the payment network TSP

For details, see Check card eligibility.

2

Process the Tokenization request

If the card is eligible, D1 decides whether to approve or decline the Tokenization request.

D1 evaluates data from:

• The card and end-user data available in D1 (or retrieved from your issuer backend, depending on your integration model)
• The token requestor (device and wallet signals provided through the TSP)

Depending on the outcome, D1 can:

• Approve
• Decline
• Approve with step-up authentication

For details, see Processing the decision.

3

Complete Tokenization

Based on the decision, the payment network TSP provisions the DPAN (digital card) to the token requestor.

• For an approval, the digital card can be activated and used.
• For a decline, no digital card is provisioned.
• For step-up authentication, the end user must complete an additional authentication step before activation.

In all cases, D1 notifies the issuer backend with the Tokenization outcome.

For details, see Processing the response.

After Tokenization

After Tokenization completes, the issuer can perform additional operations, including:

• Retrieve Tokenization data (for example, digital card credentials and token requestor characteristics). See Tokenization data retrieval.
• Perform LCM operations on digital cards (for example, suspend, resume, or delete). See Digital card life cycle.

Tokenization is a server-to-server solution that uses the D1 API.

If your step-up authentication includes an in-app flow, you can optionally use the D1 SDK in the issuer application. See In-app authentication backend.

Example end-user experience

The following example shows an end-user experience for Tokenization with approval and OTP step-up authentication: