Maya Native Payment in the Philippines: How It Differs from GCash and How to Integrate

What Is Maya? The Other Major Player in the Philippine Digital Wallet Market

GCash is most people's first association with digital wallets in the Philippines, with over 90 million registered users (see What Is GCash for a fuller introduction). But the Philippine digital payments market isn't a one-wallet story. Maya is the other major player at a comparable scale. Together, GCash and Maya cover the vast majority of the Philippines' active digital users, and QR code payments now account for more than half of all digital transaction volume by count. In practice, a merchant who only accepts GCash and skips Maya is turning away a real slice of customers who would otherwise happily pay by scanning a code.

Like GCash, Maya has to be recognized by the central bank (Bangko Sentral ng Pilipinas, BSP) as an Operator of Payment Systems (OPS) to legally process payments or fund transfer solutions, and separately needs Electronic Money Issuer (EMI) status to issue e-wallet balances. Both licenses are approved by BSP, which reviews an applicant's actual capital strength, operational capability, and governance — a process that typically takes quarters, not weeks. That's worth keeping in mind whenever someone claims they can set you up with Maya overnight.

Maya vs GCash: Instead of Comparing User Numbers, Check Whose Name the License Is Under

Maya and GCash already share part of the same payment infrastructure. QRPH (QR Ph) is a nationwide unified QR code standard led by BSP — it doesn't belong to any single wallet. A merchant that sets up one QRPH code can be scanned by GCash, Maya, and apps from dozens of participating banks to complete payment. The underlying technology follows the internationally common EMVCo QR framework, the same logic used by Singapore's SGQR and Thailand's PromptPay. On the simple question of "can I scan one code and pay," GCash and Maya are converging fast at the consumer-experience layer.

What's actually worth a merchant's attention isn't who has more users or a nicer app — it's which legal entity the license sits under. Behind the same brand name, the company actually processing payments may hold OPS, EMI, or both, and which combination applies to a given brand shouldn't be assumed from brand reputation alone. BSP publishes a public list of registered Electronic Money Issuers and Operators of Payment Systems, so merchants can independently verify the license number and registered company name a provider gives them. Not everyone who claims to handle "Maya integration" actually holds a BSP OPS or EMI license — undisclosed white-labeling and subcontracting do happen. Fee structures, settlement cycles, and the number of channels each provider supports also vary, so it's worth comparing more than one option rather than skipping that step because a name sounds familiar.

From what we understand, SmartPay (paysmartph.com) handles GCash native integration, QRPH aggregated collection, and Maya disbursement, and holds OPS and EMI status issued by BSP. For the specific question of who to talk to about Maya native collection, it's worth asking them directly (Telegram: @LouisSMARTPAY) and verifying their credentials yourself — treat it as one option to compare, not the only one.

How Maya Native Payment Integration Actually Works

There are two common integration shapes: redirecting to a third-party checkout page, where the user temporarily leaves your own site or app, and "native" integration, where the user stays on your own page the whole time and scans a code or launches the Maya app with one tap. The second is what "Maya native payment" specifically refers to, and it typically converts better.

Three common ways to trigger it:

• Web-based H5 wake-up: suited to merchants without their own app, completed entirely in the browser;
• In-app SDK integration: suited to merchants who already have a native app, requiring the mobile team's involvement;
• Offline static or dynamic QR codes: common for retail and dining, and paired with QRPH, a single code can serve multiple wallets instead of needing separate codes for GCash and Maya customers.

The integration process generally follows the same framework: submit company documentation for due diligence to meet BSP KYC/AML requirements (a lot of this overlaps with what's needed to open a corporate bank account in the Philippines); once cleared, you get a sandbox environment where the technical team jointly tests order creation, payment callbacks, and refunds; before going live there's an acceptance check covering transaction reconciliation, payment success rate, and risk-alert mechanisms; only after that does the integration switch to production; and after launch, someone still needs to keep watching reconciliation and anomalies through the merchant backend's transaction reports — integration isn't a one-time task.

A few details worth asking about explicitly during sandbox testing, rather than discovering the hard way: whether payment results come through active polling or a pushed webhook callback; whether duplicate notifications for the same payment could cause double-booking, i.e. whether the interface handles idempotency; and whether refunds go back through the original payment method or as a separate transfer, and whether the arrival time matches the original payment. Settlement also comes in two common flavors — D0 same-day settlement and T1 next-day settlement — and not every provider does D0 uniformly, so it's worth confirming which applies, and whether exceptions exist, before signing on.

Why Many Merchants Integrate Both GCash and Maya Instead of Just One

Merchants who typically need this kind of integration include cross-border e-commerce sellers entering the Philippines, local online stores, subscription or pay-per-use services, chain retail and dining businesses with high-frequency small transactions, schools and training institutions collecting tuition, logistics and delivery platforms collecting cash-on-delivery payments, and agencies or service companies collecting deposits. These businesses share one thing in common: checkout conversion directly determines whether the business works.

As noted earlier, GCash and Maya together cover the vast majority of the Philippines' active digital users, and QR payments already account for more than half of all digital transaction volume. If a merchant only integrates one, loyal users of the other wallet won't see their preferred payment method at checkout — some will abandon the purchase or go to a competitor instead, a direct hit for any business that depends on conversion. For merchants relying purely on static offline QR codes, QRPH alone can cover GCash, Maya, and dozens of participating bank apps with one code. But for merchants building a native H5 wake-up or in-app SDK experience — avoiding redirects and keeping users on their own page — GCash's and Maya's interfaces and SDKs aren't the same, and each needs to be integrated and tested separately. That's why many merchants look for a provider that has already connected both GCash and Maya, turning what would be two separate integration efforts into one, rather than working through both sets of documentation from scratch.

None of this works, though, if the company itself isn't registered in the Philippines yet — payment providers doing due diligence will ask for registration documents, director information, and a business address, and without a registered entity this step generally can't move forward. It's worth handling company formation first, whether through company formation support or by working through the full guide to registering a company in the Philippines. Cross-border sellers who haven't mapped out their overall collection setup yet should also start with the overview page on Philippine payment gateways covering GCash/QRPH merchant collection, licensing, and settlement.

The Less Convenient Side: Integrating Maya Isn't a Hand-Off

Finding a licensed provider to help integrate Maya doesn't mean the merchant can walk away. KYC and anti-money-laundering documentation that has to come from your own company still has to come from your own company — no provider can sign or stamp that on your behalf.

The systems behind Maya and GCash also get updated periodically, with interfaces or rules changing from time to time. Integration isn't a set-it-and-forget-it task; once it's live, someone still needs to keep watching reconciliation and anomaly alerts on an ongoing basis.

Official Sources

Like GCash, Maya needs BSP-recognized OPS status to process payments or fund transfer solutions, and EMI status to issue e-wallet balances, with both licenses approved by the central bank. For the official introduction and technical standard behind QRPH, see the central bank's public materials: Bangko Sentral ng Pilipinas (BSP). To verify a provider's or a brand's underlying registered company, check the Securities and Exchange Commission (SEC) registry. (Last verified: September 2026.)

About this guide and Yixing

Want someone to check your documents against the current requirements? → Yixing can review your case with you

Yixing is a private consulting company registered in the Philippines (SEC Reg. No. CS202009551; BI Accreditation No. CA-202624381-1). This guide does not name or rate other providers and does not promise any outcome; approval rests with the competent authority, and the rules in force are those it currently publishes. For legal disputes or case-specific judgments, consult a practising lawyer — this is not legal advice.