Click To Pay


Click to Pay is an intelligent, password-free online checkout option that provides a quick and easy checkout experience designed to make ‘guest checkout’ faster and easier across all devices. Click to Pay provides a single checkout button and a standardised checkout flow for all participating card schemes, including Mastercard, Visa, American Express, Discover, and others. Click to Pay is built off EMVCo's SRC specification and replaces Masterpass, Visa Checkout, and Amex Express Checkout.

A payer can create a Click to Pay profile using their email address. During checkout, the payer must then provide this email address and perform an additional verification step with a one-time passcode (OTP). They can also choose the "Remember me" option to subsequently skip the verification when using the same browser in a subsequent checkout. The payer can store multiple credit, debit, or prepaid cards, the associated billing addresses, and multiple shipping addresses in their Click to Pay profile. Card details are securely stored, and additional security is provided by offering network tokenization where possible (market acceptance of network tokenization must be enabled). Click to Pay allows your payer to select the payment details to be used for the payment; however, the payment itself is processed using the acquirer configured for your merchant profile in the gateway.

The Click to Pay ‘Embedded Experience’ is supported through a JavaScript SDK if you are using your own payment page. Click to Pay is currently only available in a select number of countries. Check with your payment service provider to see if it is available in your country. The Click to Pay ‘Embedded Experience’ is supported on MasterCard Payment Gateway from API version 62 for Mastercard, Visa, and American Express cards. You will need to build your integration using the MTF environment first and then go live on the production environment.

Key Benefits

Click to Pay offers the following benefits:

  • Intelligent consumer recognition, ‘embedded’ into the checkout flow, to initiate faster guest checkout across all devices (with no passwords to remember).
  • A reduction in clicks and manual card entry to ultimately increase conversion and create frictionless experiences.
  • Potential for higher authorization approval rates, via network tokenization, assisting in the reduction of preventable declines.
  • Built upon EMVCo Secure Remote Commerce standards to create a consistent user experience and lower fraud rates in eCommerce guest checkout payment moments.
  • Secure exchange of payment data including card details, billing, and shipping address details.


If you want to offer Click to Pay as a checkout option to your payers:

  • Contact your payment service provider to ensure that Click to Pay is available to you.
  • From the Admin menu in Merchant Administration, click SRC Configuration and follow the instructions to onboard to SRC and activate SRC for your merchant profile. You must have the required privilege to update your SRC configuration.

Interaction sequence flows diagrams

The following diagrams detail the Web Service API and JavaScript operations for each Click to Pay flow.

New Card / Payer
Returning payer recognized by cookie
Returning payer recognized by email

Click to Pay Payment Details

This section describes the payment details returned for Click to Pay interactions.

Type of Payment Details Returned for Click to Pay Interactions

Click to Pay supports returning different types of payment details for processing. The payment details returned by the Click to Pay system depend on the type requested by the gateway, your configuration in the Click to Pay system, and the card scheme. Click to Pay typically returns a network token, token expiry, and full cryptogram (where supported by the card scheme).

If a card does not support network tokenization (for example, where the the issuer is not participating), Click to Pay returns the card details (card number and card expiry) instead of network token details (network token, token expiry and cryptogram).

If you are a U.S. merchant and have indicated that you want to make use of your rights under the Durbin amendment, Click to Pay provides the card details (card number and card expiry) for debit cards.

Click to Pay Payment Details in API Transaction Response

The payment details selected by the payer during the Click to Pay interaction are stored in the session and returned in the transaction response for API requests performed using the session. When Click to Pay provides the network token details, both the network token details and the (masked) card details are provided.

Depending on the type of payment details returned by the Click to Pay system, you receive the following details in the API response.

Name Response
Network token with full cryptogram (American Express does not support this type of network token) (The cryptogram is not returned in transaction responses)
  • The response contains sourceOfFunds.type=SCHEME_TOKEN
  • The (masked) card details are returned in the following fields:
    • sourceOfFunds.provided.card.number
    • sourceOfFunds.provided.card.expiry.year
    • sourceOfFunds.provided.card.expiry.month
  • The network token details are returned in the following fields:
    • sourceOfFunds.provided.card.deviceSpecificNumber
    • sourceOfFunds.provided.card.deviceSpecificExpiry.month
    • sourceOfFunds.provided.card.deviceSpecificExpiry.year
Card number and expiry
  • The response contains sourceOfFunds.type=CARD
  • The (masked) card details are returned in the following fields.
    • sourceOfFunds.provided.card.number
    • sourceOfFunds.provided.card.expiry.year
    • sourceOfFunds.provided.card.expiry.month

Payer Details

The payer's name and phone number are provided in the transaction response in the customer parameter group.

The payer's email address is provided in the transaction response in the field, if you have set consumerEmailAddressRequested to true.

Billing Address Details

The billing address details associated with the card are provided in the transaction response in the billing.address parameter group.

Shipping Address Details

If you have set collectShippingAddress to true, the shipping address details are provided in the transaction response in the shipping.address parameter group.

Merchant-Initiated Transactions

You must not offer Click to Pay as a checkout option to your payers if you want to subsequently use those payment details to initiate payments in a series, such as recurring or installment payments. This will be supported in a future release.

Adding Click To Pay to Your Integration

The gateway supports the following integration options for Click To Pay

Integration Option When to Use
Hosted Checkout This is the easiest integration option. To initiate Click To Pay directly from the payer's browser, you must first establish the authentication channel where your merchant server must communicate with the gateway server for creating a session on the gateway. The gateway generated session Id is then included in all browser-initiated authentication requests as the password parameter (see session-based authentication).
Hosted Session This is a client-side JavaScript integration that allows you to have control over the layout and styling of your payment page, while reducing PCI compliance costs. Use this option if you want to allow the payer to submit their payment details directly to the gateway from the browser (see session-based authentication).

Test Your Integration

The MPGS Click to Pay experience can be tested using merchant’s test profile.

Supported Testing Methods

Region Live or Test Merchant Card Type Used Functionality/Purpose
MTF Live Click to Pay Provided – Sandbox Test Card Testing through the Click to Pay Sandbox portion of the Payment flow only
MTF Test MPGS Provided Test Card Testing the merchant’s integration with MPGS only (Click to Pay Portion of flow is simulated)
Production Live Live Cards owned by the merchant Full end to end testing with MPGS and Click to Pay
Production Test MPGS Provided Test Card Testing the merchant’s integration with MPGS only (Click to Pay Portion of flow is simulated)

Please note: These cards may not work with EMV 3DS or test payment processing. You may need to test these features separately using the standard TEST merchant prefix approach.

Frequently Asked Questions

As a payer, I've added a card to my Click To Pay wallet. Why doesn't it appear on the checkout page?

While your payer's Click to Pay profile itself can contain cards for any supported card schemes, for a given transaction your payer can only use Click to Pay for those cards where:

  • The card scheme has been activated for SRC on your merchant profile, and
  • Your merchant profile is configured to process cards with this scheme and the transaction currency.  

Is End to End testing available with Click To Pay?

Currently, End to End testing is not supported with Click To Pay. Merchants are able to test with live merchants in MTF for the Click To Pay interaction only.  

Copyright © 2023 Mastercard