Payment methods look like features. You add GCash, then Maya, then cards, the way you'd add a size filter to a product page. Underneath, each one is its own business relationship, with a separate contract, its own approval process and its own way of sending you money.
That's why "should we just integrate directly?" comes up so often, usually once a business starts paying meaningful transaction fees every month. Cutting out the middle layer sounds cheaper, and for a few companies it is. For most, the fee they save ends up smaller than the work they take on.
This article walks through what going direct involves in the Philippines, the costs that tend to show up later, and the situations where building your own integrations does make sense.
What going direct actually involves
The short answer is that you'd be signing up with each provider separately, and not all of them will take you.
Start with e-wallets. GCash's API portal is open only to selected partner organizations. There's no public application form. You reach out, get assigned an account manager if your volume justifies one, and go through their business verification. Most small and mid-sized merchants don't reach that point, which is why so many online GCash checkouts run through a gateway. Maya, GrabPay and ShopeePay each have their own process, so going direct with all four means four sets of paperwork and four integrations.
Cards are a different kind of work. You'd need a merchant account with an acquiring bank, which means underwriting, a review of your business and its refund history, and possibly a reserve held against chargebacks. Then there's PCI DSS. A merchant that sends customers to a gateway's hosted checkout usually qualifies for SAQ A, a short self-assessment. Build your own card form or store card numbers for repeat buyers, and you move to SAQ D, which covers all 12 PCI DSS requirements and runs to more than 300 controls.
QR Ph and online banking are the hardest to do alone. QR Ph merchant acquiring is done through BSP-supervised banks and e-money issuers, so a merchant can't plug into it on its own. You'd still be going through a bank, just a different one for each channel.
There's also the regulatory side. If your setup starts to look like you're collecting or moving money for other people, for example as a marketplace or a platform with sub-merchants, the BSP may consider you an operator of a payment system under the National Payment Systems Act. That comes with registration and ongoing oversight. The BSP also floated a 12-month pause on new operator registrations in September 2026, so that path may not even be open for a while.
The costs that show up after launch
The build itself is the part teams plan for. A developer reads the docs, wires up the API, tests it and ships. What's harder to see from the planning stage is everything that has to keep running afterward.
Reconciliation is usually the first surprise. Every provider settles on its own schedule and sends its own report, in its own format. Say you sell skincare online and go direct with GCash, Maya and a card acquirer. On Monday morning your finance person opens three portals, downloads three settlement files, and matches them against last week's orders by hand. GCash paid out Friday's sales but Maya hasn't yet, and the card file nets out a refund from two weeks ago. Nobody is doing anything wrong. It's just three systems that were never meant to agree with each other, and someone on your team now owns making them agree.
Cash flow gets harder to read too. With one gateway, you get one payout schedule. With four direct relationships, you have four, and each one treats holidays and cutoffs differently.
During Holy Week or the December rush, when several banking days drop out at once, it's hard to say on any given day how much money is actually on its way to you.
Then there's maintenance. Providers update their APIs, retire old versions, change how they report failed payments, and roll out new security requirements on their own timelines. Each change lands as a ticket for your engineering team, usually when they're in the middle of something else. If the developer who built the GCash integration leaves, the knowledge of how it works often leaves with them.
Compliance doesn't go away either. If you handle card data yourself, PCI DSS becomes a yearly assessment with real security work behind it. You also carry the fraud and chargeback handling a gateway would normally help with, from deciding which payments to block to fighting disputes with the card networks.
None of these is a deal-breaker on its own. Together they add up to a small payments team, and that's the real cost to weigh against the fee you'd save.
When building direct makes sense
There are businesses where going direct is the right call. They tend to share a few traits.
Volume concentrated in one method is the most common reason. A ride-hailing app or a large telco where most customers pay with GCash may process enough through that one channel to get a partner rate and a dedicated account manager. At that scale, a fraction of a percentage point is real money, and the company likely already has engineers whose full-time job is payments.
Some products also need things a gateway doesn't offer. If you need a custom checkout flow inside a super app, special data fields passed to the bank, or settlement in a structure no gateway supports, building it yourself may be the only way to get it.
And sometimes the business is turning into a payments company itself, such as a platform that wants to hold funds for sellers and pay them out.
At that point you're probably dealing with the BSP directly anyway, and owning the integrations is part of the plan.
If none of those describe you, the more common middle path is to use a gateway for everything and revisit the question once one payment method makes up most of your volume. You can still negotiate rates with a gateway as you grow, without taking on the maintenance.
Build vs. buy, side by side
Here's how the two approaches compare on the things that tend to matter a year in.
Where PayMongo fits
PayMongo is the gateway option in this comparison. One integration gives you cards, GCash, Maya, GrabPay, ShopeePay, QR Ph and online banking, with published rates on the pricing page. If you'd rather not write any checkout code, Hosted Checkout keeps card data off your servers entirely.
If your team is already halfway into a direct GCash or card build, it's worth pricing out the reconciliation and maintenance work before you finish. And if you're comparing gateways, our breakdown of Maya vs GCash vs PayMongo for business covers the differences.
Frequently asked questions
Can I integrate GCash directly without a payment gateway?
Only if GCash accepts you as a partner. Its API portal is limited to selected organizations, and access usually goes through an account manager. Most businesses accept GCash through a licensed gateway instead.
Is a payment gateway more expensive than going direct?
Per transaction, a direct rate can be lower once your volume is large. But the gateway fee also covers the integrations, payouts, reconciliation, fraud screening and compliance work you'd otherwise staff yourself.
Do I need to be PCI compliant if I use a gateway?
Yes, but the scope is much smaller. A merchant using a hosted checkout usually completes the short SAQ A. Handling card data yourself moves you to SAQ D and the full set of PCI DSS requirements.
Do I need to register with the BSP to accept online payments?
A merchant selling its own products through a gateway generally doesn't. A business that collects or moves money on behalf of others may be treated as an operator of a payment system under the National Payment Systems Act and need to register. Check with a lawyer if your model involves sub-merchants or holding funds.
Can I switch from a gateway to direct integrations later?
Yes. Many businesses start on a gateway and move one high-volume method in-house later, while keeping the gateway for everything else.