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

Most operators building payment flows for Singapore know PayNow as an instant transfer to a phone-number or NRIC/FIN alias. PayNow Corporate lets an eligible entity register its UEN as the payee alias. Provider-specific QR, API and reporting products can make that useful for collections and reconciliation, but the UEN registration itself is not a universal payment-request API or a GIRO mandate.

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 for entities. Key differences and provider-dependent additions:

• 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: the payer chooses the entity's UEN or scans a PayNow QR and confirms a transfer. A provider may offer a separate request or checkout product; check its terms rather than assuming a scheme-wide merchant pull.
• API access: some bank and PSP corporate products expose payment, QR and receipt APIs. The available method, eligibility and notification payload are provider-specific.
• Reconciliation: a provider's QR or collection product may prefill a bill reference and return it with a credit notification. A manually entered UEN transfer need not carry a unique invoice reference; verify the field actually received.

For an operator, a selected provider implementation may offer a QR with prefilled amount and reference, a payment notification and a reconciliation payload. Test those fields end to end before promising automatic invoice matching. PayNow P2P is an individual alias product and should not be used as a substitute for a business collection account.

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: a sole proprietorship can use its UEN. A sole proprietorship's ACRA Business Registration Number is its UEN. ABS describes PayNow Corporate for entities with a Singapore-issued UEN linked to a Singapore bank or e-wallet account at a participating bank or major payment institution. A SGD current account is a requirement of some bank products, not a universal scheme requirement. Confirm which account types your provider accepts before onboarding.

Registration is through the participating bank or major payment institution, not a separate government filing. The following bank-specific paths are examples:

• 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 is an alias for the eligible account linked by that provider. A bank may link it to a SGD current account; ABS also describes eligible e-wallet accounts. The payer can use the UEN without needing the account number. Check the displayed recipient name and your provider's reconciliation fields rather than treating the public UEN alone as a KYB check.

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.

PayNow Corporate can use different bank routes

The ABS PayNow description describes the instant FAST route. UOB's corporate PayNow page also offers payments to a registered PayNow recipient via GIRO. That is a batch credit option for corporate payers, not a recurring debit mandate. Registering a PayNow UEN does not authorize anyone to pull funds from an account.

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. A PayNow Corporate payment sent via FAST reaches the recipient bank in real time, subject to the provider's processing.

GIRO is a batch rail for direct credits as well as authorized direct debits. UOB says a corporate PayNow payment sent via GIRO takes 2–3 business days to reach the recipient, and only corporates can choose that route. For recurring debit collections, ask the bank separately about eGIRO mandate setup and fees; a payer has not authorized recurring debits by paying a PayNow QR once.

For a payment above the applicable FAST limit, check whether your bank supports corporate PayNow via GIRO and whether its batch timing fits. UOB states a S$200,000 FAST limit for PayNow payments and no maximum for its GIRO route; another bank or channel may impose different limits. If you need a separate high-value route such as MEPS+, do not assume it accepts the same PayNow UEN identifier.

PayNow, FAST and GIRO: service versus rail

These names are easy to conflate because a bank can offer all three products through one business channel:

The practical distinction: FAST and GIRO describe routes, while PayNow lets a payer address a registered recipient by alias instead of account number. A GIRO debit still needs its own authorization. Match the bank's route to the collection flow and verify timing, limits and fees separately.

Corporate bank API paths: DBS, OCBC, and UOB

There is no single, unified PayNow Corporate API. Participating institutions have different portals, APIs and file channels. A merchant using one receiving bank does not need an integration with every payer's bank; it does need to integrate the receiving provider's reporting or notification channel if it wants automated reconciliation. Capabilities vary and are not interchangeable.

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

• Initiation: can this product generate a PayNow QR with amount and reference, and does it offer a separate payer-approved request? Do not assume the latter is part of UEN registration.
• 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: which payer, amount and reference fields actually reach your system, including after a manually entered UEN transfer?
• 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 offers operations and reconciliation views, with bulk instructions via file upload; verify which payer and reference fields appear for the specific collection channel. DBS RAPID ("Real-time API by DBS") is a corporate API library including PayNow payments, collections, inward-credit confirmation, balance and transaction enquiry, and direct-debit authorisation as separate capabilities. Confirm access and payloads before designing auto-match.

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.

UOB and OCBC schedules rechecked 2026-10-28; DBS remains the dated 2026-10-02 observation. Pricing is product-specific and promotional; confirm your provider's current schedule before modelling economics.

ERP reconciliation and reference-field matching

The reconciliation opportunity is a provider-supported QR or collection flow that prefills an amount and bill reference. Check whether the chosen bank or PSP carries that reference into the recipient record. A manually entered UEN transfer may not include the invoice key, and a displayed QR alone does not prove that a matching credit arrived.

Where the provider supports it, issue a QR with a unique invoice ID, wait for a confirmed credit, and match the returned reference and amount to the open invoice. If the provider reports the credit later or omits the reference, hold the invoice for statement reconciliation or manual exception handling. Verify the actual payload before promising immediate auto-match.

The reference only helps if it is present and unique. A reused ID or generic payment note defeats auto-match, while an ordinary payer-entered transfer may omit the desired key. Recurring collections are a separate primitive: an electronic GIRO mandate (eGIRO, or a bank's eDDA API) authorizes scheduled debits rather than turning a PayNow QR into a pull. The cross-rail subscription view covers that pattern. For reconciliation exceptions, see the PSP reconciliation failure runbook.

Worked receipt ledger: paid is not the same as allocated

Fictional merchant ledger, not a bank API schema or a PayNow scheme rule. Start with three open invoices A, B and C, each for S$500. Assume the incoming credits below have been confirmed through the chosen account/source, with reliable unique provider transaction identifiers scoped to that account/source. R1-R4 are our local labels, not promised provider field names. Distinguish another delivery of an existing event from a distinct incoming credit.

A redelivery is ignored for financial counting only after its identity and payload agree. A conflicting amount, currency or reference under the same identifier requires investigation against the provider/account record; blindly dropping it as a duplicate can hide a real discrepancy. Keep the account/source with the identifier so two providers' local IDs cannot collide.

Closing reconciliation: distinct observed receipts are S$300 + S$200 + S$500 + S$50 = S$1,050. Allocate S$500 to A; leave S$550 unallocated/excess (R3 S$500 plus R4 S$50). A is paid; B and C each remain open at S$500, or S$1,000 combined. Thus receipts S$1,050 = invoice allocations S$500 + held credits S$550. The repeated delivery of R1 adds nothing. Neither the unknown S$500 nor the excess S$50 automatically belongs against B or C.

Resolve R3 with validated remittance/invoice information and the applicable customer/account records, checked against receipt confirmation. Resolve R4 by confirming the intended purpose with those records and following the merchant's excess-credit process; its arrival is not an automatic refund instruction. To resolve an identity conflict, request the account-scoped transaction record and delivery history before changing the ledger. The exception runbook's investigation steps help assemble supporting evidence.

These are observed receipts and invoice allocations, not a statement of settlement finality, withdrawable balance or funds available for payout. Verify those separately under the chosen provider's account and settlement terms. The method illustrates controlled allocation, not a guarantee that every PayNow provider supplies an immutable ID or supports automatic matching.

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.

UOB and OCBC schedules rechecked 2026-10-28; DBS remains the 2026-10-02 observation:

• 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 reserves the right to charge SGD 0.20 for certain use cases and industries; 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 of fees waived on the current pricing guide; confirm governing product terms; 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: still states that inward PayNow "will remain free until end of 2025." The page does not state a rate for later periods. If you bank with DBS, request its current schedule rather than assuming that an expired public promise remains in force or that 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% + S$0.13 per transaction on the Singapore PayNow page (checked 27 October 2026).
  • 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.

Compare actual bank-direct PayNow charges with the all-in card and PSP quotes for your transaction mix. A low per-item bank fee can be attractive at higher values, but account, API, implementation and operating costs still matter. Include the possibility that a waiver is not renewed rather than treating the rail as permanently free.

Bank-direct versus aggregator: the integration decision

For a numerical comparison, enter each route's actual fee schedule in the quote-cost calculator. Keep bank and checkout fees separate, and account for engineering and reconciliation work outside the modeled processing charges. A lower quoted payment fee does not establish lower total operating cost.

Both paths offer PayNow acceptance, with different customer contracts, receipt records and settlement terms.

Bank-direct (RAPID/IDEAL, Velocity, Infinity/API Services) can offer a low flat per-item collection fee and reconciliation data from the receiving bank. UOB and OCBC currently waive inbound fees, subject to conditions; OCBC's OneCollect QR product is a differently priced percentage-fee offering. The costs include account and integration requirements: you build against the receiving bank's channel and confirm its API eligibility and charges. Payers can still come from other participating banks; the integration is tied to the receiving provider, not to every payer's bank.

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), the receiving bank or provider's account, API eligibility and actual payer coverage, 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 Visa-specific 0.60% component and S$0.13 fixed processing fee (checked 27 October 2026), 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):

In the S$500 example, PayNow costs less on both quoted schedules. Fixed charges, minimums and add-ons prevent extrapolating one ticket-size calculation into a universal all-value comparison. At Adyen the published rates do not settle it: its PayNow fee (1.30%) is higher than its published Visa component (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 invoicing, compare the per-payment gap with account, implementation and operating costs; no universal ticket-value threshold establishes the best route.

When cards win:

• Low-value checkout where measured completion and operating overhead outweigh the fee saving
• 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
• Repeat invoices where customers initiate each PayNow payment; use a separate GIRO mandate if automatic debits are required

Practical Integration Architecture

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

Step 1: Choose a participating institution and eligible account. ABS lists both banks and major payment institutions and describes PayNow Corporate linkage to a Singapore bank or e-wallet account. DBS, OCBC and UOB are bank examples, each with its own onboarding and account requirements. Confirm the account type, business documents, API access and fees directly; a Pte Ltd company is not the only eligible entity type, and opening timelines are not fixed scheme rules.

Step 2: Register your UEN for PayNow Corporate. Use the participating institution's portal; the bank examples above are DBS IDEAL, OCBC Velocity/Business App and UOB Infinity/SME App. A sole proprietorship can use its ACRA-issued UEN, subject to the chosen provider's account rules. Payers can then select the registered UEN without knowing the linked account number.

Step 3: Verify the chosen provider's collection interface. Confirm whether it can issue a QR with amount and reference, how it reports a received payment, and whether the reference survives into the bank credit record. Build matching against the actual fields; do not presume that every bank exposes a webhook or the same payload. An aggregator can supply a different pre-built collection interface, with its own pricing and settlement flow. The A2A acceptance architecture reference covers the broader design.

Step 4: Confirm the payment before fulfilling. A PayNow QR can let the payer complete a transfer in a participating app. The merchant should confirm the credit through the selected bank or PSP's reliable notification or account record before marking an order paid. A browser redirect, displayed QR or unverified deep link is not itself payment confirmation.

What This Means for Operators

For Singapore collections, compare bank-direct PayNow with actual PSP and card quotes on your transaction mix. Ticket value alone does not establish savings, implementation cost or completion outcomes.

The direct bank API path requires the receiving bank's account and API eligibility; an MPI or PSP route has different access and settlement terms. Estimate integration work from that provider's QR, notification and reconciliation interfaces. No scheme-wide build time or savings figure follows from the UEN alone.

For consumer checkout, test PayNow alongside cards on eligible Singapore traffic rather than imposing a universal transaction-value threshold. The fee difference may favor PayNow on larger tickets, while completion, customer preference and refund operations also matter. Measure conversion and actual all-in cost on your own mix.

The decision is a quote and workflow comparison: bank-direct PayNow, an MPI account or a PSP checkout product may suit different businesses. Confirm the account requirement, how a credit is reported, fee and settlement schedule, and the expected conversion before choosing a route.

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.