> For the complete documentation index, see [llms.txt](https://doc.ecomm.api.tietoevry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ecomm.api.tietoevry.com/payment-method/digital-wallets/click-to-pay.md).

# Click to Pay

The Tieto E-Commerce Payment Gateway supports Click to Pay by Mastercard, a secure, streamlined checkout solution that enables consumers to complete online purchases quickly — without manually entering card details. Click to Pay is based on EMV® Secure Remote Commerce (SRC) standards and supports guest checkout, card-on-file experiences, and SCA-compliant flows.

EGW integrates Click to Pay as part of the Hosted Checkout experience or via APIs, enhancing the user journey while reducing fraud and cart abandonment.

{% hint style="info" %}
You can try this payment experience in our [Sandbox](/e-commerce-payment-gateway/sandbox-guide.md). Learn more about the [Sandbox](/e-commerce-payment-gateway/sandbox-guide.md) , and feel free to [contact us](https://ecomm.api.tietoevry.com/your-access) with any questions!
{% endhint %}

## Gateway Owner Responsibility

To activate Click to Pay in production, the Gateway Owner (e.g., Bank or PSP) is responsible for:

* Registering with Mastercard Identity Check / SRC
* Enabling merchant IDs with Mastercard’s Click to Pay program
* Ensuring compliance with branding and display rules

These responsibilities apply in both delivery models:

* Managed Service – EGW provides integration, while contractual registration is handled by the Gateway Owner.
* On-Premises – The Gateway Owner manages both technical and business enablement.

## What is Click to Pay?

Click to Pay allows customers to securely store their card credentials (via Mastercard and other participating schemes) and pay with a one-click experience across multiple merchant websites — similar to wallets, but scheme-managed.

Customers benefit from:

* No need to enter card numbers or billing details
* One-tap checkout experience
* Consistent look and feel across merchants
* Support for Visa, Mastercard, and other SRC-enabled cards

##  EGW Integration Capabilities

Tieto EGW natively integrates with Mastercard’s Click to Pay SDK and SRC APIs, managing tokenization, scheme messaging, and checkout orchestration.

| Component        | Responsibility                                                                                                       |
| ---------------- | -------------------------------------------------------------------------------------------------------------------- |
| EGW              | Embeds Click to Pay button in Hosted Checkout, handles identity lookup, transaction requests, and response handling. |
| Mastercard       | Provides SRC framework, card vault, and user authentication flow.                                                    |
| Merchant Website | Displays Click to Pay button (automatically via EGW script).                                                         |

Integration is available via:

* Hosted Checkout Page (automatically enabled if device/browser supports it)
* API-based checkout with SRC SDK injection

## Customer Checkout Flow

1. Customer selects Click to Pay at checkout.
2. EGW invokes Mastercard’s SRC SDK to identify the user via device, email, or card number.
3. Customer authenticates (if needed) and selects a stored card.
4. EGW receives a tokenized payload via Mastercard MDES and processes the payment.
5. Customer sees immediate confirmation on the site.

### Security & Compliance

* Compliant with EMV SRC standards
* Uses network tokenization via MDES
* Built-in Strong Customer Authentication (SCA) via issuer or Mastercard authentication
* PCI DSS scope reduced due to no raw card data entry
* Secure browser/device identification and fraud checks

### Merchant Benefits

* Increased conversion with frictionless repeat purchases
* No need to store card data on merchant systems
* Supports guest checkout and returning customer flows
* Automatically updated card credentials via Mastercard
* Fully white-labeled in Hosted Checkout or merchant’s brand


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.ecomm.api.tietoevry.com/payment-method/digital-wallets/click-to-pay.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.