> 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.md).

# Digital Wallets

The Tieto E-Commerce Payment Gateway supports [Apple Pay](https://doc.ecomm.api.tietoevry.com/payment-method/digital-wallets/apple-pay.md), [Google Pay,](https://doc.ecomm.api.tietoevry.com/payment-method/digital-wallets/google-pay.md) [PayPal](https://doc.ecomm.api.tietoevry.com/payment-method/digital-wallets/paypal.md) and [Click to Pay](https://doc.ecomm.api.tietoevry.com/payment-method/digital-wallets/click-to-pay.md), enabling our customers to offer merchants secure and convenient digital wallet payment options. These methods provide a seamless checkout experience across mobile and desktop environments, helping merchants improve conversion rates and meet customer expectations for fast and easy payments.

Click to Pay, provided by Visa and Mastercard, offers a simplified and secure online checkout experience without requiring customers to manually enter card details. It leverages EMV® Secure Remote Commerce (SRC) standards, tokenization, and advanced authentication to protect payment information. Click to Pay enables faster transactions and is optimized for both desktop and mobile use, providing a consistent experience across participating merchants.

The integration of digital wallets is available through both the [GatewayCheckout Page](broken://pages/D5r6kKD7cgcWaRjfA1dz) and [API-based ](https://doc.ecomm.api.tietoevry.com/integrations/unified-merchant-api.md)integrations, allowing merchants to select the option that best fits their technical and business requirements. In the hosted checkout scenario, the payment page is managed by Tieto, reducing the merchant’s compliance scope and simplifying implementation. Merchants opting for API integration can fully embed wallet payments within their checkout flow while maintaining secure processing through the EGW.


---

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