> 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/linkpay-and-qr-codes.md).

# LinkPay and QR codes

The E-Commerce Payment Gateway (EGW) provides Payment Link and QR Code functionality, allowing merchants to easily create secure payment requests that can be shared with customers through multiple channels.

With Payment Links, merchants can generate unique payment URLs that redirect customers to a secure Hosted Checkout page to complete their payment. These links can be shared via email, SMS, messaging apps, invoices, or embedded directly into websites.

**Each payment request can be configured with parameters such as:**

* payment amount and currency
* payment description or reference
* expiration time or validity period
* single-use or reusable payment links
* optional customer reference information

**For every payment request, the gateway can generate:**

* a secure payment link (URL)
* a QR code that customers can scan to open the payment page
* embeddable payment button code for use on websites or invoices

**Payments initiated through Payment Links or QR codes can support multiple payment methods depending on the merchant configuration and market, including:**

* card payments
* account-to-account (A2A) payments via Open Banking
* digital wallets, where supported

The hosted payment page can be customized with merchant branding, enabling a consistent and secure checkout experience for customers.

**Payment Links and QR codes provide a flexible payment option for many use cases, such as:**

* remote payments
* invoice payments
* customer support payments
* social media or messaging payments
* in-store QR payments

All transactions are processed through the secure EGW payment environment, ensuring high security standards and regulatory compliance.


---

# 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, and the optional `goal` query parameter:

```
GET https://doc.ecomm.api.tietoevry.com/features/linkpay-and-qr-codes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.