← Back to brand directory

Wallet

Maya payment acceptance

Maya is treated as a wallet. The customer sees it as a payment option, while the merchant must confirm who provides onboarding, settlement, refunds, and support.

1Market entriesExisting channel URLs kept
1MarketsFrom public channel data
2Provider recordsPublic provider library
5Contact leadsPublic PSP contact feed

What this brand represents in LocalPayMap

Maya is treated as a wallet. The customer sees it as a payment option, while the merchant must confirm who provides onboarding, settlement, refunds, and support.

This is a brand-level overview, not a live quote, official pricing page, endorsement, or onboarding guarantee. Country pages explain local payment habits; PSP contact records explain who may be able to connect your business.

Merchant brand notes

Maya is framed on LocalPayMap as a wallet or account-based checkout brand. Use this page to understand its merchant role, then compare it with wallet, PSP, platform, and local method options for the target market and checkout model. Before implementation, ask the official provider or partner to confirm market route, direct or PSP access, buyer flow, refunds, settlement currency, reporting, and integration.

How merchants should read this brand

Read Maya as a neutral brand-context page. It explains the payment role to investigate, while country and compare pages hold market-specific checks.

Where it fits in a shortlist

Place Maya beside wallet, PSP, platform, and local method options when the buyer journey or country page suggests a relevant route. Keep a fallback route for comparison.

What to verify with the provider

Ask the official provider or partner to confirm market route, direct or PSP access, buyer flow, refunds, settlement currency, reporting, and integration before contracts, build work, or launch dates.

Record-specific caution

Use Maya as a payment-method or wallet-route verification page across Philippines. Confirm whether merchant access is direct, PSP-enabled, acquirer-enabled, bank-enabled, or platform-enabled, then verify entity fit, checkout flow, refunds, disputes, reconciliation, settlement owner, and support path.

Merchant usage and connection route

Maya in the payment stack

Maya is relevant for Philippines merchants that want wallet, QR, online checkout, or local business payment acceptance under the Maya brand. Merchants should decide whether Maya is needed as a direct wallet relationship, a PSP-supported payment method, or part of a broader Philippines checkout mix.

Connection route

A merchant may approach Maya Business directly or use a Philippines PSP, gateway, aggregator, or commerce platform that offers Maya-related acceptance. Verify which product is being sold, who handles onboarding, whether QR or online checkout is supported, and how settlement, refunds, and support are assigned.

Verification questions

  • Is the intended Maya route wallet checkout, QR acceptance, card acquiring, or another business product?
  • Will onboarding be direct with Maya Business or through a PSP, gateway, or platform?
  • Which Philippines entity, store, website, or app must be reviewed before activation?
  • How are wallet payments, QR payments, refunds, reversals, and failed attempts reported?
  • What customer instructions and branding are required in checkout or at point of sale?

Merchant caveats

  • Maya product scope can differ between wallet, gateway, QR, and business services.
  • PSP availability is not proof of direct Maya merchant eligibility.
  • Operational handling for refunds and disputes should be confirmed before launch.
  • Do not generalize Philippines wallet behavior to other markets.

Provider examples to verify

Maya BusinessPayMongoWitpay

Related markets

Philippines

Keep researching

This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.

Sources

Why merchants ask about it

Merchants ask about Maya because buyers may recognize it at checkout. The next question is whether the merchant can connect it directly, through a PSP, or only through a local partner.

Role clarification

Brand type
Wallet
Payment types
Wallet
Related countries
Philippines
Country URLs
Market-specific entries remain available for country research.

Related market links

Market-specific entries

Each row below is a country or payment-scenario record. It is kept because the same brand can behave differently by market, entity requirement, settlement route, and provider coverage.

Related PSP contact leads

These public contact routes are prioritized toward official forms, contact pages, and direct public routes when available. Confirm market scope, merchant eligibility, pricing, settlement, and support coverage directly before relying on any listing.

Philippines · PSP / aggregator

Bayad (CIS Bayad Center, Inc.)

Bayad's network is domestic and physical, and it has been extended to serve overseas Filipino workers paying bills at home. A foreign merchant would use it as a collection channel rather than as an acquirer.

Philippines · PSP / aggregator

Dragonpay via Xendit

online bankingover-the-counter cashe-walletsbank payments

Philippine ecommerce merchants needing local alternative payment coverage, especially non-card bank and cash-based options.

Philippines · Wallet operator

Maya Business

Maya walletcardsQR Phcheckout

Philippine merchants that need wallet, card, QR, payment-link, terminal, and direct checkout options under a large local regulated payments brand.

Philippines · Payment gateway

PayMongo

cardsGCashMayaQR Ph

Philippine SMEs, ecommerce merchants, marketplaces, SaaS, social sellers, and platforms needing API, payment links, QR Ph, cards, and local wallet acceptance.

Next actions for merchants

Use this brand page as a navigation layer. Before outreach, narrow the target market, decide whether you need a PSP, gateway, acquirer, wallet operator, or platform route, then confirm eligibility directly with the provider.

Questions merchants ask

Is Maya a recommendation from LocalPayMap?

No. The page is a neutral brand reference to help merchants ask sharper questions and compare routes for a specific market.

Can merchants assume Maya fits every country page?

No. Availability, onboarding, currencies, documentation, and payment flows should be checked for the target country and business model.

What should be checked before adding Maya to checkout?

Confirm the official route, merchant eligibility, integration owner, refund and dispute handling, reporting fields, settlement currency, and pricing model.

FAQ for first-time merchants

Can a cross-border merchant accept Maya?

Possibly through a PSP, bank, acquirer, aggregator, or local partner. The brand name alone does not prove that offshore merchant onboarding is available.

Do I need a local company or local bank account?

It depends on the country, industry, transaction model, and provider route. Some wallet records can be reached by cross-border merchants; others require a local entity, local bank account, local tax registration, or extra licensing.

Are fees and settlement terms fixed?

Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.

What should I ask before integration?

Ask who signs the merchant agreement, which countries and currencies are covered, whether your industry is allowed, how refunds and disputes work, whether reserves apply, what settlement timing is available, and which official contact route handles onboarding.

Is this page the same as a country payment-channel page?

No. This page explains the brand-level role. A country payment-channel page shows how the brand appears in one country or payment scenario.

Pricing note

Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.