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

# QRIS

## Overview

QRIS (Quick Response Code Indonesian Standard) is the Bank Indonesia–regulated standard for QR payments in Indonesia. All QR-based payments in Indonesia must follow QRIS.

## Payment flow

### Merchant Presented Mode (MPM)

1. The merchant requests QR generation from Finpay.
2. Finpay creates the QR and sends it to the merchant.
3. The merchant displays the QR to the customer.
4. The customer scans the QR using their issuer/bank/e-money app.
5. The customer reviews the details and confirms the payment.
6. The issuer notifies Finpay of the transaction status.
7. Finpay notifies the merchant of the final transaction status.

{% hint style="info" %}
Static-amount QRIS is currently available only via Mitra Finpay. Check the Mitra Finpay page for details.
{% endhint %}

### Customer Presented Mode (CPM)

1. The customer generates a QR using their issuer/bank/e-money app.
2. The merchant scans the QR using their device.
3. The merchant sends the transaction details to Finpay via API.
4. Finpay requests the issuer/bank/e-money provider to debit the customer for the transaction.

## Operations

### Settlement

Settlement timing depends on your configuration.

See [Settlement and Refund](/documentation/payment-gateway/settlement-and-refund.md).

### Refunds

Refund support depends on QRIS rules and your configuration.

## Limits and key rules

See [Limit & Terms](broken://spaces/wdWV5w9iOXHhU6klMx61/pages/31c9RZ6c5C90qsqfyGxx).

## Reporting and reconciliation

See [Payment Statuses](/documentation/report/payment-statuses.md).


---

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