A branded payment gateway for casino Philippines operators who already know that GCash is the deposit story, PayMaya is the second name on every Filipino phone, and InstaPay is how cross-bank money actually moves. Your domain, your colors, your merchant relationships — running on infrastructure that treats Philippine e-wallets and bank rails as first-class rather than as long-tail global checkboxes.
Two-part pricing: monthly hosting fee plus 0.1%–0.4% transaction share. Aligned with your channel's performance.
The Philippines is an e-wallet-first country with one of the most mature digital-payment user bases in Southeast Asia. The two-wallet pattern — GCash and PayMaya on every smartphone — is so universal that a casino cashier missing either name does not look budget; it looks suspicious. Filipino players notice when a deposit page does not match the wallet pattern they use for everything else.
GCash, operated by Mynt (a joint venture involving Globe Telecom and Ant Group), is the dominant Filipino e-wallet by user base and the primary deposit method on virtually every Philippine-facing casino cashier. PayMaya — now branded as Maya — sits as a strong second with its own user base and increasingly its own banking-style features through Maya Bank. InstaPay is the BSP-supervised real-time retail payments system that handles cross-bank transfers, including most account-to-account flows in the country.
The PAGCOR dimension is what makes the Philippines structurally different from every other market in our coverage. The Philippine Amusement and Gaming Corporation regulates domestic gaming and licenses certain online gaming categories. Operators serving the Philippine market split into those operating under PAGCOR licensing and those operating from offshore jurisdictions targeting non-Philippine players from a Philippine-domiciled support footprint. The compliance posture differs sharply between the two; the payment infrastructure pattern is similar but with different banking-partner expectations.
Player payment behavior is the unifying piece. Whether the operator is PAGCOR-licensed serving local Filipino players or offshore-licensed serving a different base, the cashier still has to lead with GCash to convert at the rate the market expects. The Filipino e-wallet pattern is too deeply embedded in consumer behavior to be replaced by a card form, regardless of the operator's jurisdiction.
Regulatory note. iGaming regulations in the Philippines involve PAGCOR licensing for domestic operators and a separate posture for offshore operators serving non-Philippine players. The regulatory environment continues to evolve. We work with operators who hold appropriate licenses or operate from offshore jurisdictions in line with their counsel's guidance. We provide payment infrastructure; clients are responsible for their own regulatory compliance.
The four failure modes below are the ones we hear most often when a Philippine-market operator arrives on our platform after running into the limits of an international processor or an aggregator-wrapped wallet integration.
International processors with global merchant footprints almost never have a working GCash integration; the few that do route it through aggregators with thin partnership relationships. Aggregator-wrapped GCash integrations break in predictable ways — partner-side API changes are not propagated, fee structures shift without warning, and the operator finds out via a spike in deposit failures rather than a partner notice. Direct partnership integration is the difference between a GCash button that works and one that fails on Saturday night.
Operators running under PAGCOR licensing operate in a regulatory framework that imposes specific reporting, segregation, and partner-vetting requirements. A generic payment processor is not built for the audit posture PAGCOR-licensed operators need. The mismatch shows up at the worst possible moment — during a regulator review, when reporting that should have been clean is suddenly the centerpiece of a stressful conversation. Our infrastructure produces transaction-level detail in the format Philippine compliance work actually needs.
Operators with offshore-domiciled corporate structures processing PHP deposits typically face a settlement-currency conversion at every cycle, plus the reconciliation overhead of mapping PHP rail data to a non-PHP operating ledger. Operators settling in PHP through Philippine banking partners have a different set of requirements driven by BSP oversight. Either pattern is workable; neither is workable on a generic processor that treats PHP as a long-tail currency.
Filipino players have a particularly strong "does this cashier feel Filipino?" filter. A cashier loading in English (which many Filipino players read fluently) but missing GCash and Maya entirely reads as a foreign site that wandered into the market. A cashier that names both wallets, surfaces InstaPay for bank-rail flows, and feels like the rest of the player's phone earns the deposit. The trust gap between the two cashiers is the gap between a Filipino-feeling product and a foreign-feeling one — and Filipino players notice it immediately.
Two e-wallets, one inter-bank rail, plus card and bank-rail support where it makes sense. The two wallets carry the conversion; InstaPay carries the bank-anchored cohort.
Dominant Philippine e-wallet operated by Mynt. Default deposit method for the majority of Filipino casino and sportsbook players. GCash for casino payment →
Second-pillar Filipino e-wallet now branded as Maya, with growing banking-style features. Distinct user base from GCash; treated as a named first-class method.
BSP-supervised real-time retail payments rail. Handles cross-bank account-to-account flows and the deposit cohort that prefers bank-anchored transactions.
Batch-cleared bank rail for higher-ticket flows where same-day rather than instant settlement is acceptable. Used for VIP deposit cohorts and selected operator-side patterns.
Visa and Mastercard configured where issuing-bank approval rates make it worth offering. Honest about the fact that GCash and Maya carry the bulk of Filipino deposits, not cards.
Withdrawals back to GCash and Maya wallets, or via InstaPay to bank account. Time-to-payout tuned for the rail behavior Filipino players expect.
The deployment shape is the same as any other tenant on our platform. The Philippine-specific configuration sits in the rail integrations, the compliance reporting, and a cashier that actually feels Filipino.
GCash and Maya are integrated through structured partner relationships rather than aggregator-wrapped. That difference is invisible until a partner-side API change happens, at which point it becomes the only thing that matters. We work directly with the partners and propagate changes on the partner's timeline rather than waiting for an aggregator's sandbox to catch up.
For operators running under PAGCOR licensing, the reporting layer is built for the specific transaction-level detail audits look at: settlement timestamps, rail-specific identifiers, FX context where applicable, and segregation between operator-side and player-side flows. For offshore operators serving non-Philippine players, the same reporting layer adapts to their counsel's chosen audit posture. The data is flexible; the cleanliness is constant.
Player-facing flows are PHP. Operator settlement currency is configured at the float boundary — PHP for Philippine-banking operators, USD or other for offshore-domiciled operators. Reconciliation reports show PHP rail data and operator-currency conversions on the same row, which removes the manual stitching most Philippine-market finance teams put up with on generic processors.
Casino-vertical operators serving the Philippines should read the casino payment gateway page for vertical-specific deposit and withdrawal patterns. Sportsbook operators — particularly those running NBA, PBA, or major boxing windows — should review the sports betting payment gateway notes. The broader operator-focused solution overview covers the integration model end-to-end.
Philippine-market operators frequently also serve other Southeast Asian markets, sometimes alongside South Asian footprints. Each is a distinct deployment with distinct rails — there is no shared cashier configuration that works across the region.
MoMo, ZaloPay, and VNPay as the rail story. Vietnam payment context →
Volatile rail availability; routing adapts as the landscape shifts. Myanmar operator notes →
UPI-led with IMPS, Paytm, and PhonePe. payment gateway in India →
We also operate in Pakistan (JazzCash/Easypaisa-led) and Bangladesh (bKash-dominant). The main payment platform overview ties the regional picture together.
Two-part pricing: monthly hosting fee plus a 0.1%–0.4% transaction share. Philippine deployments run with a different cost profile depending on whether the operator is PAGCOR-licensed and settling locally or offshore-domiciled and settling in another currency. Quotes reflect the actual rail mix, settlement pattern, and reporting requirements rather than a public rate card. See the pricing model or message us on Telegram.
Questions specific to running a branded payment channel into the Philippine iGaming market.
Tell us your monthly PHP processing volume, your iGaming platform, your licensing posture, and the rail mix you expect — wallet-led, balanced, or bank-anchored. We will tell you within an hour what a branded payment gateway for casino Philippines on our infrastructure looks like for your operation.