How QR Payments Work: SGQR, PayNow and Banks

Did you know? When you scan a QR code at a Singapore hawker stall, the black-and-white squares do not contain money. They cannot move dollars from one bank to another. Yet that simple scan can begin a payment that completes in moments. What makes it work is a conversation between your payment app and the financial systems behind it.

Quick answer: a payment QR code provides structured payment information, such as the merchant or recipient details and sometimes the amount. A compatible banking or wallet app reads it, shows the transaction for you to review, requests your approval and then uses the relevant payment network to process the transfer. Scanning starts the journey; it does not by itself prove that payment succeeded.

The 30-second explanation

Merchant displays: a payment QR code identifies an accepted way to pay and may include the merchant information and amount.
Customer scans: a supported banking or payment app interprets the code.
Customer checks: the app presents the recipient and the amount, which may need to be entered.
Customer confirms: the app authenticates the customer and sends payment instructions through the appropriate provider and payment rails.
Both sides verify: the customer and merchant rely on payment confirmations and transaction records—not the appearance of the QR code.

A QR code is a shortcut for payment details

Think of a handwritten form asking for a payee and a sum. You could type all the details yourself, but you might make a mistake. A QR code lets a payment app read the relevant information from the printed symbol instead. It is a convenient way to pass instructions from the merchant’s display into your phone.

The code does not need to contain your bank balance, the merchant’s entire account ledger or an image of cash. Its job is to provide information the payment application can understand. The application still decides which scheme is supported and asks you to approve the transaction.

Many payment systems use a merchant-presented QR code: the shop displays it and the customer scans. Some services also support consumer-presented codes, where the customer displays a code for the merchant’s reader. Those two experiences can feel similar but involve different participants initiating the scan.

Step 1: The shop presents a payment code

Picture buying a bowl of noodles for S$5.20. At the counter is a payment label. Depending on the system, the encoded data may include a merchant identifier, transaction information, the amount or a way for the app to obtain those details. If no amount is encoded, you may be asked to enter S$5.20 yourself.

A merchant may use one reusable code for many purchases, or a checkout system may generate a code for a particular order. The reusable option is convenient for small stalls, while a transaction-specific code can associate the payment with an order and its amount. Not every QR payment product supports exactly the same features.

Step 2: The app reads the payment information

You open a compatible banking app or payment wallet, select the QR-scanning function and point it at the code. The phone camera recognises the pattern. The payment app interprets the message according to the format and payment scheme it supports. That is why an ordinary camera app may simply display some encoded text or link, while a payment app can understand a merchant payment request.

The app usually presents a confirmation screen. Treat it like the final review of a bank transfer: inspect the merchant or recipient information, the amount and any other details. A scan is a convenience, not permission to skip checking.

Step 3: The bank or wallet processes the payment

When you approve, the app passes a payment instruction through its service. The participating bank, wallet provider and relevant payment infrastructure determine how the amount is debited and credited. Exactly which systems are involved depends on the payment method. A PayNow bank transfer, for instance, is not the same product as every wallet balance payment, even when both can be initiated from a QR code.

Successful processing produces a transaction state and records in the payment system. The merchant may receive a notification or see the transaction in a point-of-sale dashboard. A phone briefly showing a scanner animation does not mean a payment has cleared. If the app reports an error, the payer and merchant should check their official transaction histories rather than guessing or paying again immediately.

What is SGQR in Singapore?

SGQR stands for Singapore Quick Response Code. It is a common QR label designed to bring several accepted electronic-payment schemes under one displayed code. The merchant’s label indicates which payment options are supported. SGQR is not itself a separate payment app or a new bank. It makes acceptance easier to recognise and reduces the number of different QR signs a merchant has to display.

A café could accept PayNow and certain wallet schemes through its SGQR label, but that does not mean every app can make every type of payment. Check the logos shown on the actual label and use an app that supports the merchant’s accepted scheme. The particular app handles the transaction, subject to the payment provider’s rules.

For PayNow, participating banks and some major payment institutions can support transfers using a PayNow QR code. The Association of Banks in Singapore explains that PayNow QR is integrated into SGQR. The transfer still depends on the participating app, registration and financial infrastructure—not on the geometry of the printed square.

Static amount versus transaction-specific amount

Reusable merchant code: a stall can display one code all day; customers may enter their purchase amount.
Order-specific code: a checkout may generate information for a particular purchase and include the intended amount.
Customer-presented code: in some payment models, the merchant scans a code displayed by the buyer.
Connected checkout: a point-of-sale system can match a successful payment to a specific order, reducing manual reconciliation.

These are design patterns, not universal features. Different markets, payment apps and providers use different data formats and settlement arrangements. When a payment flow feels unfamiliar, the safest guide is the information displayed in the legitimate payment app.

What if the internet connection fails?

Your camera may be able to read a printed code even with no mobile data. But most live payment processing needs a working connection somewhere in the transaction flow so that the payment service can authorise or record the transfer. Some specialised offline payment schemes exist, but they are not a safe assumption for an ordinary merchant-presented QR payment.

This distinction also explains a common puzzle: the code scans instantly but the payment takes longer. Decoding a local square pattern is different from communicating with a payment provider and confirming financial state.

Why a payment screenshot is not the same as payment

Suppose somebody shows the cashier an image saying ‘Payment successful’. Pictures can be copied, altered or shown out of context. The seller should rely on the official merchant banking or payment account, payment terminal or other supported confirmation mechanism. A payment code and an on-screen image are not substitutes for a transaction record.

Similarly, the customer should not simply rescan and resend money when the screen is slow. Open the transaction history or seek assistance in the official payment app. Duplicated payments can be awkward to reverse.

A simple family or classroom experiment

Without moving real money, sketch the steps for buying a S$3 drink. Write QR code, phone, payment app, bank or wallet provider and merchant on five pieces of paper. Arrange them in the order information travels. Now put a star beside the exact step where the person approves a payment. Put another star beside the step where a provider confirms it.

Ask: if the printed QR code disappears after the phone has read it, can the system still process a valid authorised transaction? Often yes: the code has already served its purpose. If the app never contacts the payment provider, has money necessarily moved? No. That contrast turns a simple purchase into a lesson about systems and evidence.

Questions people often ask

Does scanning a PayNow QR code transfer money immediately?

Scanning normally reads payment information. You then review and authorise in the participating app; a successful payment is confirmed through the payment service.

Is SGQR the same as PayNow?

No. SGQR is the shared label and code framework through which merchants may support multiple payment options. PayNow is one payment method that can be accepted through it.

Why do some QR payments ask me to enter an amount?

A reusable merchant code may identify a merchant without carrying a purchase-specific total. A checkout-generated code may include the intended amount.

How do I know the shop received the payment?

Use the approved status and transaction record within your legitimate app; merchants should verify through their own official payment records. If there is doubt, check before submitting another payment.

The idea to remember

A payment QR code shares instructions; a financial network moves money. The scan is only the convenient first step. The important steps are understanding the recipient, authorising the transaction and verifying the result.

Sources and further reading

Association of Banks in Singapore: PayNow — participating institutions and PayNow QR information.
GovTech Singapore: How Do QR Codes Work? — SGQR and everyday digital infrastructure.
HSBC Singapore: PayNow Scan and Pay FAQ — the review and confirmation process.
People’s Association: How to Pay With PayNow QR — example payment steps.

Explore the How QR Codes Work series

Each guide explains a different part of the same everyday technology. Choose what you would like to understand next.

How QR Codes Work | How Scan-to-Pay Connects to Banks and Wallets