Use Cases

Visa Click to Pay

Merchants and Payment Service Providers

Use Cases

A Digital Terminal can create multiple checkout initialization experiences for their DPAs. Sample user journeys are shown in the below pages. These user journeys are provided for illustrative purposes only. Digital Terminal should independently evaluate all content and recommendations in light of their specific business needs, operations, and policies, as well as any applicable laws and regulations.

Below are our Consumer Experience Guidelines that can be viewed as a Figma Prototype to further familiarize yourself with the implementation requirements needed to foster the complete user journey from end-to-end as a Digital Terminal or Digital Payment Application. The password is: coffee-thumb-vote-marine

Existing User Recognized via Remember Me

Assumptions:

Alex has used the device to perform a prior checkout.
Alex has previously enrolled in Visa Click to Pay and chosen to be remembered during prior checkout on the same device.
Returning‑user recognition may rely on SRC System cookies (when supported by the browser) and/or a Merchant Recognition Token (MRT) stored as a first‑party cookie.

Notes:

Remember Me using SRC System cookies is only available on supported browsers (e.g., Chrome, limited support on Edge depending on whether the user was stepped up on a pop-up or not).
Remember Me using Merchant Recognition Tokens (MRT) is supported across all browsers. MRTs are stored as first‑party cookies and recognition occurs only when Alex returns using the same browser where the MRT was originally stored. Cookie validity may vary depending on each browser’s restrictions.

Journey:

Alex navigates to the checkout page.
The Digital Terminal attempts to recognize Alex on the device using available mechanisms:
- SRC System cookies, if present and supported by the browser, and/or
- A previously stored MRT, included as a request parameter in the Click to Pay recognition call.
One or more Click to Pay systems recognize Alex as a returning user on the device.
The Digital Terminal receives card details from the recognized Click to Pay system(s).
The Digital Terminal aggregates the card list obtained from all participating Click to Pay systems, orders the cards, and displays them for selection.
Alex selects a card from the list and continues checkout.
Once Alex confirms the order, the Digital Terminal submits the information and selections to the Click to Pay system to receive the checkout payload.
The Digital Terminal orchestrates any required Cardholder Verification Method (CVM).
The Digital Terminal passes the payload to the Digital Payment Application for transaction processing.

Existing User Identified via Email Address or Mobile Number

Assumptions:

Alex has previously enrolled in Visa Click to Pay.
Alex is not recognized on the device by any Click to Pay system.

Journey:

Alex navigates to the checkout page.
The Digital Terminal checks with participating Click to Pay systems to identify Alex on the device and receives a "user not recognized" response.
The Digital Terminal offers Alex the option to identify using an email address or mobile number.
The Digital Terminal initiates profile lookup with Alex's information, including email address or mobile number.
The Digital Terminal requests all participating Click to Pay systems to identify the provided email or mobile number.
Based on the responses, the Digital Terminal selects the Click to Pay system that recognizes the email address or mobile number to initiate the one-time code flow to validate Alex’s identity.

Note: System selection is based on the Click to Pay system containing the last-used card. If no last-used card exists, the system that responds first is selected.
Alex receives a one-time code via email and text (SMS).
The Digital Terminal presents a screen to capture the one-time code and offers Alex the option to be remembered on this device. Alex needs to enter the one-time passcode either from the email or text (SMS). The entered code is sent to the Click to Pay system for verification.
After successful verification, the Digital Terminal retrieves Alex's card list from participating Click to Pay systems.

Linking a Card

New User
Existing User

Assumptions:

Alex does not have a Click to Pay profile.

Journey:

Alex navigates to the checkout page.
The Digital Terminal captures all necessary data, including card details, name, billing address, email address, and phone number.
The Digital Terminal displays Click to Pay awareness content, terms, privacy notice, profile information, and an opt-out option to Alex.
Once Alex confirms the order, the Digital Terminal submits the information and other selections to Click to Pay system to receive the checkout response.

Note: During link card flows; Digital Terminal must always wait for checkout response to receive a tokenized payload. In certain scenarios, Visa Click to Pay may return PAN payload if tokenization was unsuccessful. The card will not be made available for future purchases until tokenization is successful.
An email is sent to Alex with the result of their link card request.
The Digital Terminal passes the payload to the Digital Payment Application for transaction processing. This application may also use the checkout reference identifier to obtain a full payment payload for transaction processing (if not already processed).

Cardholder Authentication Methods

3DS
Passkeys
Issuer Online Banking
Issuer OTP
CVV2

Visa Secure with EMV 3-D Secure is embedded within Click to Pay to get authenticated payload without having to integrate with an external 3DS provider for Click to Pay transactions. This may not be available depending on regulatory requirements for certain countries or regions (e.g., Strong Consumer Authentication in Europe). DPA can provide a specific authentication preference during the transaction for Visa Click to Pay to facilitate 3DS authentication.

In the checkout request, the Digital Terminal can pass an authentication preference specifying 3DS as a method and pass respective configuration settings, including challenge indicator, to request 3DS authentication to be performed by Visa Click to Pay on behalf of its DPA. Visa Click to Pay will perform 3DS and return payment credentials in the checkout response, including ECI value and dynamic data.

Use Case Variations

Card List Optimization

Issuers in certain countries or regions only support the enrollment of consumer credit and debit cards using a mobile number, without requiring an email address.

When a consumer uses Click to Pay at checkout, the Digital Terminal performs an identityLookup with either an email address or mobile number to Visa Click to Pay to retrieve the consumer’s list of cards. If the identityLookup is performed using only an email address, only cards enrolled with that email will be retrieved. This may result in missing cards from issuers who enrolled the consumer’s card with only a mobile number and without email. To maximize the number of relevant cards retrieved for a consumer, we recommend that the Digital Terminal performs sequential identityLookup requests with both the mobile number and the email address if there is no result. In the Asia Pacific region, it is recommended to perform identityLookup with the mobile number first, followed by the email address

Displaying Combo Cards in Card List

Certain Visa card products support both credit and debit accounts (such as combo cards in Brazil) and allow cardholders to choose whether the transaction will be processed as credit or debit at checkout. When the Visa Click to Pay system returns card details, an additional combo card indicator is included to enable the user experience based on merchant market preferences.

Additional CVV Verification

As described above, additional CVV verification can be triggered during the checkout flow to mitigate fraud risks from mobile number recycling, SIM card swap attacks, and stolen phone scenarios.

It is targeted at high-risk markets (CEMEA, AP) and applies to returning users authenticating via mobile identity with SMS OTP.