InstaPay and PESONet: The Philippines' Dual Real-Time Rail Architecture

The Philippines has two national payment rails, and they are not interchangeable. InstaPay handles real-time, low-value interbank transfers 24/7. PESONet handles batch-cleared, higher-value transfers on a scheduled basis. Both use BancNet as the ACH operator, governed by the Philippine Payments Management Inc. (PPMI) — the BSP-recognized Payments Management Organization — and together form the backbone of the National Retail Payment System (NRPS) that the BSP launched in 2018.

Most operators working with the Philippine market interact with GCash or Maya rather than the underlying rails directly — understanding how global payments infrastructure is structured in this market is the essential foundation — but understanding how InstaPay and PESONet work, who can access them, and how the dominant wallets sit on top of them is essential for building payment flows that are both cost-efficient and operationally resilient.

The NRPS Framework

The BSP's NRPS was a deliberate structural intervention. Before 2018, interbank retail payments in the Philippines were slow (transfers could take 1–3 business days), expensive (fees of PHP 50–200 per transfer), and bank-hours dependent. The BSP mandated the creation of two Automated Clearing Houses (ACHs) to address this: one for real-time low-value transactions, one for batch high-value transactions.

The two rails have different ACH operators, which is routinely got wrong: BancNet operates InstaPay and the Philippine Clearing House Corporation (PCHC) operates PESONet. The two merged on 1 June 2026 into Payments Network of the Philippines Inc. (PNPI) — BancNet is the surviving legal entity — but both brands are retained and remain operationally distinct per rail. while PPMI provides governance and oversight as the BSP-recognized Payments Management Organization. For operators benchmarking InstaPay against other real-time rails, a comparison of Pix, UPI, SPEI, and PromptPay places the Philippine architecture in regional context. BancNet is the Philippines' existing interbank ATM network consortium — a cooperative owned by its member banks — making it the natural technical operator for the new infrastructure. Every bank participating in the NRPS connects to BancNet and must support both InstaPay and PESONet.

InstaPay: Architecture and Limits

InstaPay is the Philippines' real-time rail. Key parameters:

• Speed: Real-time, typically under 30 seconds
• Availability: 24/7/365
• Transaction cap: PHP 50,000 per transaction (~$870 USD)
• Fees: In flux, and the mechanism matters more than the number. BSP froze InstaPay/PESONet fee changes from December 2021; under that freeze charges varied by institution rather than sitting at any single regulated rate. BSP Circular No. 1238, issued 17 June 2026 with compliance required by 4 July 2026, lifted the moratorium and replaced it with a cost-based standard: fees must be reasonable, fair, transparent and commensurate with underlying expenses, and inter-bank charges must not be materially higher than intra-bank ones. Competitive pressure then pushed most major banks to waive consumer transfer fees entirely by mid-July 2026 — but that is a commercial outcome, not a BSP mandate. There is no zero-fee rule to rely on, and fees can return where a provider can justify them on cost. Verify per institution
• Participants: Roughly 95 InstaPay and 124 PESONet participants as of end-July 2026 — note PESONet's is the larger network, which the previous "70+" figure obscured by giving one number for both. Counts move monthly; pull BSP's current participant list rather than quoting these

InstaPay routes via account number (typically a 16-digit account number or, for EMIs, a mobile number or email alias). The sender cannot simply reverse an authorised transfer, but calling this a no-recall environment is wrong and has been since 2025. The Anti-Financial Account Scamming Act (AFASA, July 2024) and BSP Circular No. 1215 of 30 May 2025 let supervised institutions freeze suspicious or disputed funds for up to 30 calendar days without a court order, and the InstaPay/PESONet Dispute Resolution Manual requires the sending bank to issue an Urgent Recall Request to the receiving bank within two hours of a fraud report. Model it as a freeze-and-recall regime with tight timers, not as irreversibility — the fraud implications are still real and operators should model them, but model the timers rather than assuming finality, much as operators processing India’s UPI must account for that rail’s similarly irrevocable confirmation model.

The PHP 50,000 cap applies to standard consumer InstaPay and remains in force. Since 29 July 2026 there is a second option: BSP and PPMI launched InstaPay for Business, carrying a PHP 500,000 per-transaction limit for registered business accounts, alongside Direct Debit PH and InstaPay Cash-In. That materially changes the analysis below, which assumed the 50,000 ceiling was the only path. On standard consumer InstaPay, a merchant accepting a PHP 60,000 payment by bank transfer cannot process it as a single InstaPay transaction — it would require two transactions or routing via PESONet. For e-commerce platforms with high average order values (travel, electronics, B2B procurement), this cap means InstaPay alone is insufficient.

InstaPay's QR Ph Integration

The BSP launched QR Ph in 2019 as the national QR payment standard for the Philippines. QR Ph encodes InstaPay and PESONet routing information into an EMV-compliant QR code. In practice, QR Ph for merchant payments routes through InstaPay (the real-time rail) because merchant transactions are overwhelmingly below the PHP 50,000 cap.

GCash and Maya both support QR Ph scanning, meaning a QR Ph code displayed at a merchant is scannable from either app. However, QR Ph for merchant acceptance is not yet ubiquitous — GCash and Maya each also maintain proprietary QR codes that route to their own internal networks rather than through the InstaPay rail. The proliferation of QR standards (QR Ph for bank accounts, GCash QR, Maya QR, and Visa/Mastercard QR) creates the same multi-QR problem that Indonesia solved with QRIS and that Vietnam is still dealing with — Thailand pre-empted this by mandating a unified PromptPay QR standard from the outset.

PESONet: Batch Clearing for High-Value Flows

PESONet is a batch ACH for electronic fund transfers without a per-transaction cap. Key parameters:

• Settlement: Three windows per business day — 10:00, 13:00 and 16:00 — under the PESONet 3MBS (Three Midday Batch Settlement) enhancement live since 1 August 2024. Beat the window and funds credit the same banking day; miss it, or send on a weekend or holiday, and settlement moves to the next banking day. This reference previously said two windows, which was already out of date when it was written. Original text for reference: next-day settlement for afternoon batch)
• Transaction limit: No cap — suitable for corporate payments, payroll, large invoice settlement
• Fees: Lower than pre-NRPS wire transfers. The same BSP Circular 1238 cost-based regime applies here as to InstaPay; PaymentBrief does not publish a per-transaction figure, because charges are set per institution and moved sharply in mid-2026
• Availability: Business hours only (not 24/7); not available on public holidays

PESONet is the appropriate rail for payroll disbursements, B2B invoice payments, government benefit disbursements, and any transaction above PHP 50,000. The batch nature means it lacks the real-time confirmation of InstaPay — senders and recipients need to account for the clearing window in their reconciliation flows.

For operators disbursing to large recipient pools (gig economy platforms, insurance payouts, government transfers), PESONet is the standard mechanism. BSP has also designated PESONet as the rail for government-to-person (G2P) disbursements, including the Philippines' Pantawid Pamilyang Pilipino Program conditional cash transfers.

GCash and Maya: The Wallet Layer

GCash (operated by G-Xchange Inc. under Mynt — ownership per Mynt's 2026 IPO prospectus is roughly Globe Telecom 33.8%, Ant Group entities 32.4%, AM 50 Ventures 13.0%, with Ayala Corporation holding around 6.5% indirectly) reports approximately 90 million registered users and, per Mynt's SEC IPO prospectus, 39.1 million monthly active users for FY2025 and 40.4 million as of March 2026. The gap matters: an "81 million active" figure circulates widely but is GCash's own unaudited marketing claim, and the company's own filed disclosure puts monthly actives at under half that. Registered users are not actives, and neither is "nearly the entire Filipino adult population". Maya (formerly PayMaya, now the banking and fintech arm of Voyager Innovations, backed by PLDT) reports over 90 million registered users on 2026 IPO-related disclosures. The widely-repeated 50-million figure is a June 2022 milestone and understates current scale by roughly half. Together they are not competitors in the way Amazon and Walmart are competitors — they serve overlapping but distinct demographics, and both are growing.

GCash and Maya are both EMIs licensed by the BSP, and both sit on top of the InstaPay and PESONet rails for bank-linked transactions. When a GCash user sends money to a BDO bank account, the transfer routes through InstaPay (if below PHP 50,000) or PESONet (above the threshold). When a Maya user receives a salary disbursement from an employer, it arrives via PESONet.

The closed-loop distinction matters: GCash-to-GCash transfers are internal (no InstaPay routing, no external fee); GCash-to-bank transfers use InstaPay or PESONet. Maya-to-Maya transfers are similarly internal. This means that for operators wanting to disburse to a mix of GCash and bank account recipients, they need access to both the wallet's API (for direct GCash/Maya disbursements) and to InstaPay/PESONet (for bank account disbursements).

GCash's Market Dominance and Platform Lock-In

GCash's 94 million users represent a payment acceptance problem and opportunity simultaneously. Any Philippine e-commerce operator or platform not accepting GCash is excluding a payment method used by the majority of the country's digitally active population. But GCash's dominance also creates concentration risk — GCash has experienced notable outages that left merchants unable to accept payments for hours at a time.

GCash's merchant MDR for its own QR acceptance is commercially negotiated and varies by merchant category and volume; PaymentBrief does not publish a rate, because the figure previously carried here could not be traced to a source. For context, retrievable QR Ph person-to-merchant rates cluster in the low single digits rather than at any single published number. For operators, the practical question is whether to integrate GCash directly (via GCash's merchant API, available to licensed merchants) or through an aggregator like 2C2P or PayMongo that provides GCash access bundled with card and bank transfer acceptance.

Access Requirements: EMI Licensing vs Bank Partnership

Foreign operators wanting to access InstaPay and PESONet directly — not through GCash or an acquirer — face a licensing requirement. BSP mandates that InstaPay and PESONet participants must be either:

1. A BSP-licensed bank (commercial, thrift, or rural bank with appropriate BancNet membership)
2. A BSP-licensed EMI (Electronic Money Issuer — the non-bank category covering digital wallets and payment companies)

EMI licensing for non-banks requires:

• Minimum paid-up capital of PHP 100 million (~$1.74 million USD) for basic EMI
• Local corporate entity (100% Filipino ownership or with foreign ownership under relevant investment laws — financial services generally limited to 40% foreign ownership without special approval)
• Compliance with BSP's technology risk management framework
• AML/KYC program meeting AMLC standards
• Timeline: typically 12–24 months from application to license

Bank partnership model: Foreign operators typically access InstaPay and PESONet through a BSP-licensed bank that acts as the settlement participant. The operator integrates with the bank's payment API; the bank processes the InstaPay/PESONet transactions on the operator's behalf. Major banks with well-documented payment APIs include BDO, BPI, UnionBank (which has positioned itself as the most API-forward Philippine bank), Landbank, and Metrobank.

Aggregator model: Payment aggregators — PayMongo (Philippines-based), 2C2P (regional), Xendit (regional, with Philippines operations) — provide access to InstaPay via bank transfer acceptance, GCash, Maya, and cards through a single integration. This is the fastest path to market for most foreign operators and avoids the licensing overhead.

Operator Integration Paths

For payment collection (accepting payments from Philippine customers):

The practical stack for most operators is: card acceptance (acquirer via Stripe/Adyen/2C2P) + GCash acceptance (direct or via aggregator) + bank transfer via InstaPay (via aggregator or direct bank API). This covers >95% of payment methods used by Philippine consumers for online purchases.

QR Ph merchant acceptance is growing but has not yet displaced proprietary wallet QRs. For in-person acceptance, displaying both a QR Ph code and separate GCash/Maya QR codes is currently the standard practice, though BSP has stated an intention to rationalize this.

For disbursement (paying out to Philippine recipients):

InstaPay for individual disbursements under PHP 50,000 (gig worker payouts, insurance claims, marketplace seller settlements); PESONet for payroll and bulk disbursements. Both require a Philippine bank account relationship or an EMI license.

For operators disbursing to GCash wallets specifically — a common requirement for platform businesses in the Philippines given GCash's penetration — GCash offers a disbursement API that routes directly to GCash wallets without going through InstaPay. This is faster and has no PHP 50,000 cap for outbound disbursements to GCash. The trade-off is exclusivity: you can only disburse to GCash accounts via this mechanism, not to bank accounts.

What This Means for Operators

The Philippines' dual-rail architecture is well-designed for its intended use cases: InstaPay for the real-time consumer payments that dominate daily commerce, PESONet for the high-value and bulk flows that require higher transaction limits and lower per-unit costs. The BSP has been consistent in its infrastructure investment and mandate enforcement, which gives operators more confidence in the rail's longevity than in markets where real-time payments are operator-led rather than regulator-mandated.

The practical challenge is not infrastructure quality — it's access complexity. A foreign operator wanting to accept InstaPay needs either an EMI license or a bank partner; accepting GCash requires a separate agreement; accepting Maya requires another. The aggregator model resolves this but at a cost that may not be justified for operators with high volume and thin margins.

The medium-term structural question is whether QR Ph adoption accelerates to the point of displacing proprietary wallet QRs. If BSP enforces QR Ph as the mandatory standard — as Indonesia's central bank did with QRIS — the multi-QR problem disappears and the acceptance integration simplifies dramatically. Watch for BSP circulars on QR standardization as the leading indicator.

For operators entering the Philippine market in 2026, the recommended path is: start with an aggregator for speed to market, build a direct bank partnership once volume justifies the integration cost, and model the EMI licensing decision based on whether you need to hold user funds rather than just pass transactions through.

For a side-by-side comparison of InstaPay against Pix, UPI, SPEI, PromptPay, PayNow, NAPAS 247, and DuitNow — MDR model, identifier architecture, cross-border readiness, and licensing path — see the Real-Time Payment Rails Comparison Matrix.