Bank Indonesia and HKMA deepen cooperation on cross-border QR payments

Sourced news briefing

Bank Indonesia announcement, 24 September 2026 announced the development on 24 September 2026. Bank Indonesia and the Hong Kong Monetary Authority signed a memorandum of understanding concerning cross-border payment cooperation based on quick-response codes. The central-bank announcement framed the cooperation as supporting more convenient cross-border transactions. The initiative sits within broader efforts to strengthen payment connectivity between the two economies. A memorandum and implementation work do not mean that every merchant, wallet, bank or use case is immediately live. Detailed participation, technical and commercial arrangements remain relevant to providers and merchants before activation.

This opening briefing is limited to the published announcement. The announcement establishes a cooperation direction; it does not publish universal merchant pricing, settlement timing, foreign-exchange treatment or an activation date for every participant. The sections that follow are independent FixPays analysis for merchants and do not attribute conclusions to Bank Indonesia.

Independent analysis: acceptance scope

Cross-border QR acceptance can look simple at checkout while depending on the customer wallet, participating acquirer, merchant category, currency route and market rules behind the code. For a merchant, the immediate question is not whether the announcement sounds ambitious, but where it changes an actual payment, settlement, compliance or customer-service workflow. Ask which customer wallets and merchant locations are actually enabled. Document whether a static or dynamic code is used. Keep unsupported-market messages clear at checkout.

The implementation file should identify participants, currencies, transaction limits, refund support and the merchant contract governing acceptance. A useful review should name the responsible team, the system of record, the exception path and the date on which the control was last tested. That converts a broad industry development into work that can be compared with existing provider contracts and operating procedures.

Independent analysis: currency and settlement

The customer-facing amount, conversion point, merchant receivable and bank credit can differ across a cross-border QR journey. For a merchant, the immediate question is not whether the announcement sounds ambitious, but where it changes an actual payment, settlement, compliance or customer-service workflow. Capture the quoted currency and amount. Record who performs conversion and when. Reconcile gross sales, fees, refunds and net settlement separately.

A test pack should include the QR payload, customer confirmation, provider reference, exchange-rate information where supplied and final bank credit. A useful review should name the responsible team, the system of record, the exception path and the date on which the control was last tested. That converts a broad industry development into work that can be compared with existing provider contracts and operating procedures.

Independent analysis: operations across two markets

Disputes and support requests can cross language, time-zone and institutional boundaries even when payment initiation is immediate. For a merchant, the immediate question is not whether the announcement sounds ambitious, but where it changes an actual payment, settlement, compliance or customer-service workflow. Publish a support path that identifies the merchant. Set service ownership for failed or duplicated payments. Confirm how refunds reach the original funding route.

An exception matrix should cover timeout, pending, duplicate, reversal, refund and unmatched-settlement scenarios. A useful review should name the responsible team, the system of record, the exception path and the date on which the control was last tested. That converts a broad industry development into work that can be compared with existing provider contracts and operating procedures.

Independent analysis: merchant implementation checklist

Confirm live participant coverage before advertising the method. Merchants should connect this point to the order ledger, retain evidence in a corridor control sheet, and define who decides whether an exception can proceed. The same record should show what was expected, what occurred, how any difference was resolved and whether a provider or customer communication was required.

Test customer and merchant receipts in the supported languages. Merchants should connect this point to the currency quotation, retain evidence in a transaction trace, and define who decides whether an exception can proceed. The same record should show what was expected, what occurred, how any difference was resolved and whether a provider or customer communication was required.

Map every provider reference into the order system. Merchants should connect this point to the refund workflow, retain evidence in a finance reconciliation file, and define who decides whether an exception can proceed. The same record should show what was expected, what occurred, how any difference was resolved and whether a provider or customer communication was required.

Separate exchange-rate questions from payment-status questions. Merchants should connect this point to the settlement report, retain evidence in a support case log, and define who decides whether an exception can proceed. The same record should show what was expected, what occurred, how any difference was resolved and whether a provider or customer communication was required.

Monitor acceptance and refund performance by corridor. Merchants should connect this point to the order ledger, retain evidence in a corridor control sheet, and define who decides whether an exception can proceed. The same record should show what was expected, what occurred, how any difference was resolved and whether a provider or customer communication was required.

Update checkout messaging when participation or limits change. Merchants should connect this point to the currency quotation, retain evidence in a transaction trace, and define who decides whether an exception can proceed. The same record should show what was expected, what occurred, how any difference was resolved and whether a provider or customer communication was required.

Before changing production, the merchant should run a controlled sample through the order ledger, compare the result with the currency quotation, and archive the outcome in a corridor control sheet. Failed tests should remain visible until an accountable owner records the cause, corrective action and decision to retest or stop. This protects customers from a launch based only on a successful demonstration.

Commercial review should cover more than the advertised feature. The merchant should compare contractual scope, service levels, settlement terms, data responsibilities, incident duties and exit arrangements with the operating assumptions documented in a transaction trace. Any unresolved dependency should be recorded before volume moves, because an announcement cannot amend the merchant’s existing agreement by implication.

After launch, performance should be reviewed by corridor, method, product or customer journey as relevant. Approval rates alone are insufficient: finance and operations should monitor unmatched items, reversals, refunds, complaints, support time and settlement differences. Material deterioration should trigger investigation through a finance reconciliation file and a decision on whether the affected flow should continue.

Keep all relevant operational merchant payment compliance control testing exception resolution approval reconciliation settlement customer support transaction governance audit implementation provider contract risk change records complete and current.

Document all relevant operational merchant payment compliance control testing exception resolution approval reconciliation settlement customer support transaction governance audit implementation provider contract risk change decisions clearly before launch.

Keep all relevant operational merchant payment compliance control testing exception resolution approval reconciliation settlement customer support transaction governance records complete and current.