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 webhook callbacks 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.

Integrating PayNow Corporate via Bank APIs

PayNow Corporate’s API access is bank-specific — there is no universal PayNow Corporate API. Each bank exposes its own PayNow Corporate API with somewhat different implementation, though the core functionality is consistent.

DBS PayNow Corporate API: DBS is Singapore’s largest bank (approximately 40% of retail banking market share) and has the most developed PayNow Corporate API for corporate customers. The DBS API supports:

• Real-time inbound payment notification webhooks when a customer pays to the UEN
• Payment status query
• PayNow QR code generation with pre-populated amount and reference
• GIRO direct debit mandate management

Access requires a DBS corporate bank account and API agreement. DBS’s developer portal (developers.dbs.com) provides documentation and sandbox access.

OCBC and UOB: OCBC and UOB also expose PayNow Corporate APIs for their corporate customers. Coverage is comparable to DBS for core payment notification and QR generation. For operators with existing banking relationships at OCBC or UOB, the PayNow Corporate API access is available through those relationships without requiring a DBS account.

Third-party integration paths: For operators who don’t want to build directly against bank APIs, payment aggregators operating in Singapore provide PayNow Corporate access:

• Stripe Singapore: Supports PayNow acceptance (via PayNow Corporate QR) as a payment method alongside card acceptance
• Adyen Singapore: PayNow Corporate QR and bank transfer acceptance in the Adyen platform
• Fiuu (formerly Razer Merchant Services): Singapore-based aggregator with PayNow Corporate support
• HitPay: Singapore-focused SME payment platform with PayNow Corporate QR integration

The aggregator path adds a fee layer (typically 0.3–0.8% of transaction value for PayNow acceptance via aggregator) but reduces integration complexity and provides unified settlement reporting across payment methods.

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:

• Settlement: effectively zero cost at the bank level (interbank transfers in Singapore are not charged per-transaction to businesses above baseline account fees)
• Via aggregator: 0.3–0.8% MDR
• Direct bank API: near-zero marginal cost per transaction (monthly account fees apply)

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 — 80% of consumers and businesses in Singapore use PayNow as of 2025, and FAST (the underlying rail) processed 500 million transactions worth SGD 662 billion in 2024 (MAS Payment Statistics, 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.