PayNow Corporate Fees, UEN Registration, and Bank APIs in Singapore

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.

UEN registration for PayNow Corporate: who qualifies and how

A UEN is Singapore's standard identifier for registered entities — administered by ACRA jointly with other issuance agencies including IRAS, the CPF Board, and Singapore Customs — and it does for a business what an NRIC does for an individual. Businesses and local companies already registered with ACRA, which is the large majority of registered entities, simply retain their existing ACRA registration number as their UEN; there is no separate UEN application to file.

That matters directly for one of the most common questions on this topic: sole proprietorships qualify. A sole proprietorship's ACRA Business Registration Number is its UEN, and it registers for PayNow Corporate the same way a Pte Ltd company does. Entity type doesn't gate eligibility — having a Singapore-issued UEN and a Singapore SGD current account does, and PayNow Corporate is open to companies, LLPs, sole proprietorships, government agencies, associations, and societies.

Registration itself is a bank-side action, not a separate government filing:

• DBS: log in to DBS IDEAL, open Applications, select PayNow & SGQR, choose the account, enter the UEN (add a 3-digit alphanumeric suffix if the business wants multiple PayNow proxies linked to different accounts), and submit — status shows "Pending Approval" until the bank confirms it.
• OCBC: through the OCBC Business App (Settings → Manage PayNow & SGQR) or OCBC Velocity (Tools → Manage PayNow & SGQR). Register the UEN without a suffix if the entity needs to receive government subsidies and payouts through it. Online registration completes immediately; the paper form takes up to 5 business days.
• UOB: through UOB Infinity or the UOB SME App — select "Manage/Register PayNow," submit the required details for approval, and the proxy is live once status shows "Registered."

Once registered, the UEN sits as an alias on top of the linked SGD current account, functionally the same role a phone number or NRIC plays for PayNow P2P — except the identifier is public business-registry data, which is also why it's businesses, not individuals, that are expected to publish it on invoices and storefronts for KYB-adjacent verification purposes.

PayNow Corporate vs PayNow QR / SGQR: these aren't competing products. SGQR is a unified QR-code label standard, developed by MAS and the Infocomm Media Development Authority, that consolidates multiple e-payment QR schemes — PayNow among them — into a single physical or digital QR so a customer scans one code regardless of which scheme they use to pay. A business registers its UEN for PayNow Corporate first; the resulting PayNow QR can then be one of the schemes bundled into an SGQR label alongside card and wallet QR codes. Several banks issue a handful of SGQR labels free on registration.

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.

PayNow vs GIRO vs FAST: which rail for which flow

These three names get conflated because PayNow Corporate rides on top of the other two rather than replacing them:

The practical rule: if the payer already has your bank account number and it's a one-off payment, FAST alone works without PayNow. PayNow Corporate earns its keep specifically where you don't want to publish bank account numbers (a UEN is safer to display publicly than an account number), where a pre-filled QR with an embedded reference beats a free-typed transfer, or where you're layering a recurring mandate — in which case GIRO is doing the settlement work underneath, with PayNow Corporate as the registration and reconciliation layer on top.

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: enable PayNow Corporate through DBS IDEAL — log in, Applications → PayNow & SGQR, register the UEN against a corporate account. The IDEAL portal itself carries no monthly platform charge; the fees section further down has what DBS publishes — and doesn't publish — on inbound pricing. IDEAL also covers 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: enable PayNow Corporate through the OCBC Business App (Settings → Manage PayNow & SGQR) or OCBC Velocity (Tools → Manage PayNow & SGQR), OCBC's digital business-banking platform with role-based maker/approver access. Inbound and outbound list pricing, and the current waiver dates, are in the fees section below. For collection-specific merchants, OCBC OneCollect issues a single QR accepting PayNow alongside other schemes (Alipay+, WeChat Pay, UnionPay, ShopeePay, DuitNow) with an embeddable API for kiosks, apps, and checkout, priced separately from Velocity's PayNow Corporate rates (also in the fees section).

UOB: enable PayNow Corporate through UOB Infinity or the UOB SME App — select "Manage/Register PayNow" and submit for approval; new registrations get four free SGQR labels. List pricing and the current fee waiver are in the fees section below. Beyond the portal, a separate UOB API Services offering provides a self-service developer portal; 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.

Fee figures as published by each bank's own pricing/product pages, retrieved 2026-08-20 — see Sources below. Pricing is promotional and bank-controlled; confirm current rates before modelling economics.

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.

PayNow Corporate fees: what it actually costs, by bank

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, it is shifting, and the "free" figures in circulation are mostly promotional waivers sitting on top of a non-zero list price — not a permanently zero rate. What follows is what each bank's own published pages say, dated to when we checked them, not a market-wide average.

As published by each bank (retrieved 2026-08-20):

• UOB — PayNow Payables Solutions page: outbound via FAST is SGD 0.50 per item and outbound via GIRO is SGD 0.40 per item (with a SGD 1.00 return fee); inbound via FAST is SGD 0.20 per transaction and inbound via GIRO is free at list price. UOB currently waives fees on all incoming PayNow Corporate transactions — FAST and GIRO alike — through 31 December 2028.
• OCBC — Business Pricing Guide: inbound PayNow is listed at SGD 0.20 per transaction, currently free under a promotion extended to 31 December 2028, though the guide says OCBC reserves the right to charge SGD 0.20 for certain use cases and industries (retrieved 2026-09-17); outbound PayNow is the applicable FAST (SGD 0.50/transaction) or GIRO (SGD 0.20/item) fee plus a SGD 0.20 lookup fee, with the lookup fee also waived to the same date. OCBC's collection-focused OneCollect product prices PayNow QR collection separately, at 0.25% of funds collected, deducted monthly, with the first 3 months free for SME customers (operating receipts ≤SGD 100 million or ≤200 employees); non-PayNow QR schemes on the same product (Alipay+, WeChat Pay, UnionPay, ShopeePay, DuitNow) are 1.50%, deducted daily, with no waiver.
• DBS — PayNow Corporate product page: states that inward PayNow "will remain free until end of 2025." That page does not publish a rate for periods after 2025, and we could not confirm a current inbound figure from DBS's public pages as of this retrieval. We are not carrying forward a guessed number: if you bank with DBS, get the current rate from your relationship manager or the corporate pricing guide rather than assuming it matches OCBC and UOB's 2028 waivers.

The structural cost picture, holding across banks regardless of the exact promotional rate:

• Bank-direct rail cost is low and roughly flat per transaction — a fixed per-item fee (list prices above run SGD 0.20–0.50), not a percentage of value — which is why the model gets more attractive as transaction value rises. The trend across UOB and OCBC is toward small explicit list prices sitting behind long-dated promotional waivers, not toward permanently free.

• Aggregator collection products (OCBC OneCollect at 0.25% for PayNow) and third-party MDR are priced mainly as a percentage of value, in exchange for one integration, a single QR across schemes, and unified reporting. The published standard PayNow rates of the providers named in this guide differ widely (retrieved 2026-09-17):

  • Stripe: 1.3% per successful PayNow payment.
  • Adyen: 1.30% plus Adyen's fixed per-transaction processing fee.
  • HitPay: online, 0.65% + S$0.30 on payments of S$100 and above, or 0.9% (minimum S$0.20) below S$100; in person, 0.4% (minimum S$0.10). HitPay adds a further 0.2% when the payment comes through its own business software (payment links, invoicing, online store, point of sale, recurring billing) and 0.2%–0.5% through plugins.
  • Fiuu: we found no published Singapore PayNow rate, so get a quote.

  These are list prices. Stripe says it charges tax on certain services depending on a business's location and tax status, HitPay offers custom pricing above a volume threshold, and your own contract is what counts.

• 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.

PayNow Corporate vs personal PayNow, on cost: personal PayNow transfers between individuals carry no transaction fee under the ABS-run scheme, and businesses receiving PayNow Corporate payments are prohibited from surcharging the paying customer for using it. The fee, where one exists, sits between the receiving business and its own bank — the corporate account and channel fees above — not between the business and its customer.

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, price in the possibility that a 2028 waiver doesn't get renewed, and verify the current per-transaction and API pricing with each bank you intend to collect through before committing to "it's free" in a business case.

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) usually gives the lowest cost per payment and the cleanest reconciliation data, straight from the bank that settled the payment. Pricing is a flat per-item fee rather than a percentage, and UOB and OCBC currently waive inbound fees, subject to conditions; OCBC's OneCollect QR product is the exception, at 0.25% of value. 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 per-payment saving of collecting bank-direct.

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 economics: a low, flat bank-rail cost via bank-direct (a SGD 0.20 list price per inbound payment at UOB and OCBC, currently waived subject to conditions — see the cost section above), or an aggregator fee that is mostly a percentage of value: between 0.25% and 1.3% on the published standard rates above, plus a fixed charge or minimum fee at some providers, and before add-on fees.

Card acceptance economics (published standard rates for domestic cards, retrieved 2026-09-17):

• Stripe: 3.4% + S$0.50
• HitPay: 2.8% + S$0.50 online and 2.5% + S$0.50 in person
• Adyen: interchange and scheme fees passed through, plus a published 0.60% markup (Visa) and Adyen's fixed processing fee, so there is no single all-in figure to compare

Negotiated contracts can differ from these list prices for both cards and PayNow, so compare using your own rates.

A worked example at list prices. For a S$500 domestic online payment, on each provider's published standard rates (retrieved 2026-09-17; before any tax, add-on fees or negotiated pricing):

At both Stripe and HitPay, PayNow costs less than a domestic card payment at every payment size on these rates. At Adyen the published rates do not settle it: its PayNow fee (1.30%) is higher than its Visa card markup (0.60%), so which costs less depends on each card's interchange and scheme fees. Because an aggregator's percentage fee grows with the payment while a bank's per-item fee does not, the gap between aggregator and bank-direct PayNow widens as the payment grows. Bank-direct is not the cheapest at every size, though: at list prices, Stripe's 1.3% of S$10 is S$0.13, below a S$0.20 flat bank fee (while the UOB and OCBC waivers last, that bank fee is zero). The example is a per-payment comparison only — it leaves out account fees, the cost of building and running a bank integration, and any difference in how many customers complete payment. For B2B invoice collection above S$1,000, the per-payment gap in bank-direct PayNow Corporate's favour is large on these rates; whether it justifies the integration work depends on your volume.

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 (DBS IDEAL, OCBC Velocity/Business App, or UOB Infinity/SME App — the exact steps for each are in the registration section above). Your company UEN (from ACRA, Singapore's business registry — sole proprietorships and LLPs qualify the same as Pte Ltd companies) becomes the PayNow alias; payers can send to your UEN directly, without your bank account number.

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) — each bank exposes its own webhook contract rather than a shared one, a constraint the A2A merchant acceptance architecture reference covers alongside how it compares to Pix, UPI, PromptPay, and SEPA Instant. 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 can produce durable cost savings on Singapore bank-transfer transactions.

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 high-value Singapore transactions. The infrastructure is accessible, the bank APIs are mature, and at meaningful Singapore payment volume the per-payment savings can justify the integration cost.

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.