In-app authentication

The in-app authentication use case occurs during a tokenization flow where the end user chooses to be authenticated through the application of the issuer. The issuer can determine whether to support this ID&V method. To support the ID&V method, the Issuer has to consider a certain level of effort (development) to allow the interaction between the wallet and its applications, which is covered in this section.

The general flow is depicted in the following diagram:

Note

• In step 4, it is up to the Issuer to respond to a digitization request with an in-app ID&V.

• In step 6, issuer has to perform a configuration in the TSP.

• In step 9, issuer has to manage the integration with the Wallet properly to identify the card and the token. This is explained in the following section.

• In step 10, the application must show the last4 of Card PAN as card identification.

• In step 12, it is up to the issuer to perform the consumer authentication accordingly.

• In step 13, it implies the knowledge of the token reference to allow the activation of the token where the token information is provided through the step 9 . The activation can be accomplished through the Token life cycle management.

To redirect the end user to the issuer application, the wallet application needs the appropriate redirection information.

The redirection information is partially provided in the response of step 4 and partially configured in the scheme TSP. To configure this information correctly, check with your contact in TSP team.

The following sections show the integration between the issuer application and the wallet.