> 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/classic-tokenization/use-cases/card-enrolment/cobadged-card-enrollment-flow.md).

# Cobadged card enrollment flow

Cobadged cards include two payment applications on the chip:

* An international payment network application (for example, Mastercard or Visa)
* A domestic payment network application

The domestic application typically works only in the issuing country.

The international application typically works globally.

Using the domestic application can reduce fees for merchants and issuers.

Cobadged card digitization requires two **TSP** flows:

* A primary flow with the international payment network **TSP**
* A secondary flow with the domestic **TSP**

The token requestor (wallet provider) owns both flows.

{% hint style="info" %}
API details: See the [API reference - cobadged cards](/classic-tokenization/api-reference-cobadged-cards/api-reference-cobadged-cards.md).
{% endhint %}

### How cobadged card digitization works

<figure><img src="/files/I9Dc6SJLbACocGmdENr2" alt=""><figcaption><p>End-to-end cobadged card digitization flow.</p></figcaption></figure>

In this context, there are two flows:

1. The primary flow between the token requestor, the international **TSP**, and the **Issuer**.
2. The secondary flow (auxiliary flow) between the token requestor, the domestic **TSP**, and the **Issuer**.

The flows are independent.

The token requestor must keep them synchronized.

The token requestor handles card eligibility, **ID\&V**, card metadata, and terms and conditions approval in the primary flow.

If any primary-flow prerequisite fails, the token requestor stops digitization.

The token requestor triggers the secondary flow only when primary token provisioning is guaranteed.

### Eligibility (primary and secondary flows)

The following diagram shows the key eligibility steps.

<figure><img src="/files/aay8g6UDLXQLlzCS8bBc" alt=""><figcaption><p>Eligibility flow for primary and secondary digitization.</p></figcaption></figure>

### Digitization: request (optional)

While the token requestor progresses through the primary flow with the international **TSP**, it can also trigger digitization with the domestic **TSP**.

Some payment authorization flows require the domestic **FPAN**.

They do not accept the international **FPAN**.

During digitization, the token requestor does not always provide the domestic **FPAN**.

In that case, the Tokenization Service asks the **issuer backend** to map the international **FPAN** to the domestic **FPAN**.

The following diagram shows this request flow.

<figure><img src="/files/Yq635WieDzCGs74IMGYK" alt=""><figcaption><p>Optional request to map the international FPAN to the domestic FPAN.</p></figcaption></figure>

### Digitization: token creation

The Tokenization Service receives the required data from the **Issuer**.

It then requests token creation from the domestic **TSP**.

In parallel, the Tokenization Service prepares the associated digital card profile.

<figure><img src="/files/85yWWqtFfBPJal7LmXJ5" alt=""><figcaption><p>Domestic token creation and profile preparation.</p></figcaption></figure>

### Digitization: provisioning

When the digital card profile is ready, the Tokenization Service notifies the token requestor.

The token requestor pulls the profile and downloads it into the wallet application in a suspended state.

<figure><img src="/files/EsbRi2fzcMsUssjHW1Wl" alt=""><figcaption><p>Provisioning the domestic profile into the wallet application.</p></figcaption></figure>

### Activation

Once the token requestor receives a notification that the primary token is activated, it requests activation of the secondary token.

After activation completes, the **Issuer** is notified.

This is the final step in cobadged card digitization.

<figure><img src="/files/zfoXfq29H0DdSMB7Xio9" alt=""><figcaption><p>Activation and issuer notification for the secondary token.</p></figcaption></figure>


---

# 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/classic-tokenization/use-cases/card-enrolment/cobadged-card-enrollment-flow.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.