> 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/tokenization/implement-tokenization/check-card-eligibility.md).

# 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**.

{% hint style="warning" %}
Only the **Issuer** can configure card-product metadata in the payment network **TSP**. D1 cannot access or modify these TSP settings.
{% endhint %}

{% hint style="info" %}
In the **D1 API**, an **End User** is referred to as a `consumer` (for example, `consumerId`).
{% endhint %}

### Prerequisites

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

1. [Define card products](/tokenization/get-started/manage-cards/define-card-product.md)
   * 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](/tokenization/get-started.md) 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

<figure><img src="/files/RRkMvxPeh2H42QIA8od4" alt=""><figcaption><p>Example end-user flow when a token requestor checks card eligibility</p></figcaption></figure>

### High-level flow

<figure><img src="/files/CUEyHKP2zTxRol4fihMZ" alt=""><figcaption><p>High-level eligibility check flow across the token requestor, payment network TSP, D1, and issuer backend</p></figcaption></figure>

### Sequence diagram

<figure><img src="/files/U8hTGaFjZnu2XD5Rahqs" alt=""><figcaption><p>Sequence diagram for the eligibility check</p></figcaption></figure>

### 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](/tokenization/get-started.md) 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).

{% hint style="info" %}
If you still see failures after these checks, capture the payment network TSP error details and contact Thales support.
{% 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/tokenization/implement-tokenization/check-card-eligibility.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.