> 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/features/one-click-payment.md).

# One-Click Payment

One-click payment makes repeat purchases easier for returning customers. Instead of entering payment details or selecting a payment method from the beginning, the customer uses a previously saved card, bank account reference, or digital wallet and confirms the payment.

The E-Commerce Payment Gateway (EGW) supports one-click experiences through saved cards, Pay by Bank, and digital wallets. The available options depend on the merchant’s configuration and enabled payment services.

### How It Works

1. During an initial payment, the customer chooses to save or enable the payment method, where this option is available.
2. EGW or the relevant payment provider securely stores a token, reference, or payment profile for future use.
3. When the customer returns, the saved method reduces the information they need to enter.
4. The customer reviews and confirms the payment. Additional authentication may be required depending on the payment method, bank, issuer, or transaction.
5. EGW processes the payment and provides the transaction status to the merchant.

### One-Click Options

#### Saved Cards

The customer chooses to save their card during an initial purchase. EGW stores the card details securely as a token. For a later purchase, the customer selects the saved card and confirms the payment without re-entering the card details. 3D Secure authentication may be requested when required.

#### Pay by Bank

The customer can choose to save a bank account reference during an initial Pay by Bank payment. On a later purchase, the saved reference can allow the customer to skip selecting the bank and account again. The customer still confirms the payment through their bank, and additional authentication may be required as part of the bank’s flow.

#### Digital Wallets

Digital wallets provide their own saved payment experience. The customer selects a wallet, chooses an available payment credential, and confirms the payment in the wallet interface. Depending on the wallet and configuration, a token may also be stored with the customer’s consent for future payments.

### Benefits for Merchants and Customers

* Faster checkout for returning customers
* Fewer payment details to enter again
* A familiar confirmation flow through the selected payment method
* Secure handling of payment credentials through tokens or references
* Support for card, bank payment, and wallet experiences within EGW

The merchant’s systems use the relevant token or payment reference rather than storing customers’ underlying card or bank credentials. The exact integration and authentication flow depends on the selected payment method.


---

# 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/features/one-click-payment.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.
