← Back

Country payment guide

Accept payments in Philippines

The Philippines requires a checkout mix that reflects wallet-heavy consumer behaviour, bank transfer routes, cards, cash-linked options, and local PSP or aggregator onboarding. Small merchants should compare GCash and Maya coverage, local payment gateways, bank transfer support, settlement terms, and whether the provider can onboard a foreign merchant without creating operational friction.

Which PSPs and payment routes can you explore in Philippines?

Existing research for Philippines includes PayMongo, Xendit Philippines, Bank of the Philippine Islands (BPI Cashless Payment Acceptance), UnionBank UPAY, GCash for Business, Maya Business. Explore their products and local payment methods, then use your business and company location to narrow the enquiries.

No local company, or no clear contact route?

These are research leads, not approval or industry-support guarantees. Tell us the market and your company location so we can help you explore further.

8Channel recordsPublic directory entries
AsiaRegionPH
Usually requires a local entityOnboardingFrom structured fields
To be confirmed, T+1SettlementVerify on detail pages

Curated market guide

Philippines PSP routes to verify first

Which PSPs, wallets, and bank routes should a merchant ask first for GCash, Maya, InstaPay/PESONet, cash collection, and cards in the Philippines?

4
local_psp_or_aggregator · curated

Philippine PSP / gateway shortlist

PayMongoXendit PhilippinesDragonpayPaynamics Technologies Inc.

Use when you need wallet, card, bank-transfer, and over-the-counter options in one PSP evaluation.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
acquirer_or_bank · curated

Bank acquiring or cashless acceptance route

Bank of the Philippine Islands (BPI Cashless Payment Acceptance)UnionBank UPAYMetrobank Card Corporation (Metrobank Payment Acceptance Solutions)

Use when bank acquiring, enterprise treasury, or local account-to-account flows are important.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
direct_scheme_or_wallet · curated

Wallet and cash-collection route

GCash for BusinessMaya BusinessBayad (CIS Bayad Center, Inc.)ECPay

Use when customer adoption depends on local wallets or cash collection and direct/partner access needs confirmation.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
international_psp · curated

Regional PSP route

Dragonpay via XenditAsiaPay Philippines (PesoPay)Brankas Philippines

Use when Southeast Asia expansion or open-banking coverage matters, while verifying Philippine onboarding conditions.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
KYB prep

Documents to prepare

  • Company registration and Philippine entity or foreign onboarding question
  • Beneficial-owner and signatory ID
  • Website/app URL and product category
  • Bank account and payout-currency requirements to verify
  • Refund, dispute, and customer-service policy
Due diligence

Questions to ask

  • Can my current merchant entity onboard for this market, or is a local company required?
  • Which local payment methods are actually enabled for my merchant category and transaction model?
  • Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
  • Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
  • Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?
Contact route fallback

If the official contact route is unclear

If public contact details are not specific enough, ask LocalPayMap to identify the right official form, PSP sales route, or local acquiring partner before committing engineering work.

  • Which local payment methods are actually enabled for my merchant category and transaction model?
  • Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
  • Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
  • Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?

Merchant questions before choosing a provider

Use these questions to separate customer payment fit from PSP onboarding, settlement, pricing, support, refunds, disputes, and compliance details.

How customers may pay locally

GCash, Maya, local bank transfers, cards, QR routes, and cash-adjacent methods may all matter depending on audience and ticket size. A checkout that only accepts international cards can feel incomplete for mass-market buyers.

Local entity and settlement checks

Confirm whether the provider can onboard a foreign company, whether local settlement is required, and how PHP settlement, FX, reserves, and payout timing work.

PSP selection notes

Merchants can compare local PSPs, regional Southeast Asia aggregators, wallet acceptance routes, bank-transfer providers, and global PSPs with Philippines support. The most practical route is often the one that combines wallet coverage with clear settlement and support.

Documents and KYB checks

Expect company documents, owner details, website review, product category, refund policy, customer support contact, expected volume, and bank or settlement details.

Integration checklist

Confirm these items before committing engineering time or signing provider terms.

Merchant checklist before integration

Use these questions before committing engineering time or signing a provider contract.

  • Confirm GCash, Maya, card, and bank-transfer coverage.
  • Ask whether foreign merchant onboarding is available.
  • Verify PHP settlement, FX conversion, reserves, and payout timing.
  • Check refund and reconciliation handling for wallet payments.
  • Confirm sandbox, hosted checkout, API, webhook, and payment link support.
  • Request official pricing or a written quote before comparing cost.

How customers actually pay here

The Philippines is a wallet market with a large cash shadow. GCash is a major consumer payment app used for transfers, bills, QR payments and online checkout, and Maya is another important wallet with a digital bank licence behind it. Together they can cover many digitally active buyers, but actual merchant coverage depends on the PSP route. Bank transfers run underneath through InstaPay and PESONet for different transfer and batch use cases. QR Ph, the national QR standard, connects participating banks and wallets. Cash is still significant: over-the-counter points such as 7-Eleven, Bayad and Palawan Pawnshop serve buyers without accounts, and cash-on-delivery remains common in ecommerce.

  • GCash is a major consumer payment app in the Philippines.
  • Maya is another important wallet and operates with a digital bank licence.
  • InstaPay and PESONet support different transfer and batch use cases.
  • QR Ph is the national QR standard linking participating banks and wallets.
  • Cash-on-delivery and over-the-counter payment remain common in ecommerce.

Next actions

Next actions for Philippines

Use these internal paths to move from market research to provider outreach without assuming eligibility, pricing, settlement, or local-entity access.

Questions merchants ask

Which payment methods should a Philippines checkout consider first?

Wallets such as GCash and Maya, local bank-transfer routes, cards, and QR or cash-linked options are common items to verify.

Is wallet acceptance the same as PSP onboarding?

No. GCash or Maya may be the customer-facing method, while a PSP, aggregator, bank, or platform handles merchant onboarding, settlement, and integration.

Do foreign merchants need a local Philippines entity?

Requirements vary by provider. Some routes may support foreign entities, while others require local registration, local banking, or additional KYB checks.

What operations matter after launch?

Refund handling, payment confirmation timing, reconciliation reports, customer support, chargeback or dispute handling, and settlement timing should be agreed before launch.

Can published prices be used as final Philippines PSP pricing?

No. Published pricing is only useful for screening; final terms should come from official pricing pages or the provider's quote.

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

Not necessarily. Regional and cross-border providers will often contract with a foreign entity and provide GCash, Maya and cards. Local entities usually get better pricing and faster onboarding. Ask each provider directly whether their wallet connections are available to non-resident merchants before you commit.

Which payment method should I add first in the Philippines?

Add GCash first, then Maya. Together they cover most digitally active Filipino buyers, and many will abandon a checkout that offers neither. Add cards third for higher-ticket and international orders, then InstaPay for transfers and over-the-counter cash for unwalleted buyers.

How long does settlement take for GCash and Maya payments?

Wallet payments confirm quickly at checkout, but your provider still applies its own payout cycle before funds reach your bank. Bank transfers depend on the rail, with InstaPay faster than PESONet. Over-the-counter cash waits on the buyer. Always confirm the exact schedule in writing.

Public sources