Click to Pay

Overview

Click to Pay is Mastercard's solution for returning cardholders who have registered their card with the Click to Pay network. Once registered, they can complete purchases at any merchant that supports Click to Pay without re-entering their card number — they authenticate once and their tokenized card details populate the checkout automatically.

How it works

1. The customer selects "Click to Pay" at your checkout.
2. They authenticate using their Click to Pay profile (email, OTP, or biometric depending on their device).
3. Their saved card is retrieved as a network token and used to create a Payment Method.
4. Payment proceeds through the standard Payment Intent workflow.
5. The card is never exposed — only the token touches your integration.

Key benefits

For your customers:

• No card re-entry on repeat purchases
• Works across all Click to Pay-enabled merchants

For your integration:

• Sensitive card data is fully tokenized — the actual card number never reaches your server
• Complies with EMVCo security standards

How customers use it

1. Customer selects card payment at checkout
2. If they have no Click to Pay profile, they fill in their card details and check the option to create a profile using their email or mobile number
3. On future checkouts at any Click to Pay-enabled merchant, they enter their email or mobile number — their saved cards are displayed automatically
4. The customer verifies with an OTP, selects a card, enters their CVC, and pays

Availability

Click to Pay is available through the PayMongo Checkout page — it works automatically for merchants using:

• Checkout API
• Shopify (with the PayMongo plugin)
• PayMongo Pages
• PayMongo Links

It is currently not available as a direct Payment Intent API integration. No additional setup is required beyond using one of the above integration methods.

Relationship to Card Vaulting

Click to Pay and Card Vaulting both provide faster repeat checkout, but they work differently:

They can be used together — a Click to Pay token can be vaulted on a Customer object for future use.