Integrate in-app ID&V
The End User might be asked by the token requestor to perform a verification under two essential circumstances:
during a tokenization flow. Upon the request to tokenize a card and a subsequent decision to approve with a step-up. This happen in the case a token for proximity payment is requested.
in a post-tokenization flow. This occurs only for e-commerce tokens. Essentially, the merchant can trigger a request for a verification and if the issuer approves with a step-up request, the in-app method can be used.
In general, the user journey is displayed in the following picture:
The digital wallet launches the issuer application for step-up authentication for any of the reason above mentioned:
Step 1: Choose in-app ID&V. The End User selects Sign in to the bank app.
Step 2: Authenticate. The End User signs in to the issuer application.
Step 3: If required, confirm the card. Show the last four digits of the PAN. The End User confirms activation.
Step 4: Confirm the verification result.
Step 5: Return to the wallet to confirm success.
Once the End User selects the in-app method for ID&V, the digital wallet application must redirect the flow to the issuer application.
To do this, the TSP provides the following redirection information:
The issuer application reference (configured by the issuer in the TSP during onboarding).
An opaque payload that describes the reason for the ID&V request.
This section provides a guideline regarding :
The information the issuer must provide to the TSP (application metadata).
How to handle the redirection call from the digital wallet application.
The diagram below shows, at a high level, the main steps involved for such type of interaction between a digital wallet and the issuer application:
During onboarding, the issuer configures the application metadata in the TSP.
During Tokenization, when step-up authentication is required, the TSP provides the following data along with the method type:
issuer application reference
opaque payload
The digital wallet application uses the issuer application reference to open the issuer application. It passes the opaque payload in the call.
The issuer application parses the opaque payload to understand the request. It then prompts the End User to enter credentials.
The issuer application verifies the credentials.
The issuer application returns the verification result to the issuer backend.
The issuer backend reports the result to the TSP.
The opaque payload is essentially a base64 string that encodes a JSON object formatted by the TSP scheme.
The content of this object is not sensitive, so the only operation that the issuer has to do is to decode the base64 format and interpred the JSON fields.
The fields allow the issuer to identify the context for which the verification is required.
Below few examples extracted from the scheme's documentation.
Visa
Use case: tokenization
Use case: device binding
Use case: cardholder verification
Mastercard
Use case: tokenization
Use case: device binding
Optionally, the issuer can rely on D1 SDK to parse the JSON object provided by the digital wallet. This can be used by in all the cases whereas the digital wallet does not manipulate the JSON object in some ways. For example, this can't used for Apple Pay. See details in the section Integration with Apple Pay.
CODE snippet
Mapping the fields with D1 fields
The following mapping rules apply:
D1 digitalCardId:
Visa:
tokenReferenceID.Mastercard:
tokenUniqueReference.
Post-tokenization use cases:
D1 authenticationId:
Token binding
Visa:
deviceIndexMastercard:
authenticationCorrelationId
Cardholder verification
Visa:
lifeCycleTraceId
Last updated
Was this helpful?