Check card eligibility

Overview

Card eligibility is the first step in Tokenization. It verifies that a card can be tokenized by the payment network TSP.

A card is eligible only when both conditions are true:

1. The Issuer configured the required card-product metadata in the payment network TSP (for example, card artwork and terms and conditions).
2. The card is in the active state.

If the card is eligible, the payment network TSP can return the metadata to the token requestor (for example, xPay Wallets) so it can be displayed to the End User.

Only the Issuer can configure card-product metadata in the payment network TSP. D1 cannot access or modify these TSP settings.

In the D1 API, an End User is referred to as a consumer (for example, consumerId).

Prerequisites

Before D1 can check eligibility on behalf of the Issuer, make sure you:

1. Define card products

   • Configure the mapping between the card product BIN range and the payment network TSP card-product identifier.
2. Manage cards and end users. Check Get Started section.

   • So D1 can resolve the card and link it to the End User (consumerId).

Who triggers the check

The token requestor triggers the eligibility check through the payment network TSP.

D1 evaluates eligibility and returns the result to the payment network TSP.

User experience

Example end-user flow when a token requestor checks card eligibility

High-level flow

High-level eligibility check flow across the token requestor, payment network TSP, D1, and issuer backend

Sequence diagram

Sequence diagram for the eligibility check

End User data used by D1

D1 can use End User (consumer) personal information in two ways:

• If you provided personalInformation when registering the end user, D1 uses the stored data.
• If you did not provide personalInformation, D1 retrieves it from your issuer backend when needed.

This behaviour depends on your chosen integration model. For details, see the Get started section.

If eligibility fails

If eligibility fails systematically, check the following first:

• The card is in the active state.
• The card product is configured correctly in D1, including the mapping between the card product BIN range and the payment network TSP card-product identifier.
• The required card-product metadata is configured in the payment network TSP (Issuer-owned configuration).

If you still see failures after these checks, capture the payment network TSP error details and contact Thales support.