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.

API details: See the API reference - cobadged cards.

How cobadged card digitization works

End-to-end cobadged card digitization flow.

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.

Eligibility flow for primary and secondary digitization.

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.

Optional request to map the international FPAN to the domestic FPAN.

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.

Domestic token creation and profile preparation.

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.

Provisioning the domestic profile into the wallet application.

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.

Activation and issuer notification for the secondary token.