QRIS: one code for every app, interoperability lessons from 44.86 million merchants

Industry context

A note up front: MarkasDev had no part in building QRIS. This page examines the case using official sources and media coverage. The Quick Response Code Indonesian Standard (QRIS) is set and developed by Bank Indonesia together with the payment-system industry (including the Indonesian Payment System Association / ASPI). We read Bank Indonesia’s official QRIS pages and press releases, plus Kontan, Tirto, CNBC Indonesia, and Kompas reporting that quotes BI officials. All sources are listed at the end.

On 17 August 2019, coinciding with Indonesia’s 74th Independence Day, Bank Indonesia launched QRIS as the national QR Code standard for payments. Nationwide implementation took effect on 1 January 2020, with a transition period for Payment Service Providers (PJPs). The implementing rules include Members of the Board of Governors Regulation (PADG) No. 21/18/PADG/2019 dated 16 August 2019, later amended, including PADG No. 3 of 2025 (BI’s QRIS page and Kompas, 17 August 2019).

The core idea is simple and consequential: one payment QR Code that any licensed PJP app can scan, so a merchant does not need a wall of stickers from every e-wallet and bank. The standard uses the international EMV Co specification to support interoperability across providers, instruments, and—later—countries (BI QRIS page).

For operations leaders in companies, local government, regional SOEs, health facilities, logistics, retail, and public services, QRIS is a concrete example of how a technical standard plus clear rules can change everyday behaviour for millions of people—from street stalls to MRT stations.

Problem

Before QRIS, QR-based payments in Indonesia were fragmented. Each payment app tended to work only at merchants that used a QR from the same PJP. A shop that wanted to accept several e-wallets and bank apps at once had to display several codes. BI’s official FAQ states the problem plainly: without a shared standard, an app could pay only merchants that shared the same PJP account (BI QRIS page).

The real cost of that fragmentation was more than stickers at the till. Merchants faced messy reconciliation, booking errors, and a higher barrier to entering the cashless economy. Customers wondered which QR to scan. On the policy side, BI linked the standard to the Indonesia Payment System Vision 2025 announced in May 2019: transaction efficiency, financial inclusion, and support for MSMEs (launch coverage summarised by Kompas and BI regulations pages).

The scale is national. According to Deputy Governor Filianingsih Hendarta (quoted by Tirto, 21 August 2026), Indonesia has more than 59 million MSME units, contributing about 60.5 percent of GDP and employing more than 117 million workers, or about 97 percent of the workforce. Without a cheap, uniform digital payment method, many micro businesses stay outside formal financial networks.

So the problem was not “ship another QR app.” It was how to make banks, e-wallets, switching institutions, and millions of merchants speak one technical language—without forcing everyone onto a single brand.

Constraints

• Had to become the mandatory national standard for every payment in Indonesia facilitated by a payment QR Code (QRIS PADG)
• Had to work across many bank and non-bank PJPs without locking merchants to one app brand
• Had to use the international EMV Co standard while fitting Indonesia’s local needs
• Had to reach MSMEs and small-ticket payments, with a Merchant Discount Rate (MDR) scheme set by BI (including special categories such as education, fuel stations, and BLU/PSO)
• Maximum Rp10,000,000 per transaction; issuers may add daily/monthly cumulative limits under their risk management (BI QRIS page)
• Security, PJP licensing, and BI supervision had to hold—users are directed to licensed PJPs
• Later extensions (MPM/CPM, QRIS TUNTAS, cross-border, and NFC-based QRIS TAP) had to expand capability without breaking older interoperability
• Evidence limit: full internal switching design, national uptime SLAs, and the full cost of building the standard are not fully published in the sources we opened

Approach

High-level architecture

This flow is our simplification of BI’s official QRIS page and related press releases, not an architecture we audited. Detailed switching protocols, national capacity figures, and the exact technical split among PJPs are not fully published in the sources we opened. QRIS TAP uses NFC: the user brings a smartphone near a terminal instead of scanning a QR image. The sources we opened do not describe AI as a core QRIS component. This is a standardisation, interoperability, and national-operations case.

Typical outcomes

Common questions