Collect the way Filipinos pay.
Pay people where they are.
Cards are a minority of Philippine payments. This is the full method set, the rails behind it, and the four channels you collect through — on PayMongo's licensed Philippine operations.
PLACEHOLDER: hero capture — the Philippine method set rendered in a checkout, PHP amounts
PCI DSS Level 1 · AICPA SOC examined
$18B+ processed · 2.7B transactions · 350,000+ businesses. Processed through PayMongo's licensed Philippine operations since 2019.
What your Filipino customer can pay with
Named below, because a buyer cannot evaluate the phrase "local methods". This is the list you send to your own engineer.
The apps most Filipinos pay from
Four mobile money apps carry most online payments in the country. A global processor that takes cards takes none of them, which is the gap this closes.
The national QR standard
One code, accepted from any participating bank or mobile money app the customer already has — which is most of them.
Direct online banking
BDO, BPI, UnionBank, Metrobank, Landbank and RCBC, paid from the customer's own banking app.
Cards
Visa and Mastercard, domestic and international. The method a global processor already gives you, and the one Filipinos use least.
Buy now, pay later
BillEase, for higher-ticket purchases where the alternative is an abandoned cart.
Over the counter
PLACEHOLDER: over-the-counter network list — which partners and outlets, confirmed against the live product rather than carried from a deck.
Collecting is half the job
A marketplace with Filipino sellers, a platform paying Filipino contractors, a business paying Philippine suppliers — all of them need money to go the other way, to people who bank and spend in PHP.
PayMongo sends funds to Philippine bank accounts and mobile money accounts over InstaPay and PESONet, inside the Philippines, on our Philippine licence.
PLACEHOLDER: repatriation and movement mechanics for a foreign-owned account — where funds land, in which currency, on what timeline, and the FX treatment. Product and Treasury own this, and it is the second question every buyer asks.
Start from where you are
Four setups, four answers.
- “I have a website”
A hosted page that renders every method your processor supports.
Checkout - “I sell over chat and email”
One link that opens a checkout, sent wherever the conversation is.
Payment Links - “I have a physical venue”
A QR code that opens your menu on the customer's own phone.
Order & Pay - “I have no site yet”
Describe what you sell and get a store with checkout built in.
Storefront
Four ways to collect
Same methods and rails underneath. Four different moments in front of them.
- I have a website
Checkout
One checkout. Every method your processor supports.
A hosted payment page your processor's methods render inside
- I sell over chat and email
Payment Links
Send a payment request in seconds. No website needed.
One link that opens a checkout, sent over any channel you already use
- I have a physical venue
Order & Pay
Take the order. Close the table.
QR ordering and checkout for venues, with tabs, tipping and split bills
- I have no site yet
Storefront
Describe your business. Get a store.
A generated storefront with checkout built in, live the same day
How they differ
The last row is the same for all four, and it is the point of the layer.
| Checkout | Payment Links | Order & Pay | Storefront | |
|---|---|---|---|---|
| Integration effort | One call from your backend | None — created from the dashboard or the API | None — put the codes out | None — describe it and publish |
| Time to live | Days | Same day | Same day, plus printing the codes | Same day |
| Where it's used | On your site, at the end of a cart | In an invoice, an email, a chat thread | On a table, a counter, a stall | As your store, on your own domain |
| Customisation | Branding, fields, languages, currencies | Branding, fields, single-use or standing | Menu, locations, tipping, review prompts | Pages, products, branding — all editable |
| Your processor | Stays yours | Stays yours | Stays yours | Stays yours |
PLACEHOLDER: time-to-live figures — relative today, pending verification against real onboarding data
Your rails
Works with your processor
Processor-agnostic. Integrations on request. We do not publish a list of supported providers, because naming one is a commitment to a live integration rather than an intention. Tell us what you run and we will tell you plainly whether it works today.
Tell us what you sell and who buys it.
Where you operate, what you sell into the Philippines, and whether you have a Philippine entity yet.
The questions everyone asks first
No. A processor authorises transactions and handles the money on your behalf. A PayMongo channel is the layer above that — the page, sheet or menu your customer actually uses — and it runs on the processor you already contract with. You are buying this alongside your provider, not instead of them.
No. Your processor does, exactly as it does today. We render the surface your customer pays on; the transaction is authorised and the money handled by the provider you already contract with.
If your processor's checkout fits your business, use it — we will tell you that on the call. The layer earns its place in three situations: the hosted surface you have is weak or missing, you need a channel your processor does not offer at all (QR ordering at a table, a generated storefront, a link per invoice), or you want the experience to stop being tied to the rail so changing processor later is a credentials change rather than a rebuild.
No. Keeping the one you have is the entire point of a channel layer. If a proposal requires you to open a new merchant relationship, it is not this one.
They stay with your processor and in the tooling you use for them now. We do not stand between you and a chargeback, and we do not add a second place to look.
PLACEHOLDER: regional availability — the honest list, including the markets we cannot serve yet and why
Two separate bills. You pay us for the experience layer; your processor keeps charging you for processing on the terms you already agreed. PLACEHOLDER: commercial decision — the experience-layer figures are not set yet.
The no-code channels can be live the day your processor is connected. Checkout takes longer because it touches your backend. We will give you a real answer on the first call rather than a number on a page.