Payment Providers in the Philippines: QR Ph and PHP Payouts

Comparing payment providers in the Philippines starts with the transaction you need to support. A customer paying a merchant by QR, a personal transfer and a business sending a supplier payment can involve different services, limits and reporting requirements—even when the same banking app appears in the journey.

For merchants, two questions make the shortlist more useful: which payment flow will customers actually use, and what evidence will your team receive to match money to an order or beneficiary?

What the PayStar review covers

Our review of the 14 September 2026 PayStar data snapshot identified 52 unique offers linked exclusively to the Philippines: 29 incoming-payment records and 23 payout records. All 52 also have a PHP currency link. We counted each offer once, rather than counting repeated rows from joined data.

This gives us a starting set for comparing acceptance and payouts separately. An offer record is not evidence of current availability or approval for a particular business. Country, currency and payment-method links also need qualification together before a specific route can enter an implementation plan.

QR Ph merchant payments and InstaPay QR serve different purposes

The BSP's July 2026 rebranding FAQ makes the distinction explicit: QR Ph identifies person-to-merchant payments; InstaPay QR identifies person-to-person transfers. The change clarifies the customer-facing names while retaining the underlying interoperable standard. It also addresses confusion when customers use a personal-transfer QR for a merchant purchase. BSP: QR Ph rebranding.

QR Ph P2M lets customers pay merchants across participating banks and electronic money issuers. For a merchant, that makes the acquiring arrangement and supported customer applications relevant to the same acceptance discussion. BSP: QR Ph P2M.

Ask a prospective provider to demonstrate your checkout. Confirm the merchant identity displayed before payment, how the amount is populated and how the order reference reaches the merchant's records. For an online purchase on one phone, test the actual handoff or QR-upload journey rather than relying on a demonstration with two devices.

Request the merchant agreement and reporting examples for that flow. A QR image alone tells you little about the operational service behind it.

PHP payouts: identify the service behind the limit

Standard InstaPay provides domestic PHP transfers between participating accounts around the clock, with a PHP 50,000 per-transaction ceiling. Account or institution limits can further constrain use. BSP: InstaPay fact sheet.

However, that ceiling does not describe every business service. The BSP's InstaPay for Business FAQ, dated 29 July 2026, describes real-time B2B and B2C transfers of up to PHP 500,000 per transaction, available 24/7 to businesses with business or corporate accounts. Originating institutions may impose their own limits, and receiving institutions perform limit checks. Availability must be confirmed with the participating institutions involved. BSP: InstaPay for Business.

For PESONet, payments are processed in batches across three settlement windows. Provider cut-offs and banking days matter: after-cut-off, weekend or holiday instructions can move into the next banking day. PESONet itself sets no minimum or maximum transaction value, while individual providers can impose transaction and daily caps. PPMI: PESONet.

These are qualification paths, not a statement that a particular PSP in our snapshot supports every service.

Compare a real payout schedule

Consider a hypothetical merchant paying a supplier PHP 180,000 on Friday afternoon. The amount is above the standard InstaPay ceiling, but within the published InstaPay for Business ceiling. That makes the business service worth checking where the accounts and institutions are eligible. If the merchant instead chooses PESONet, its provider's cut-off and the next banking day become part of the payment promise.

Ask the provider to document the expected outcome for the actual submission time, beneficiary account and amount. A successful API submission, a debit from the funding account and credit to the beneficiary are separate checkpoints. Your operations team needs to know which status proves each one and how to investigate an unresolved transfer before retrying it.

Make reconciliation part of provider selection

For collections, request a sample report connecting the merchant order, payment reference, gross amount, any deductions and the amount credited. For payouts, connect the instruction to its beneficiary, provider reference, final outcome and any return. Review how duplicate notifications and delayed confirmations are identified.

For a supplier-payment batch, test a report containing completed, rejected and unresolved instructions. Each item needs its own reference and outcome so finance can reconcile the batch while operations investigates outstanding payments without sending the completed ones again.

Where a PSP collects on your behalf, verify its settlement schedule separately from the payment system's transfer speed. Establish the receiving account, currency, reconciliation file and handling of adjustments before comparing commercial terms.

Build a Philippines PSP shortlist around your business

Share your registration country, business activity, customer-payment journey, payout recipients, transaction sizes and expected volumes with PayStar Discovery. We can help structure a shortlist and the commercial, technical and operating questions to take to each provider.

The merchant chooses the PSP and signs a direct agreement. The PSP remains responsible for processing and settlement under that agreement. The next step is to qualify the proposed services for your business and test the evidence needed to operate them.

Offer snapshot: 14 September 2026. Official payment-system sources checked on 18 September 2026.