Overview

Click to Pay is an EMVCo standard for secure online checkout that improves the security of e‑commerce transactions while preserving a smooth user experience for end users.

It provides an e‑commerce wallet experience owned by the payment networks and used directly from the merchant’s checkout page. Conceptually, it is similar to xPay Wallets such as Apple Pay or Google Pay, but dedicated to browser- and app-based e‑commerce.

How Click to Pay works

In Click to Pay, digital cards are managed in the cloud and can be used across multiple devices and channels.

The main characteristics are:

• Digital cards are cloud-based, not tied to a single device.

• End user identification happens directly on the merchant checkout page, typically using an email address and/or phone number.

• The same Click to Pay profile can be reused across participating merchants, which simplifies checkout for the end user.

High-level Click to Pay view for the end user, merchant, and payment network.

Standards and participants

The Click to Pay framework is defined by EMVCo under the name EMV Secure Remote Commerce.

EMVCo is a global organization, led by international payment networks, that defines standards and ensures interoperability across the payment ecosystem.

Based on this framework:

• Click to Pay is supported by major payment networks such as Mastercard, Visa, American Express, and Discover.

• EMVCo defines the framework, architecture, use cases, and user experience.

• Each payment network operates its own Click to Pay program, with specific APIs and requirements for merchants, payment service providers (PSPs), acquirers, and issuers.

Each participant in the Click to Pay program, from the merchant to the issuer, must meet a defined set of technical and operational requirements.

How D1 helps issuers

With D1, Thales enables issuers to integrate with multiple payment networks’ Click to Pay programs through a unified model. This allows issuers to:

• Simplify integration with each payment network’s Click to Pay APIs.

• Reuse their existing D1 integration instead of building custom connections per payment network.

• More easily comply with the obligations and program requirements defined by the networks.