Option C – activate in the issuer application

Use this option to complete ID&V in the issuer application. The wallet application redirects the end user to the issuer application. After successful authentication, the issuer backend resumes token activation.

Flow

1

1. Return the issuer application ID&V method

In your requestCardDigitization response, return an idvMethod with type=bank_app. Return the related id and value fields.

See requestCardDigitization in the API reference.

2

2. Redirect to the issuer application

Support redirection between the wallet application and the issuer application. This lets the wallet application continue the flow after the end user selects this method.

See Issuer application integration with the wallet.

3

3. Resume token activation

After the end user completes authentication, call updateCardState with action=RESUME.

See updateCardState in the API reference.

Not all xPay Wallets support issuer application ID&V. Confirm support with your xPay Wallet contact before implementing.

Visa Token Service (VTS)

Visa Token Service (VTS) requires two additional fields for issuer application ID&V. Return these fields in the idvMethod you provide in requestCardDigitization.

• source: Represents the issuer application that provided the "authentication proof" to the wallet application in an app-to-app flow.

  • Apple Pay: Apple Adam ID of the issuer application

  • Google Pay and Samsung Pay: Android package name of the issuer application

• platform: Represents the platform where the issuer application runs. Use one of: IOS, ANDROID, WEB.

Mastercard Digital Enablement Service (MDES)

source and platform do not apply to MDES. Configure MDES to support issuer application ID&V.