Buyer’s guide · Philippines

How to choose a payment gateway in the Philippines

A Philippines payment gateway lets a business collect and pay out Philippine pesos through local rails such as QR Ph, InstaPay, PESONet and the major e-wallets by API, and increasingly settle in USDT. This guide is for BD, product and payments leads evaluating providers: what the local rails are, what to check, what to ask, and where the traps are.

Updated September 202611 min read

Get started Talk to us on Telegram

Who this guide is for

You are an exchange, trading platform, wallet, freelancer or creator platform, gaming company, remittance business or cross-border payments provider that needs to collect from or pay to people in the Philippines, and you are deciding which provider to integrate.

The Philippines is a wallet-first market. A large share of consumers run their financial life through an e-wallet rather than a bank account, and the national QR standard and real-time rails make wallets and banks interoperable. Payouts matter at least as much as collections here: gig income, remittances, winnings and withdrawals all end in a wallet or bank account, and users judge a platform by how fast that money lands.

This guide walks through the rails, gives you a 12-point checklist with a way to verify each point, compares the four kinds of provider you will meet, lists the questions worth asking in a first call, and flags the mistakes that cost teams months. The last section explains where CVPay sits on that checklist so you can judge us by the same standard.

How payments actually move in the Philippines

Four rails matter for a business integrating in the Philippines. A gateway is only as good as its coverage of these.

QR Ph and the e-wallets

QR Ph is the national QR standard under the central bank’s framework. A customer scans a QR in GCash, Maya, GrabPay or a bank app and pays from their wallet or account. Because the standard is interoperable, one QR reaches users across wallets and banks. Dynamic QR codes carry the amount and an order reference, which is what makes automatic reconciliation possible.

InstaPay

InstaPay is the real-time interbank transfer rail. Transfers between participating banks and e-wallets typically settle near-real-time, 24/7, for amounts within the rail’s per-transaction cap. It is the workhorse for consumer-sized payouts and wallet top-ups.

PESONet

PESONet is the batch interbank rail for larger transfers. Transfers are cleared in cycles on banking days rather than instantly, so it suits supplier settlement, payroll and high-value disbursement rather than user withdrawals. A provider should route between InstaPay and PESONet automatically by amount.

USDT settlement

For cross-border businesses, USDT on TRON (TRC-20), Solana and BNB Smart Chain is the practical way to fund peso payouts and repatriate peso collections. A gateway that quotes USDT to PHP and PHP to USDT under the same account removes the need for a separate exchange relationship and manual treasury work.

For how each major wallet and bank works with CVPay, including QR collections and payout reach, see the payment method pages: Payment methods in the Philippines

The 12-point evaluation checklist

Score every provider on the same twelve points. For each, we explain why it matters and how to verify it instead of taking the sales deck’s word for it.

1
Wallet reach for both collections and payouts
Why it matters
GCash and Maya are where Filipino users keep their money. A provider that only collects from wallets but cannot pay out to them, or the reverse, forces you onto a second integration.
How to verify
Ask for the list of wallets and banks reachable in each direction. Run a sandbox collection from a wallet QR and a sandbox payout to a wallet-linked account.
2
Dynamic, order-bound QR Ph codes
Why it matters
Static QR codes force manual matching of incoming payments to orders. Dynamic codes carry the amount and reference so every payment reconciles itself.
How to verify
Create a sandbox order, scan it in a real wallet app and check that the amount is pre-filled and the reference appears in the webhook payload.
3
InstaPay and PESONet routing
Why it matters
Consumer payouts need InstaPay’s near-real-time settlement; larger amounts must go over PESONet. If you have to choose the rail yourself, you own every failure at the boundary.
How to verify
Ask how the provider selects the rail, what happens to an amount above the InstaPay cap, and how PESONet cut-off times are surfaced in the API response.
4
Payout speed distribution, not the average
Why it matters
Withdrawals define user trust. A provider can quote “minutes” while a meaningful share of transfers take hours because of downstream bank behaviour.
How to verify
Ask for the time-to-final-state distribution over the last 30 days, split by wallet and bank destinations, including nights and weekends.
5
Handling of failed and returned transfers
Why it matters
Wrong account numbers, inactive wallets and rail-side rejections are common. The money must come back to your balance with a reason you can act on.
How to verify
Send a payout to a deliberately invalid account in sandbox. Check the failed webhook arrives with a reason and that the balance is released.
6
USDT in both directions
Why it matters
Cross-border businesses fund peso payouts from USDT and repatriate peso collections as USDT. One-directional support means a second provider and manual transfers.
How to verify
Ask for the quote flow: is the rate locked when you confirm, for how long, and is the fee shown before confirmation? Check which chains are supported.
7
Licensing and compliance posture
Why it matters
Your compliance team and banking partners will ask who the counterparty is and how it is regulated. A provider without a recognisable licence creates risk you inherit.
How to verify
Ask for the licence type and issuing regulator, then check the regulator’s public register. Ask what KYB documents are required and how transaction monitoring works.
8
Entity requirements
Why it matters
Some providers can only onboard Philippine-registered companies. If you are incorporated elsewhere, that is a hard stop.
How to verify
State your incorporation country in the first call and ask directly whether onboarding is possible without a Philippine entity.
9
API quality and webhooks
Why it matters
Signed webhooks, idempotent transfer creation, explicit final states and a query endpoint decide how much operational glue you write and how many duplicate payouts you risk.
How to verify
Read the public API docs before the sales call. Look for a signature spec, explicit state machines for orders and transfers, and how retries and duplicate notifications are handled.
10
Limits and how they are configured
Why it matters
Rail caps, wallet-side tier limits and merchant-account limits stack. Your largest recipients may be blocked by a limit you did not know existed.
How to verify
Ask for the limit model at each layer and who can change it. Ask what happens to a transfer above a limit: rejected, split, or queued.
11
Pricing model transparency
Why it matters
Philippine pricing usually combines a percentage and a fixed peso fee per transaction, with different rates for wallets and banks, and FX may hide a spread.
How to verify
Ask for the full fee schedule per method and direction, and whether FX is quoted with an explicit fee or an embedded spread. Model your real ticket sizes.
12
Reconciliation, reporting and support
Why it matters
Finance needs order-level references on every movement; operations needs a human when a payout is stuck on a holiday.
How to verify
Ask for a sample statement export and check every line carries your order reference and fee breakdown. Ask which channel support runs on and the response commitment for stuck transfers.

The four kinds of provider you will meet

Names change, but providers in the Philippines fall into four archetypes. Each is right for someone; the table shows where each tends to be strong and weak.

Criterion	Global PSP	Local Philippine PSP	Crypto / stablecoin gateway	Direct wallet or bank integration
Typical customer	International e-commerce and SaaS adding the Philippines as one of many markets	Philippine-registered e-commerce, retail and domestic platforms	Exchanges, trading platforms, freelancer and creator platforms, gaming, remittance and cross-border payments	Large domestic enterprises with a Philippine entity and in-house payments team
Local rails	Often via a local partner; wallet payouts may be limited or slower	Strong QR Ph and wallet collections; payout coverage varies by provider	QR Ph collections, InstaPay and PESONet payouts to wallets and banks, plus USDT	Full access to that wallet or bank; others via the national rails
Philippine entity required	Usually not	Usually yes	Usually not; KYB on the operating entity	Yes
USDT settlement	Rarely	Rarely	Core feature, both directions	No
Settlement currency and speed	Often settled abroad on T+n, with FX applied	PHP to a Philippine bank account, typically T+1 or faster	PHP balance available immediately; USDT on-chain within minutes	PHP in the account directly
Integration effort	Low if you already use them elsewhere	Medium; documentation quality varies	Medium; one REST API for collections, payouts and FX	High; each wallet and bank API is bespoke
Best when	The Philippines is a small share of volume and cards matter	You are a domestic business selling to Filipino consumers	You pay many people in pesos, move value across borders, or hold USDT	You have scale, a local team and years to invest

Questions to ask in the first call

These separate providers that have done this from providers that plan to. Send them ahead of the call and see who answers in writing.

Can you onboard a company incorporated outside the Philippines? What KYB documents do you need and how long does approval take?
Which wallets and banks can I collect from, and which can I pay out to? Is the list the same in both directions?
Is your QR Ph dynamic and order-bound? Show me the webhook payload for a completed payment.
How do you route between InstaPay and PESONet? What happens to an amount above the InstaPay cap?
What is the time-to-final-state distribution for peso payouts over the last 30 days, split by wallet and bank, including nights and weekends?
How do you handle a payout rejected by the rail or returned by the receiving institution? How and when am I notified, and when is the balance released?
Do you support USDT to PHP and PHP to USDT? On which chains? Is the rate locked at confirmation and for how long?
Is the FX fee explicit, or is there a spread embedded in the rate?
What are the per-transaction and daily limits at the rail, wallet and merchant layers, and who can change them?
How are webhooks signed? How do you handle retries and duplicate notifications? Is there an order query endpoint?
When do I get sandbox credentials, and does the sandbox behave like production for failures and timeouts?
What does a monthly statement look like? Does every line carry my order reference and the fee breakdown?
Which licence do you operate under, and who is the regulator?
What is your support channel and response commitment for a stuck transfer outside business hours?

Mistakes that cost teams months

Treating wallets as an afterthought

A provider with excellent bank coverage and weak wallet payouts will fail the majority of Filipino recipients. Test wallet payouts first, not last.

Ignoring the InstaPay cap

Amounts above the real-time rail’s cap must go over PESONet, which clears in cycles on banking days. If your product promises instant withdrawals, cap the amount or set expectations in the UI.

Choosing on the headline rate

Wallet and bank payouts are often priced differently, and a low percentage with a high fixed fee is expensive for the small tickets typical of gig and creator payouts. Model your real distribution.

Discovering the entity requirement late

Teams have spent weeks in integration before learning the provider could not onboard a foreign company. Ask on day one.

Unlocked FX rates

If the rate is set at execution rather than at confirmation, your users see one number and get another. Insist on a quote that is honoured when confirmed inside its window.

No plan for rejected transfers

Inactive wallets, mismatched names and rail rejections are routine. If failures do not return to your balance with a reason, your support queue becomes a finance problem.

What a realistic timeline looks like

From shortlist to first live transaction, most teams need two to four weeks with a provider that has done this before. The critical path is KYB, not code.

1
Shortlist and first calls
Send the question list above to three providers. Drop any that cannot answer in writing or cannot onboard your entity.
2
KYB
Submit company documents, ownership and use-case description. With a complete pack, approval typically completes within 1–3 business days at a well-run provider.
3
Sandbox integration
Implement order creation, webhook handling and the query endpoint. Test failure cases: invalid wallet, amount above the rail cap, rejected transfer, duplicate notification.
4
Pilot and go-live
Start with a small volume and low limits, watch reconciliation for a few days, then raise limits. Keep the second provider warm as a fallback.

How to read a Philippines pricing sheet

Philippine collections and payouts are usually priced per transaction as a percentage plus a fixed amount in pesos, often with different rates for wallet and bank destinations and sometimes a minimum fee. Because gig, creator and gaming payouts skew to small tickets, the fixed component usually dominates. Always model your real ticket distribution rather than a single average.

FX between USDT and PHP is priced either as an explicit fee on top of a reference rate or as a spread embedded in the quoted rate. Both can be fair; what matters is that you can see the reference rate and the fee separately before you confirm, and that the confirmed rate is honoured.

Ask for the complete schedule by method and direction, and for any charges on failed or returned transfers, statement exports or balance holds. Setup fees and monthly minimums are uncommon in this market and worth pushing back on.

Where CVPay sits on this checklist

We wrote the checklist first and then scored ourselves. Here is the honest summary so you can compare us on the same terms as everyone else.

Rails

QR Ph collections from the major wallets; PHP payouts to bank accounts and wallet-linked accounts over InstaPay and PESONet, routed by amount, with final status by signed webhook. Payout QR parsing can pre-fill recipient details.

USDT and FX

USDT deposits and payouts on TRON (TRC-20), Solana and BNB Smart Chain, with quote-and-confirm conversion to and from PHP. The rate and fee are shown before you confirm and honoured inside the lock window.

Compliance and entity

Licensed under Singapore’s Payment Services Act and regulated by MAS. We onboard the operating entity wherever it is incorporated; KYB typically completes within 1–3 business days.

API and operations

One REST API for collections, payouts and FX with signed webhooks and order query; sandbox after KYB; order-level references on every ledger line; support on Telegram. Limits and pricing follow your merchant configuration and are agreed in writing. Our Philippine volume is smaller than our Vietnam volume today, and we say so.

Frequently asked questions

What is a Philippines payment gateway?+

A service that lets a business collect and pay out Philippine pesos through local rails such as QR Ph, InstaPay, PESONet and e-wallets by API, handling routing, reconciliation and status notification. Some gateways also settle in USDT for cross-border businesses.

Do I need a Philippine company to accept payments in the Philippines?+

It depends on the provider. Many local providers require a Philippine entity; some licensed cross-border gateways onboard foreign companies after KYB. Ask this on the first call.

What is the difference between InstaPay and PESONet?+

InstaPay is the real-time rail for transfers within its per-transaction cap and settles near-instantly, 24/7. PESONet is the batch rail for larger amounts and clears in cycles on banking days. A good provider routes between them by amount automatically.

Can I pay out to GCash and Maya users?+

Yes, through providers whose payouts reach wallet-linked accounts over the national rails. Confirm that the wallet list is the same for payouts as for collections, and test it in sandbox.

Can I settle Philippine collections in USDT?+

With a gateway that supports USDT conversion, yes. Collections land as PHP, you request a quote, confirm, and receive USDT on-chain. Check which chains are supported and whether the quote is locked at confirmation.

What does a Philippines payout API typically cost?+

Pricing is usually a percentage plus a fixed peso fee per transaction, often different for wallets and banks. There is no single market rate; model your ticket sizes and ask for a full schedule rather than a headline number.

How long does integration take?+

With a provider that has a sandbox and clear docs, most teams go from KYB approval to first live transaction in two to four weeks. KYB, not coding, is usually the critical path.

What are the biggest risks when choosing a provider?+

Weak wallet payouts, ignoring the InstaPay cap, entity requirements discovered late, FX rates that are not locked, and no process for rejected transfers. The checklist above covers how to verify each.

Glossary

QR Ph: The Philippines’ national QR payment standard, letting one QR be paid from participating wallets and bank apps.
InstaPay: The real-time interbank and wallet transfer rail for amounts within its per-transaction cap, available 24/7.
PESONet: The batch interbank transfer rail for larger amounts, cleared in cycles on banking days.
BSP: Bangko Sentral ng Pilipinas, the Philippine central bank that oversees the national payment rails and licenses e-money issuers.
E-wallet / EMI: A mobile wallet such as GCash or Maya, operated by a BSP-licensed electronic money issuer.
Dynamic QR: A QR code generated per order that carries the amount and reference, enabling automatic reconciliation.
Pay-in / Pay-out: Collecting money from a payer (pay-in, deposit) versus sending money to a recipient (pay-out, disbursement, payout).
Payout QR: A QR code a recipient shares that encodes their bank or wallet details, which a provider can parse to pre-fill a payout.
KYB: Know Your Business: the provider’s due diligence on your company, owners and use case before onboarding.
USDT (TRC-20 / SPL / BEP-20): The dollar-pegged stablecoin Tether on the TRON, Solana and BNB Smart Chain networks respectively.
Payment Services Act (PSA): Singapore’s payment services law under which the Monetary Authority of Singapore licenses payment providers.