PayNow Corporate vs PayNow: What Operators Miss About Singapore's Rail

Most operators building payment flows for Singapore understand PayNow at a surface level: it's Singapore's real-time bank transfer system, linked to phone numbers, fast, and widely used for P2P. What many operators miss is that there are two distinct PayNow products with fundamentally different capabilities, and the one relevant for business payment flows — PayNow Corporate — supports API-initiated payment requests, structured reconciliation data, and integration with FAST and GIRO rails in ways that PayNow P2P does not.

Getting this distinction wrong means either building on the wrong infrastructure (trying to use PayNow P2P for merchant collection flows where it doesn't fit) or overlooking PayNow Corporate entirely and defaulting to card acceptance for Singapore transactions that could be collected more cheaply via bank transfer.

PayNow P2P vs PayNow Corporate: The Core Distinction

PayNow (the P2P product) launched in 2017 and allows individuals to send money to other individuals using a phone number, NRIC/FIN (national identity number), or a PayNow proxy registered in their banking app. The sender initiates the transfer; no request or invoice flow is involved. Settlement is instant via the FAST real-time rail. This is the product Singapore residents use to split bills, pay for market purchases, and transfer to friends.

PayNow Corporate launched in 2018 as a distinct product for businesses. Key differences:

• Identifier: Businesses register their UEN (Unique Entity Number — Singapore's business registry number) as the PayNow alias, rather than a phone number or NRIC
• Initiating party: PayNow Corporate supports both push payments (payer-initiated, as in P2P) and pull-style flows where the merchant initiates a payment request that the payer approves
• API access: Participating banks (DBS, OCBC, UOB, and others) expose PayNow Corporate as an API product for corporate customers, enabling programmatic initiation, automated reconciliation, and real-time notification on payment receipt
• Reconciliation: PayNow Corporate transactions carry structured reference data (bill reference number, merchant reference) that enables automated matching against invoices and orders — a critical operational difference from P2P transfers where remittance information is free-form text

For operators, PayNow Corporate is the product that enables:

• A checkout flow where the merchant presents a QR code or payment link with a pre-populated amount and reference
• Real-time notification when the customer's payment lands
• Automated reconciliation against the order ID or invoice number
• Payment request notification to the customer (via bank's notification system)

PayNow P2P cannot reliably support any of these — the payer enters an amount and a free-form reference manually, and the receiving business has no API-based notification hook.

How PayNow Corporate Integrates with FAST and GIRO

PayNow Corporate sits on top of Singapore's existing interbank payment rails:

FAST (Fast And Secure Transfers) is Singapore's real-time rail, launched in 2014. FAST enables 24/7 near-instant interbank transfers between participating banks. PayNow Corporate uses FAST as its settlement rail — when a payer's bank sends a PayNow Corporate transfer, it routes through FAST and settles in real time to the recipient bank.

GIRO is Singapore's batch payment system — equivalent to ACH or SEPA Direct Debit — used for scheduled recurring payments (salary crediting, utility bill collection, subscription billing). PayNow Corporate can also be used as an alias layer over GIRO-initiated collections: a corporate entity can register its UEN for GIRO collection authorization, enabling customers to pre-authorize recurring debits via their banking app. This is the PayNow Corporate capability most relevant for subscription operators.

The architectural implication: for one-off payments, PayNow Corporate over FAST provides real-time settlement. For recurring payments, PayNow Corporate + GIRO provides a scheduled debit mandate model. For high-value B2B payments above FAST limits (FAST has a per-transaction limit of SGD 200,000), the MEPS+ high-value payment system handles settlement, though PayNow Corporate UEN routing still applies.

MAS SGFinDex: The Data Layer

SGFinDex (Singapore Financial Data Exchange) launched in 2020 and is operated by the Monetary Authority of Singapore (MAS). It allows Singapore residents to consent to sharing financial data across institutions — bank accounts, CPF data, insurance, and investments — via a centralized consent framework.

SGFinDex is relevant to operators in the following contexts:

• Financial management platforms: Apps that aggregate a user's bank balances and transaction history with user consent can use SGFinDex as the data access layer, rather than building per-bank open banking connections
• KYC and creditworthiness verification: Lenders and financial services operators can request SGFinDex data (with user consent) to verify income, account balances, and existing liabilities
• Tax and accounting tools: SGFinDex enables automated import of bank transactions into accounting software for SME users

SGFinDex does not support payment initiation — it is a read-only data sharing infrastructure. For operators needing payment initiation (the ability to initiate a transfer from the user's bank account), PayNow Corporate via bank API is the relevant capability.

Corporate bank API paths: DBS, OCBC, and UOB

There is no single, unified PayNow Corporate API. Each bank exposes PayNow Corporate through its own corporate channels, and most offer two integration surfaces — a web portal for operations staff and a programmatic API (or host-to-host file connectivity) for system integration. If your customers bank across DBS, OCBC, and UOB, a bank-direct strategy means integrating more than one of these; the capability is broadly equivalent, the implementations are not interchangeable.

What an operator should actually evaluate per bank, regardless of brand names:

• Initiation: can you generate a PayNow QR (or request) with a pre-filled amount and reference programmatically, and validate a UEN before paying out (PayNow lookup)?
• Receipt notification: does the bank confirm an inbound credit in near-real time — so your system learns of a payment without polling a statement — and via what mechanism (API confirmation, host-to-host, or portal)?
• Reconciliation data: do the payer name, amount, and your reference reach your system on receipt?
• Recurring: is there an electronic GIRO / direct-debit mandate for subscription collection?
• File vs API: can you submit bulk instructions by file (host-to-host) as well as single API calls, and what are the FAST batching and limit behaviours?

DBS offers two surfaces. DBS IDEAL is the corporate banking portal — UEN registration, PayNow Corporate operations, and reconciliation visibility (payer name, reference, and amount surface on receipt), with bulk instructions via file upload. DBS RAPID ("Real-time API by DBS") is the programmatic layer: a library of corporate APIs that includes PayNow payments, real-time collections, inward-credit confirmation, balance and transaction enquiry, and direct-debit authorisation. RAPID is the path for embedding PayNow collection and reconciliation into your own systems; IDEAL is the path for finance-team operations.

OCBC runs OCBC Velocity, its digital business-banking platform (PayNow for Business, collections, payments, role-based maker/approver access), and OCBC OneCollect, a collections product that issues a single QR accepting PayNow alongside other schemes and exposes an embeddable API for kiosks, apps, and checkout. OCBC was an early open-API bank in the region; confirm current developer-portal access through your relationship manager.

UOB runs UOB Infinity (digital corporate banking across cash management, supply-chain finance, and trade) and a separate UOB API Services offering with a self-service developer portal. UOB's API capabilities include PayNow payments and PayNow lookup, FAST payments and collections, balance and transaction enquiry, and electronic direct-debit authorisation (eDDA) setup — both the collection and the recurring-mandate primitives, programmatically.

Across all three, API and host-to-host access is relationship-gated: you contract for it through your corporate banking relationship rather than self-serving a public key, and exact capabilities, sandbox availability, and pricing should be confirmed with the bank.

ERP reconciliation and reference-field matching

The operational advantage of PayNow Corporate over a plain bank transfer is the reference. A PayNow Corporate QR can pre-fill both the amount and a bill or order reference, so the payer never types a free-form note — and that reference travels through FAST and lands in the recipient bank's transaction record. Combined with the payer name and amount surfaced on receipt, that gives you the three fields auto-reconciliation needs: who paid, how much, and against which invoice.

In practice the matching pattern is: issue the QR with your invoice or order ID as the reference, receive the inbound-credit confirmation from the bank channel, match the reference to the open invoice, and mark it paid. Where the bank confirms receipt in near-real time, you reconcile continuously rather than waiting for an end-of-day statement. Most ERP and accounting stacks — SAP, NetSuite, Xero and the rest — reconcile on exactly this key, a unique reference plus amount, so the integration work is mapping the bank's confirmation payload to your ledger's open-item key, not inventing a new matching model.

Two caveats operators hit. First, the reference only helps if it is populated and unique: a generic "payment" note or a reused order ID defeats auto-match, so generate a unique reference per request and make the QR the default payment path, since free-typed transfers lose the structure. Second, recurring collections are a different primitive — for subscriptions, the electronic GIRO mandate (eGIRO, or a bank's eDDA API) authorises scheduled pulls and reconciliation is mandate-driven rather than per-QR; the cross-rail subscription view covers that pattern. For the reconciliation-break playbook once volumes scale, see the PSP reconciliation failure runbook.

What PayNow Corporate actually costs

PayNow Corporate has long been marketed as near-free for collections, and that shaped a lot of operator assumptions. The accurate 2026 picture is more nuanced: collection pricing is set per bank and it is shifting. Some banks still waive inbound PayNow collection fees, often via multi-year promotions, while others have begun charging a small per-transaction receive fee on business collections. Outbound PayNow payments, API or host-to-host access, and bulk-file processing are priced separately, again per bank. There is no single published PayNow Corporate rate — so size your economics against your own bank's current pricing guide, not a blanket "it's free."

The structural cost picture, holding across banks:

• Bank-direct rail cost is low and roughly flat per transaction — you pay the bank's PayNow/FAST handling, not a percentage of value — which is why the model gets more attractive as transaction value rises. But "low and flat" is not always "zero," and the trend is toward small explicit receive fees.
• Aggregator MDR (Stripe, Adyen, Fiuu, HitPay) is a percentage of value — typically a fraction of a percent for PayNow acceptance — in exchange for one integration and unified reporting.
• Account and platform fees (corporate account, API onboarding, occasional minimums) sit underneath both and are easy to forget when modelling a low-value, high-count flow.

The takeaway: PayNow Corporate is still materially cheaper than card MDR for higher-value Singapore collections, but model it on a flat-fee-plus-build basis and verify the current per-transaction and API pricing with each bank you intend to collect through — the "free" assumption is decaying.

Bank-direct versus aggregator: the integration decision

Both paths reach PayNow Corporate; they trade different things.

Bank-direct (RAPID/IDEAL, Velocity/OneCollect, Infinity/API Services) gives the lowest marginal cost — flat rail pricing rather than a percentage — and the cleanest reconciliation data, straight from the bank that settled the payment. The costs are build and lock-in: you integrate against one bank's API surface, and if your customers pay from accounts across several banks, the direct advantage applies only to collections into that bank. It also depends on a corporate banking relationship and relationship-gated API access. Bank-direct suits operators with concentrated banking, meaningful Singapore volume, and the engineering capacity to build and maintain the integration.

Aggregator (Stripe, Adyen, Fiuu, HitPay) gives one integration spanning banks and payment methods, a unified dashboard and settlement report, and a fast path to live — in exchange for an MDR and a layer of abstraction between you and the rail. It suits platforms that want cards and PayNow behind a single API, that lack bank-API access, or that value time-to-launch and consolidated reporting over the last basis points of cost.

A reasonable default: start on an aggregator to ship PayNow acceptance quickly alongside cards, then move high-value or high-volume Singapore collection flows to bank-direct once the volume justifies the build and the per-transaction saving is real. Decide on three axes — your transaction economics (value × count), which bank(s) your customers actually pay from, and your reconciliation and engineering capacity — not on the headline fee alone.

When to Use PayNow Corporate vs Card Acceptance

The choice between PayNow Corporate and card acceptance in Singapore is primarily economic for larger transaction values and operational for smaller ones.

PayNow Corporate economics: low, flat bank-rail cost via bank-direct (now trending toward small per-transaction receive fees — see the cost section above) versus a fraction-of-a-percent aggregator MDR; either way, a percentage-free or low-percentage cost that beats card MDR as value rises.

Card acceptance economics:

• Visa/Mastercard consumer cards: approximately 1.5–2.5% MDR in Singapore
• Commercial/corporate cards: 2.0–3.0%+ MDR
• American Express: 2.5–3.5%+ MDR

The crossover point: At a transaction value of SGD 500 (~$370 USD), a 2% card MDR costs SGD 10; a 0.5% PayNow aggregator fee costs SGD 2.50. The absolute fee difference grows with transaction value. For B2B invoice collection above SGD 1,000, PayNow Corporate via bank API is materially cheaper than card acceptance and worth the integration complexity.

When cards win:

• Low average transaction values (under SGD 50) where the operational overhead of PayNow Corporate QR generation is disproportionate
• Consumer checkout flows where card UX (tap-to-pay, Apple Pay) is lower friction than bank transfer
• International customers who don't have Singapore bank accounts and cannot initiate PayNow transfers
• Merchant-initiated recurring billing where card-on-file with card network tokenization is the established flow

When PayNow Corporate wins:

• B2B invoice settlement — Singapore businesses paying other Singapore businesses
• High-value consumer transactions (electronics, travel, luxury goods) where card MDR is commercially significant
• Platform payins from Singapore-based registered businesses or sophisticated consumers
• Subscription billing via GIRO mandate where the recurring debit model fits the payment cadence

Practical Integration Architecture

For a Singapore-operating platform wanting to offer PayNow Corporate as a payment option alongside cards:

Step 1: Establish a Singapore corporate bank account with PayNow Corporate capability. DBS, OCBC, or UOB are the primary choices. All three require a Singapore-registered company (Pte Ltd) and standard KYC documentation. Account opening timelines: DBS 2–4 weeks, OCBC 1–3 weeks, UOB 1–3 weeks.

Step 2: Register your UEN for PayNow Corporate. Done through your bank's business banking portal. Your company UEN (from ACRA, Singapore's business registry) becomes the PayNow alias — payers can send to your UEN directly.

Step 3: Integrate the bank's PayNow Corporate API or use an aggregator. For in-house integration: build the QR code generation flow (amount + reference + UEN), set up the inbound payment webhook to receive real-time payment notifications, and build the reconciliation matching logic (notification reference → order ID). For aggregator path: Stripe Singapore or Adyen provides this in a pre-built integration.

Step 4: Build the checkout UX. The standard PayNow Corporate checkout flow presents a QR code that the customer scans with their banking app. On mobile, a deep link (paynow://...) opens the customer's banking app directly. Payment completes when the customer authenticates in their bank app. The merchant receives a webhook notification; the checkout page polls for status and shows confirmation.

What This Means for Operators

PayNow Corporate is underutilized by foreign operators entering Singapore. Most default to card-only acceptance because it's the path of least resistance via Stripe or Adyen's standard product. But for any operator with average transaction values above SGD 200 and a meaningful share of Singapore-resident business or sophisticated consumer customers, the MDR difference between PayNow Corporate and card acceptance is commercially significant at scale.

The direct bank API path (DBS/OCBC/UOB) requires a Singapore corporate banking relationship, which is a prerequisite for operating in Singapore anyway. Building PayNow Corporate QR into a Singapore checkout flow is a few weeks of engineering work that produces durable cost savings on every Singapore bank-transfer transaction.

For consumer checkout, the pragmatic approach is: offer PayNow Corporate QR as the primary option for high-value transactions (above a configurable threshold), with card as the universal fallback. Singapore consumers are familiar with PayNow and will use it when given the option, and adoption on the business side is near-universal — over 90% of Singapore businesses have adopted PayNow or SGQR. The underlying FAST rail processed roughly 500 million transactions worth about SGD 662 billion in 2024. Corporate transactions are a growing share of total PayNow volume.

Operators who treat Singapore as a "just add Stripe" market and don't build PayNow Corporate leave money on the table on every high-value Singapore transaction. The infrastructure is accessible, the bank APIs are mature, and the economics justify the integration cost at any meaningful Singapore payment volume.

For a side-by-side comparison of PayNow against Pix, UPI, SPEI, PromptPay, and four other real-time rails — MDR model, identifier architecture, cross-border readiness, and licensing path — see the Real-Time Payment Rails Comparison Matrix.