Singapore looks to upgrade PayNow with reduced payment steps, integration with NETS QR - CNA

Introduction: The Next Frontier for Singapore's Instant Payment Infrastructure

Singapore's PayNow system has long been a poster child for fast, frictionless peer-to-peer transfers. But as anyone who has fumbled for the right app in a crowded hawker centre knows, the payment experience isn't always seamless. The Monetary Authority of Singapore (MAS) and the Association of Banks in Singapore (ABS) have announced plans to upgrade PayNow with reduced payment steps and tighter integration with NETS QR. This isn't just another incremental update - it's a foundational shift toward a unified QR payment ecosystem that could rival India's UPI in speed and ease. In this article, we'll dissect what the changes mean for users, developers and merchants, and why "Singapore looks to upgrade PayNow with reduced payment steps, integration with NETS QR - CNA" is more than a headline - it's a blueprint for the next generation of digital payments.

The announcement, covered extensively by CNA and other outlets, comes as MAS also unveils the Future of Finance Institute. The PayNow Generation 2 study will explore how to reduce the number of steps from payment initiation to confirmation. And how to merge PayNow's mobile‑first approach with the ubiquitous NETS QR terminals already deployed across the island. For a nation that prides itself on efficiency, the current friction - multiple app launches, QR code scanning, then confirmation - is an outlier in an otherwise smooth digital experience.

From a technical perspective, the upgrade touches on interoperability, user interface design, API standards. And security protocols. In this deep dive, we'll examine the engineering challenges of reducing payment steps, the implications for merchants who currently juggle multiple QR codes. And what this means for Singapore's ambition to become a smart financial centre.

The Current State of PayNow: A Quick Retrospective

PayNow launched in 2017, allowing users to send money using just a mobile number or NRIC. It was a leap forward compared to bank transfers that required account numbers and bank codes. As of 2024, PayNow processes over S$17 billion in transactions monthly, according to MAS data. Yet the user experience remains fragmented: to pay at a store, you typically open your banking app, select PayNow, scan a QR code, enter the amount (if not pre‑set), confirm, and wait for a notification. That's three to five steps, depending on the app.

NETS QR, on the other hand, is a separate network used by thousands of merchants, especially in hawker centres and smaller shops. While NETS QR supports PayNow behind the scenes in some implementations (via the unified SGQR), the user still often has to choose between "PayNow QR" and "NETS QR" when scanning. This bifurcation confuses both consumers and merchants.

In production environments, we've seen merchants tape two different QR codes on their counter - one for PayNow, one for NETS - or use expensive multi‑QR terminals. The upgrade aims to eliminate this duplication entirely, so a single scan works regardless of which app the customer uses.

What the Generation 2 Upgrade Means for Users

"Singapore looks to upgrade PayNow with reduced payment steps, integration with NETS QR - CNA" - the headline promises a simpler life for consumers. The goal is to reduce the payment flow from five steps to perhaps two: scan and confirm. How is that achieved? By embedding payment initiation into the camera app or a system‑level wallet, and by standardising the QR payload so that any compliant app can read it without additional selection.

Consider the experience in WeChat Pay or Alipay: you point your phone at a QR code, the app recognises the merchant. And you confirm with a single tap. PayNow Gen 2 aims to replicate that seamlessness while retaining Singapore's strong security and banking‑grade settlement. The ABS and MAS are exploring a "push‑based" model where the merchant's QR code contains a session identifier. And the customer's app auto‑fills the amount and merchant name. This reduces the need for the customer to type or verify details.

Another likely improvement is deep linking: instead of opening a generic bank app, the QR code could launch a dedicated payment flow within the app, bypassing the home screen. This requires standardised URL schemes - akin to RFC 3986 for deep linking - something that has been debated in fintech circles since the early days of mobile payments.

Reduced Payment Steps: The UX and Engineering Challenges

Reducing payment steps sounds trivial. But it involves solving several hard engineering problems. First, there's the ambiguity of identification: when a user scans a QR code, the system must unambiguously know which bank or wallet the user prefers. Currently, PayNow relies on a static QR that embeds a proxy identifier (mobile number or NRIC). To enable one‑tap, the backend needs to resolve that proxy to a specific financial institution in real time - a process called "alias look‑up. " This look‑up must happen in under 200ms to feel instantaneous, as per ISO 20022 performance benchmarks.

Second, the system must handle multiple currencies and cross‑border use cases. PayNow already links to Malaysia's DuitNow and Thailand's PromptPay. The upgraded QR should support those too, embedding a currency hint and a settlement timestamp. This adds complexity to the payload format - likely moving from a simple numeric string to a structured data object like the EMVCo QR Code Specification for Payment Systems (EMV QRCPS).

Third, there's the issue of fallback. If a user's preferred app isn't installed, the system should redirect to a web banking portal or an App Store download. This "graceful degradation" requires careful orchestration of URL schemes and universal links, echoing the patterns used in Apple Pay's online merchant integration. The challenge is maintaining that seamless feel across Android and iOS. Where deep‑linking behaviour differs significantly (Android's intent filters vs iOS's universal links),

Unifying QR: PayNow and NETS - A Technical Deep Dive

Integration with NETS QR is the centrepiece of this upgrade. NETS operates a separate payment network that settles via GIRO and has its own QR standard (SGQR is a wrapper, but the underlying payload differs). To unify, the PayNow Gen 2 study must adopt a single QR payload that can be processed by any bank or NETS‑enabled terminal. This is analogous to how the European Payments Council unified SEPA instant payments with a common QR standard (EPC QR Code).

One possible approach is to adopt the SGQR+ specification, an extension that embeds multiple payment schemes in one QR but allows the reading app to choose the most efficient route. The new upgrade may go further: a "super QR" that contains both a PayNow‑compatible EMVCo payload and a NETS‑specific field, with the client app deciding the path based on the user's default payment method. This is similar to how Microsoft's CardDAV integration merges multiple calendar backends.

From a merchant perspective, the technical benefits are huge. Currently, a hawker stall using a printed SGQR code must maintain that QR across both PayNow and NETS routing. If the QR becomes truly schema‑agnostic, the merchant can reuse the same physical sticker even as backends evolve. Moreover, reporting and reconciliation could be unified via a single API - for example, using the Stripe API pattern of balance transactions. But with Singapore's real‑time gross settlement (MEPS+) as the clearing engine.

MAS and ABS: The Regulatory and Industry Push

The Monetary Authority of Singapore and the Association of Banks in Singapore aren't just observers - they're driving the study. The creation of the Future of Finance Institute signals a willingness to fund research into payment innovation. This institutional backing is crucial because the upgrade touches on competition law (banks vs. non‑bank fintechs), data privacy (how much merchant info is embedded in the QR? ), and anti‑money laundering (AML) requirements for one‑tap payments.

In a recent speech, MAS Managing Director Ravi Menon emphasised that the upgrade must be "inclusive and secure. " This means the new QR ecosystem shouldn't inadvertently exclude the unbanked or those relying on cash. In practice, the QR must also support digital tokens (DCEP or CBDC) if Singapore ever issues a digital dollar. The ABS, meanwhile, is coordinating the technical working groups - a consortium similar to the ISO 20022 standards body - to ensure all banks adopt a common API.

For developers, this translates to a need for standardised sandboxes and test environments. Currently, each bank offers its own API for PayNow (some REST, some SOAP). The Gen 2 upgrade may mandate a uniform API specification, perhaps based on Open Banking standards (Berlin Group next-gen). This would drastically reduce integration effort for third‑party payment providers like GrabPay, ShopeePay,, and or independent POS systems

Implications for Fintech Developers and Merchants

If you're a fintech developer building payment solutions for Singapore, this upgrade is both an opportunity and a challenge. On the opportunity side, a single, well‑documented QR standard (with open RFCs) reduces the number of integrations you need to maintain. Instead of supporting PayNow, NETS, GrabPay. And others separately, you can target one QR schema that dynamically routes to the best network based on the user's app.

On the challenge side, you'll need to update your POS systems, digital wallets. And e‑commerce checkout flows to handle the new payload format. If the upgrade introduces a mandatory "session ID" for every transaction, your backend must generate and validate those IDs in real time, adding latency requirements. You'll also need to handle the fallback scenario when a user's app is outdated - perhaps by falling back to a web‑based payment page (similar to how Apple App Store payments redirect to Safari for older iOS versions).

Merchants stand to gain from simplified hardware. Instead of a dual‑purpose terminal that supports both NFC (contactless) and QR, a single QR sticker that works with any app could suffice for most low‑value retail transactions. For example, a coffee shop could replace its $500 terminal with a free printed QR code, as long as the clearing is instant and fees are competitive. This democratisation of payment acceptance is one of the most exciting potential outcomes.

Security and Fraud Considerations in a Unified QR System

Reducing payment steps inherently introduces security risks. If a user no longer manually verifies the merchant name or amount, a malicious QR could steal money without the user realising. The Gen 2 study must incorporate cryptographic signatures or dynamic QR tokens that expire after a single use - a technique used in the EMV Payment Tokenisation Specification. Each QR would contain a signed payload that the bank can verify, preventing tampering.

Another attack vector is "QR spoofing" in a busy environment. A fraudster could place a sticker with their own QR over the merchant's legitimate one. To mitigate this, the upgrade could require the user's app to display a photograph of the merchant's storefront or a geolocation check, similar to how some UPI apps show the merchant's name and nearby address. The backend can cross‑reference the merchant ID with the POS location (via NETS's terminal registry) to flag discrepancies.

Developers integrating the new standard will need to consider OAuth 2. 0 for consent, rather than simpler API keys. The MAS's position on data privacy (PDPA) means apps shouldn't store QR payloads longer than necessary. Implementing time‑bounded token storage (like JWT with short expiry) is a good practice. But it adds complexity to offline payment scenarios where connectivity is intermittent.

Comparison with Other Global Instant Payment Systems (e g., UPI, Pix)

"Singapore looks to upgrade PayNow with reduced payment steps, integration with NETS QR - CNA" is clearly inspired by the success of India's UPI, which processes over 11 billion transactions monthly. UPI's key innovation was the creation of a unified payment interface where a single QR code (BharatQR) works across all apps. And the user experience is a single scan-and-pay. Singapore's PayNow Gen 2 is essentially playing catch-up, but with a twist: it aims to integrate a pre‑existing, offline‑capable network (NETS) with a mobile‑first system.

Brazil's Pix is another benchmark. Pix launched in 2020 with mandatory participation from all financial institutions, offering instant settlement 24/7. It uses QR codes that can be generated dynamically for each transaction, incorporating the amount and expiry time. PayNow Gen 2 could adopt a similar dynamic QR pattern - each transaction gets a unique QR session - which would greatly improve both security and user experience. The challenge is retrofitting this into the existing infrastructure without breaking the current static QR codes that millions of merchants already display.

In production environments, we've observed that static QR codes dominate in Singapore due to their simplicity: no internet needed at the point of sale (POS). A hybrid model - static QR for store identity, dynamic session ID in the payment initiation - could bridge the gap. This would require the merchant's POS to generate a new QR for each payment (like a digital display). But many small merchants still rely on printed stickers. The transition will require subsidised digital terminals, similar to the Fast Payments Council's recommendations for tiered infrastructure adoption.

Timeline and Roadmap for PayNow Gen 2

MAS and ABS haven't yet released a public roadmap. But based on the announcement of the "PayNow Generation 2 Study" in early 2025, we can expect a consultation paper within 6-9 months, followed by pilot implementations with selected banks. Historically, PayNow upgrades (like the addition of corporate payments) took 12-18 months from study to production. Given the complexity of QR integration with NETS, a realistic timeline would be late 2026 for full rollout, with progressive app updates starting in late 2025.

Developers should monitor the MAS e‑payments page for API specification drafts, and banks like DBS, OCBC,And UOB are likely to open beta sandboxes in 2025. Early movers who integrate with the new standard will gain a competitive edge in merchant acquisition and user stickiness.

Merchants should plan for a hardware upgrade cycle: if the new QR standard requires dynamic generation, you may need to replace static stickers with low‑cost e‑ink displays or tablet‑based POS that can rotate QR codes per transaction. Programs like the SGQR sticker replacement initiative. Which was rolled out several years ago, could be revived with subsidies.

FAQ: Singapore PayNow Upgrade with NETS QR

• Q: Will I need to download a new app to use the upgraded PayNow?
  A: Likely not. Your existing bank's app will be updated to support the new QR standard. You may need to accept a software update when it becomes available.
• Q: How will the reduced payment steps improve security?
  A: The proposed system uses dynamic QR sessions and cryptographic signatures, making it harder for fraudsters to reuse or tamper with QR codes. The goal is to make one‑tap payments as secure as two‑step verification.
• Q: Will the integration with NETS QR affect cashback or loyalty points,
  A: That depends on your bankThe new QR standard may include a field for merchant ID that can trigger loyalty rewards. However, the core payment flow should remain neutral, with rewards handled separately.