> For the complete documentation index, see [llms.txt](https://docs.finpay.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finpay.id/documentation/payment-gateway/payment-channels/payment-channel-details/qr-payment.md).

# QR Payment

## Overview

Finpay accept QR-based payments for supported QR networks, including QRIS and Cross-border QR.

## Supported QR products

### QRIS (Indonesia)

QRIS (Quick Response Code Indonesian Standard) is a standard QR-based payment method, regulated by Bank Indonesia, that is used to facilitate transaction across Indonesia. Every single QR-based payment in Indonesia is required to follow QRIS.

By its flow, QRIS can be categorized into 2 categories:

1. Merchant Presented Mode (MPM)
2. Customer Presented Mode (CPM)

By its amount, QRIS can be categorized into 2 categories:

1. Static
2. Dynamic

See [QRIS](/documentation/payment-gateway/payment-channels/payment-channel-details/qr-payment/qris.md) page to learn more.

### Cross-border QR

Together with overseas switching network and collaboration lead by Bank Indonesia, Financial Institution in Indonesia can now accept QR code payment from overseas bank, including Finpay. Finpay has accept QR payment from multiple countries including, Thailand and Singapore.

Contact us for more details.

{% hint style="info" %}
Availability depends on your merchant profile and configuration.
{% endhint %}


---

# 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://docs.finpay.id/documentation/payment-gateway/payment-channels/payment-channel-details/qr-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.