GCash Card vs Maya Card: Visa Debit Cards Compared for Users, Travelers and Merchants (2026)
I run payments and integration for a company that onboards foreign merchants and developers in the Philippines, and the question "GCash Card vs Maya Card" reaches me from two very different directions. Expats and travelers want to know which card to carry. Developers want to know what happens on our side when a customer pays with one of them. This article answers both: what each card is, how you get it, where it works, how the controls differ, and then the part that matters to anyone running a checkout: a payment made with either card is a Visa card transaction, not a wallet transaction, and your integration, dispute handling and reconciliation have to treat it that way. Fees, limits and promotional terms change often and are deliberately left out; read them in the app at the moment you transact. For the broader question of which wallet to integrate as a merchant, see GCash vs Maya as merchant payment channels; this page is only about the cards.
What each card actually is: issuer, network and funding source
GCash Card. The GCash Card is a payment card powered by Visa, launched by GCash and Visa in October 2023. It is tied to the GCash wallet balance: what you can spend on the card is what you have loaded into the wallet. There is no separate card account, no credit line and no bank deposit behind it. Think of it as a Visa-shaped door to your e-money balance. A travel co-branded variant exists, but the mechanics are the same.
Maya Card. Maya offers two forms of the Maya Card, a physical card and a virtual card, and both are debit cards that draw on the Maya Wallet balance. Maya's cards run on Visa. The structure behind them matters more than it first appears: Maya operates two BSP-regulated entities, Maya Philippines, Inc., the payments and e-wallet business, and Maya Bank, Inc., a BSP-licensed digital bank. The wallet-funded Maya Card lives in the first world. Maya's credit cards, Maya Black and the Landers Cashback Everywhere card, are issued on the bank side and are a different product class: a credit line, a statement cycle and the underwriting that goes with it. Maya Black is a numberless physical Visa that earns Maya Miles and opened with early access in 2025; the Landers card is a Visa co-branded with Landers Superstore from 2024.
The one-line version: both are Visa cards spending e-money balances held at BSP-supervised electronic money issuers. The differences are form factor, in-app controls, the wallet ecosystem each one plugs into and, on Maya's side, a bank with credit cards next door.
How you get each card and who can
GCash. Any fully verified GCash user can order the card inside the app with no additional documents or approvals. The path is View all, then Manage, then Cards, then Order a GCash Card. Verification is the gate: if your account is not fully verified, finish that first. The physical card is delivered and then activated in the app.
Maya. The virtual Maya Card is created inside the Maya app at activation, with its own card number, CVV and expiry date, so it is usable online as soon as it appears. The physical Maya Card is either ordered in the app or bought at partner outlets, then activated and linked to your wallet. Maya's own material focuses on the activation steps rather than eligibility; in practice, as with any BSP-regulated wallet, expect to complete identity verification before the card does anything useful.
Expats and long-stay visitors. The real precondition is not the card but the wallet. Both cards require a Philippine wallet account in your name, which means a registered local mobile number and identity verification with documents the wallet accepts. If you are still at the registration stage, solve that before thinking about cards. Once the wallet is verified, ordering either card is the easy part.
Where each card works: online, in-store, ATMs, abroad and on your phone
Both cards are Visa, so the acceptance footprint is Visa's. GCash positions its card for online shopping on websites and apps, in-store payments by tapping or inserting at terminals, ATM withdrawals locally and abroad, and overseas spending wherever Visa is accepted; the card is contactless. Maya's physical card covers in-store contactless and chip payments, online purchases, and ATM withdrawals locally and internationally. Maya's virtual card is aimed at online payments, including international e-commerce, and anything else where a card number is typed rather than tapped.
The phone-wallet picture changed in 2026. GCash enabled Google Pay in February 2026. In September 2026 Maya and Visa extended their partnership so that Maya Visa cards, credit and wallet, physical and virtual, can be added to Google Wallet and used with Google Pay. If you pay with your phone at terminals, that detail narrows the practical gap between a virtual card and a physical one.
One thing that confuses people: in August 2026 GCash and Visa, and separately Mastercard, announced that eligible Visa and Mastercard cards can be linked to the GCash app to fund QR payments. That is the opposite direction from the GCash Card. It brings an external bank card into the wallet so you can pay a GCash QR code with it; it does not turn the GCash Card into something new.
| Dimension | GCash Card | Maya Card |
|---|---|---|
| Issuing side | GCash wallet, a BSP-supervised e-money issuer | Maya Philippines, Inc. (wallet); credit cards sit with Maya Bank, Inc. |
| Card network | Visa | Visa |
| Funding source | GCash wallet balance | Maya Wallet balance |
| Formats | Physical card; a travel co-branded variant exists | Virtual card and physical card |
| How to get it | Order in-app as a fully verified user, no extra documents | Virtual: activate in-app; physical: order in-app or buy at partner outlets, then link |
| Online payments | Yes | Yes, the virtual card is designed for it |
| In-store tap or chip | Yes, contactless | Yes, with the physical card or via Google Pay |
| ATM withdrawals | Local and abroad | Local and international, physical card |
| Phone wallets | Google Pay since February 2026 | Google Wallet and Google Pay since September 2026 |
| In-app controls | Card management in the app; GInsure coverage for unauthorized use in the initial period after activation | Virtual card lock, unlock and disable in-app; transaction history |
| Related credit products | None on the card side | Maya Black and Landers Cashback Everywhere, issued by Maya Bank |
Controls, security and protection
The virtual Maya Card is the strongest story here for anyone who worries about card-not-present fraud. It can be locked and unlocked at any time in the app, its transaction history is a tap away, and it can be disabled in a few taps. There is no plastic to lose or to have skimmed. Maya's material does not detail the same lock controls for the physical card; check your own app rather than assuming parity.
GCash's protection pitch is different: the card is contactless, and GInsure provides coverage for unauthorized transactions during an initial period after activation. I am not stating the coverage amount or the length of that period because both are the kind of term that changes; read it in the app when you order.
What the two share is structural. Both cards spend a wallet balance, so your exposure on a compromised card is capped by what you have loaded, not by a credit line or a salary account. That is a feature. My standing advice to staff and clients: keep only what you plan to spend in the wallet the card draws from, use the virtual card for subscriptions and unfamiliar websites, lock it between uses, and treat any call or message asking for your MPIN or a one-time code as fraud. Neither wallet asks for those.
Which card fits which user
- Everyday consumer. The card follows the wallet. If your salary, remittances or side income land in GCash, the GCash Card is the natural extension; if they land in Maya, the Maya Card is.
- Freelancer or online seller paid into a wallet. Either card turns platform payouts into something you can spend at a terminal or an ATM without routing through a bank account first. The Maya virtual card adds a clean way to pay for software and ad spend online while keeping the physical card in a drawer.
- Traveler. A physical card is what hotels, car rentals and ATMs want. Both work abroad on the Visa network; load what you need before the trip and check the in-app fee schedule for foreign transactions and withdrawals, which I will not quote here.
- Expat or long-stay visitor. Your constraint is wallet registration, not card choice. Pick the wallet whose onboarding you can clear with your documents, then take its card.
- Subscription-heavy online user. The Maya virtual card's lock and disable controls are built for this pattern.
- Someone who wants a credit card. Only Maya has one on offer through Maya Bank, and it is a separate application with credit underwriting. The GCash Card is a balance card, not a credit product.
My own answer when asked: if you use both wallets, hold both cards and let the funding decide which one you tap. If you use one wallet, take its card.
For merchants and developers: a card-funded payment is not a wallet payment
When a customer pays you with a GCash Card or a Maya Card, by typing the number into your checkout or tapping it at your terminal, you have accepted a Visa card transaction. Authorization, authentication, settlement and disputes follow card-network rules. The fact that the card is funded by an e-wallet is invisible to you and irrelevant to the rails. When the same customer pays by scanning your QR code or being redirected into the GCash or Maya app, you have accepted a wallet transaction: wallet-side authentication, wallet-side refunds, a different settlement path and a different dispute model.
Three consequences follow. First, you need card acceptance to accept these cards at all; integrating the GCash and Maya wallet channels does not cover them. Second, a card-funded sale carries chargeback exposure under network rules and needs the 3-D Secure result stored with the order, as discussed in 3-D Secure and card payment security; a wallet sale does not go through that program and is handled through wallet refund and dispute flows, covered in payment disputes and chargebacks. Third, reconciliation must tag the funding type on every transaction, or your finance team will chase a Visa settlement line for what they believe was a wallet payment. If you run a meaningful card volume, read card network chargeback monitoring programs before the ratios become a problem.
Compliance note: any provider that collects or disburses funds for merchants in the Philippines must be registered with the Bangko Sentral ng Pilipinas as an Operator of Payment Systems or licensed as an Electronic Money Issuer. Whether the funds arrive by wallet or by card, check the BSP OPS/EMI standing of the entity whose name is on your contract before you sign.
| Aspect | Wallet rail (GCash or Maya app, QR, redirect) | Card rail (GCash Card or Maya Card as a Visa card) |
|---|---|---|
| Who authorizes | The wallet, against the customer's balance | The card issuer via the Visa network, against the same balance |
| Customer authentication | Wallet MPIN or biometrics inside the app | 3-D Secure challenge or frictionless flow, plus CVV online |
| Dispute model | Wallet refund and dispute process | Card-network chargeback rules and reason codes |
| Evidence to keep | Wallet transaction reference, payer wallet identifier | Network reference, authorization code, 3-D Secure result, AVS or CVV result |
| Settlement path | Wallet or gateway settlement to your account | Acquirer settlement, typically on a separate schedule and statement |
| Integration surface | Wallet collection API or QR generation | Card acceptance: hosted page, tokenized fields or terminal |
| What the customer sees | Their wallet app | A card form or a terminal prompt |
In practice we expose both rails through one gateway API and let the checkout choose the method. The request shape barely changes; the payment_method value does the work. A card payment, with amounts as placeholders:
curl -X POST https://apix.example.com/api/pay \
-H "Content-Type: application/json" \
-H "X-Merchant-Id: M12345" \
-d '{
"merchant_order_no": "SO-20261023-0001",
"payment_method": "CARD",
"amount": "100.00",
"currency": "PHP",
"customer_email": "[email protected]",
"return_url": "https://shop.example.com/checkout/return",
"notify_url": "https://shop.example.com/payments/notify",
"sign": "<HMAC-SHA256 of sorted fields>"
}'Swap "CARD" for "GCASH" or "MAYA" and the same call invokes the wallet rail; whether the customer lands on a hosted card page or in their wallet app is a checkout design choice, compared in hosted checkout vs native checkout. The webhook is where the two rails must be separated, because what you store for a card sale is what a chargeback will later ask you for:
const crypto = require('crypto');
const SECRET = process.env.GATEWAY_SECRET;
function sign(payload) {
const base = Object.keys(payload).sort()
.map(k => `${k}=${payload[k]}`).join('&');
return crypto.createHmac('sha256', SECRET).update(base).digest('hex');
}
app.post('/payments/notify', (req, res) => {
const { sign: theirSign, ...data } = req.body;
const ours = sign(data);
if (ours.length !== theirSign.length ||
!crypto.timingSafeEqual(Buffer.from(ours), Buffer.from(theirSign))) {
return res.status(400).send('bad signature');
}
const order = orders.get(data.merchant_order_no);
if (!order || order.amount !== data.amount) {
return res.status(409).send('order mismatch');
}
if (data.funding_type === 'CARD') {
// Visa rail: keep what a dispute will ask for
order.network_ref = data.network_reference; // acquirer reference
order.auth_code = data.auth_code;
order.three_ds = data.three_ds_result; // e.g. 'AUTHENTICATED'
order.dispute_window_open = true;
} else {
// Wallet rail: GCash or Maya reference, wallet-side refund flow
order.wallet = data.channel; // 'GCASH' or 'MAYA'
order.wallet_ref = data.wallet_reference;
}
if (data.status === 'SUCCESS' && order.state !== 'PAID') {
order.state = 'PAID'; // idempotent transition
fulfil(order);
}
res.status(200).send('ok');
});Verify the signature before you read anything else from the body, compare order number and amount against your own record before you change state, and branch on funding type rather than channel name: a GCash Card payment reports as a card even though the money came out of a GCash wallet.
Frequently asked questions
Is the GCash Card a credit card?
No. It is a Visa card that spends your GCash wallet balance. There is no credit line. If you want a credit card tied to one of these ecosystems, Maya Bank issues them; GCash's card is a balance card.
Can I use the virtual Maya Card in a physical store?
By itself it is built for online use, where you type the card number. Since Maya Visa cards can be added to Google Wallet, tapping a phone at a terminal that accepts Google Pay is a practical route for in-store use. For an ATM you still need the physical card.
Can a foreigner get either card?
Yes, once the underlying wallet account is registered and verified in your name with a local mobile number and accepted identity documents. The wallet is the hurdle; ordering the card afterward is routine.
Do these cards work abroad?
Both are Visa and are positioned for overseas payments and ATM withdrawals. Check the in-app fee schedule for foreign transactions before you travel, because those terms are the ones that move.
As a merchant, do I need a separate integration to accept GCash Card and Maya Card payments?
You need card acceptance. A GCash or Maya wallet integration alone does not accept these cards, because a card payment runs on the Visa rail. Through a gateway that offers both, one API with a method field covers wallet and card, but the card side still needs its own hosted page or tokenized fields.
If a customer pays with a GCash Card and disputes it, does the dispute go through GCash?
No. It arrives as a card-network chargeback with a reason code, and you respond with card evidence: authorization, 3-D Secure result, delivery proof. Wallet dispute flows apply only to payments made inside the wallet app.
Which card is safer?
Both cap your exposure at the wallet balance. The Maya virtual card's lock and disable controls give you more day-to-day control for online use; GCash's card adds an insurance layer for unauthorized use in the initial period after activation. For most people the bigger safety factor is behavior, not brand.
Where I land
For users, the two cards are closer than the branding suggests: two Visa cards on two e-money balances, with Maya adding a virtual form and bank-issued credit cards, and GCash offering a straightforward physical Visa with an insurance sweetener. Pick the one attached to the wallet you actually fund. For merchants, the distinction that matters is not GCash versus Maya but wallet versus card: the same customer, with the same balance, can reach you on two different rails, and your checkout, webhook and dispute process must know which one they used.
SMARTPAY holds BSP OPS/EMI licenses and provides merchants in the Philippines with collection and payout integration across GCash, Maya, QRPH, InstaPay, PESONet and card acceptance, with funding type reported on every transaction so wallet and card settlements reconcile cleanly.
If you are deciding how to accept both wallet and card payments in the Philippines, reach out on Telegram at @LouisSMARTPAY or email [email protected].