QRPH Collection Services: How International Businesses Collect Payments in the Philippines
Foreign companies that want to sell into the Philippines quickly discover that credit cards are not the default checkout method the way they are in many other markets. Filipino consumers overwhelmingly prefer mobile wallets and QR codes, and the national standard that ties all of those wallets together is QRPH. For a business entering this market, QRPH Collection Services are the fastest way to accept that preferred payment behavior without negotiating a separate technical integration with every bank and e-wallet operating in the country.
This article explains what QRPH actually is, why it matters specifically for a foreign business rather than a domestic one, how collection through QRPH works at a technical level, and what a BSP-licensed payment gateway is actually doing behind the scenes when it offers QRPH as a collection channel.
What QRPH Is, and Why It Exists
QRPH (QR Ph) is the Philippines' national QR code standard, developed under the Bangko Sentral ng Pilipinas' (BSP) National Retail Payment System framework. Before QRPH, each bank and e-wallet issued its own proprietary QR code format, so a merchant who wanted to accept scans from multiple wallets had to display multiple codes, or integrate separately with each provider. QRPH standardizes the code structure, based on an EMVCo-derived specification, so that a single code can be read and processed by any participating financial institution.
In practice this means a shopper can open whichever wallet or banking app they already have installed, point the camera at one QR code, and the payment routes correctly regardless of which bank or wallet issued it. The settlement mechanics behind that single code are where the real complexity sits, and how QRPH differs from InstaPay and PESONet is worth understanding before choosing how to collect.
Why QRPH Collection Matters for a Foreign Business Entering the Philippine Market
For a company based outside the Philippines, the practical problem is reach, not technology. The wallet landscape is fragmented across several major e-money issuers and dozens of banks, each with its own app, its own KYC process, and its own merchant onboarding rules. Building and maintaining direct, bilateral integrations with each of them is a multi-month undertaking that most foreign entrants cannot justify before they even know whether the market will work for them.
QRPH changes that calculus. Because the standard is interoperable by design, a single QRPH integration — typically provided through a licensed gateway rather than built in-house — gives a foreign business collection coverage across the wallets and banks that matter to Filipino consumers, without a separate commercial and technical negotiation for each one. That is the core value proposition behind QRPH Collection Services for a market entrant: one integration, broad local reach, and no requirement to hold a Philippine entity or banking relationship on day one.
How QRPH Collection Works, Technically
A QRPH transaction has three layers worth understanding if you are the business receiving the funds, not just the shopper paying them.
- The code layer. A merchant QR code — static, printed once and reused indefinitely, or dynamic, generated per transaction and encoding the exact amount plus a reference number — carries the merchant's account identifier in the standardized QRPH data format.
- The routing layer. When a shopper scans the code with any participating bank or wallet app, that app reads the merchant identifier and routes the payment instruction through the national QRPH switch rather than through a proprietary rail. This is the step that makes the "any wallet, one code" model possible — the switch, not the merchant, is responsible for knowing which institution the code belongs to.
- The settlement layer. Funds move from the shopper's issuing bank or wallet to the merchant's receiving institution through the interbank settlement rails that sit underneath QRPH. This is where the receiving side needs the operational capacity to accept funds from many possible issuing wallets and banks and consolidate them into a single, reconcilable position.
| Participant type | Examples | Role in a QRPH collection |
|---|---|---|
| Universal / commercial banks | Major retail banks with QR-enabled mobile banking apps | Issuing side — a shopper's bank app generates the scan that debits their account |
| Digital banks | Fully digital, app-only banks | Issuing side — functions the same as a traditional bank for QRPH purposes |
| E-money issuers (wallets) | GCash, Maya, and other licensed e-wallets | Issuing side for most consumer scans; the largest share of everyday QRPH volume |
| Rural and thrift banks | Smaller regional banks onboarded to the standard | Issuing side — extends QRPH reach outside major cities |
| Licensed gateway (receiving side) | BSP-licensed OPS/EMI acting on the merchant's behalf | Receives across all of the above, consolidates settlement, and reconciles for the merchant |
From the shopper's side, this all happens in a handful of taps. From the merchant's side, the complexity is in the routing and settlement layers — which is exactly the part a gateway's QRPH merchant API and signature verification process is built to abstract away, and the reason most foreign businesses do not attempt direct participation in the full list of banks and wallets QRPH actually reaches on their own.
What a Licensed Gateway Handles on a Foreign Business's Behalf
A gateway that is BSP-licensed as an Operator of Payment System (OPS) and as an Electronic Money Issuer (EMI) is operating under direct central bank supervision for the exact functions — holding, moving, and settling customer funds — that a QRPH collection flow requires.
When a foreign business routes its QRPH collection through such a gateway rather than attempting direct bank-by-bank integration, three things happen on its behalf:
- Settlement consolidation. Regardless of which wallet or bank a shopper used, the business receives a consolidated settlement into one account, in one currency, on a predictable schedule, instead of managing separate payout relationships with every participating institution.
- Reconciliation. Every QRPH transaction carries a reference number, but matching large volumes of these references across multiple issuing institutions against internal order records is a data problem on its own. A gateway's reporting layer does this matching so the business's finance team works from one ledger, not a dozen.
- Compliance. The gateway carries the KYC, anti-money-laundering, and BSP reporting obligations that attach to moving customer funds in the Philippines, so the foreign business does not need to independently hold a local license to accept QRPH payments.
QRPH Collection vs Other Collection Methods
QRPH is not the only way to collect in the Philippines, and it is worth being clear about where it fits relative to the alternatives.
| Method | Interoperability | Typical integration effort | Settlement consolidation | Best fit |
|---|---|---|---|---|
| QRPH via licensed gateway | One code, broad wallet/bank reach | Low — a single API integration | Consolidated by the gateway | Foreign businesses entering the market; in-store and app-based checkout |
| Direct bilateral wallet integration | Limited to the one wallet integrated | High — a separate contract and build per wallet | Managed per wallet, by the business | Large domestic merchants with in-house engineering capacity |
| Bank transfer (InstaPay/PESONet) | Bank-to-bank, not wallet QR-based | Moderate | Depends on the receiving bank | B2B transfers, payroll, high-value one-off payments |
| Card acquiring | Card networks only | Moderate to high | Consolidated by the acquirer | E-commerce checkouts where card penetration is relevant |
Integrating QRPH Collection: A Technical Walkthrough
Below is a simplified view of the two calls a backend engineer typically implements first: generating a dynamic QRPH code for a specific order, and verifying the signature on the payment notification that follows.
1. Requesting a dynamic QRPH code via the gateway API:
curl -X POST https://api.paysmartph.com/v1/qrph/collect \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{
"merchant_id": "MCH10023",
"order_no": "ORD-2026-00917",
"amount": "AMOUNT_IN_PHP",
"currency": "PHP",
"callback_url": "https://yourapp.com/webhooks/qrph",
"sign": "GENERATED_SIGNATURE"
}'2. Verifying the callback signature before trusting a payment notification (Node.js):
const crypto = require('crypto');
function verifyQrphCallback(payload, receivedSign, secretKey) {
const ordered = Object.keys(payload)
.filter((k) => k !== 'sign')
.sort()
.map((k) => `${k}=${payload[k]}`)
.join('&');
const computedSign = crypto
.createHmac('sha256', secretKey)
.update(ordered)
.digest('hex');
return computedSign === receivedSign;
}
// Only mark the order as paid if this returns true.
app.post('/webhooks/qrph', (req, res) => {
const isValid = verifyQrphCallback(req.body, req.body.sign, process.env.QRPH_SECRET);
if (!isValid) return res.sendStatus(400);
// update order status, trigger fulfillment, etc.
res.sendStatus(200);
});The signature check is not optional. Treating an unverified callback as proof of payment is one of the most common integration mistakes foreign engineering teams make when they are new to the market — the notification endpoint has to be public to receive callbacks, which means it has to assume every request could be spoofed until the signature says otherwise.
Compliance, Licensing, and Getting Started as a Foreign Business
Because QRPH touches the movement of customer funds, every institution that participates in it — banks, e-money issuers, and the gateways that connect to them — operates under BSP oversight. For a foreign business choosing a collection partner, this is the single most important diligence item, more important than the user interface or the onboarding speed a provider advertises.
Before signing with any payment partner for QRPH collection, confirm its BSP license type directly. OPS and EMI licenses are a matter of public record, and a provider that cannot point to its own license status is not a provider worth building a payment flow on top of.
This matters because collection is only half of the relationship. A foreign business also needs its partner to handle the obligations that come with holding an OPS or EMI license correctly, including the KYC and anti-money-laundering screening that applies to every transaction passing through the rails, and the dispute process when a shopper claims a QRPH payment was unauthorized. A gateway that treats these as core infrastructure, not an afterthought, is the difference between a collection channel that scales and one that generates operational risk a few months into launch.
In practice, the onboarding sequence looks like this: complete know-your-business documentation with the gateway, receive sandbox API credentials and test the collection and callback flow end to end, confirm how consolidated settlement and reconciliation reporting will reach your finance system, and only then move to production traffic. Businesses that already operate cross-border in the region often run this in parallel with their broader cross-border collection and settlement planning, rather than treating QRPH as an isolated technical task.
Frequently Asked Questions
Is QRPH the same thing as GCash's or Maya's QR code?
No. GCash and Maya are e-wallets that participate in QRPH as issuing and receiving institutions, among many others. QRPH is the underlying national standard that lets a single code work across GCash, Maya, and participating banks, rather than being any one wallet's proprietary format.
Does a foreign business need a Philippine bank account to collect via QRPH?
Not necessarily. A BSP-licensed gateway can receive QRPH collections on a foreign business's behalf and settle out to an account structure the business already has in place, which is typically the main reason market entrants use a gateway rather than attempting direct participation.
What currency is a QRPH transaction settled in?
QRPH transactions are denominated and settled in Philippine pesos, since the shopper's wallet or bank account is peso-based. A gateway handling cross-border settlement is the layer that converts and routes those funds onward to the business's preferred settlement currency and account.
What happens if a QRPH payment is disputed?
Disputes are handled through the participating institution's standard investigation process, with the gateway coordinating the exchange of transaction evidence between the merchant, the issuing wallet or bank, and the dispute process defined under BSP rules. This is one of the operational functions a licensed gateway manages so the merchant does not have to interface with each institution separately.
Can QRPH support recurring or subscription payments?
QRPH itself is built around single transactions initiated by a scan, so recurring billing typically requires a gateway to layer a tokenized or scheduled-collection mechanism on top, rather than relying on QRPH alone for every billing cycle.
What is the difference between a static and a dynamic QRPH code?
A static code is generated once and reused for any amount, with the shopper entering the amount manually, which suits a storefront counter. A dynamic code is generated per transaction with the amount and reference encoded in, and is the pattern most foreign businesses use for online checkout because it removes manual entry error.
How can a business verify that a gateway's BSP license is genuine?
BSP publishes lists of licensed Operators of Payment Systems and Electronic Money Issuers, and a legitimate gateway will be able to confirm where it sits on that list without hesitation. Treat reluctance to do so as a signal worth taking seriously, not a minor concern.
If your business is evaluating QRPH as a collection mechanism for the Philippine market, SMARTPAY is a BSP-licensed (OPS/EMI) payment gateway that handles QRPH integration, settlement consolidation, reconciliation, and compliance on your behalf. Reach out on Telegram at t.me/LouisSMARTPAY (@LouisSMARTPAY) or by email at [email protected] to discuss onboarding for your specific market-entry timeline.