> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/click-to-pay/get-started/overview.md).

# 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.

<figure><img src="/files/llvNALehOEcl4gu9sIVa" alt=""><figcaption><p>High-level Click to Pay view for the end user, merchant, and payment network.</p></figcaption></figure>

## Standards and participants

The Click to Pay framework is defined by [EMVCo](https://www.emvco.com/emv-technologies/secure-remote-commerce/) under the name **EMV Secure Remote Commerce**.

[EMVCo](https://www.emvco.com/emv-technologies/secure-remote-commerce/) 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.payments.thalescloud.io/click-to-pay/get-started/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.