Google Pay: Global's digital wallet
Google's tokenised card wallet across Android, Chrome and the web — plus a distinct UPI product in India.
How the Google Pay flow works
Outside India, Google Pay stores tokenised card credentials linked to the shopper's Google account. At checkout the shopper taps a Google Pay button and authorises via device biometrics or Google account confirmation; the transaction rides the underlying card network with a network token and cryptogram.
In-person, Android devices with NFC replay the tokenised card as a contactless EMV transaction on standard terminals.
In India, Google Pay is a UPI app: payments are bank-to-bank via NPCI rather than card-based (see the UPI page). The consumer UX overlaps but the rails are different.
Merchants integrate via the Google Pay API for Web or Android; from an acquiring perspective it settles as a normal card transaction (or as UPI in India).
Typical use cases
- Android-first mobile checkouts where manual card entry hurts conversion.
- Chrome-based desktop checkouts leveraging saved Google account payment methods.
- In-person contactless payments on Android.
- Indian merchants: Google Pay is one of the top UPI apps by usage.
Consumer reach
Very broad reach globally across Android devices and Chrome users.
In India, one of the leading UPI apps with hundreds of millions of users.
Who should accept Google Pay
- Any merchant with meaningful Android traffic.
- Indian merchants — Google Pay is table stakes as a UPI acceptance option.
- Merchants running Chrome-heavy web checkouts.
Operational detail
The operational half of every method profile — settlement, refunds, disputes, PSP coverage and licensing — is reserved for Payment Methods List founding partners. It's the part vendor sites won't publish and the part that actually decides whether Google Pay works for your stack.
Settlement time
When Google Pay balances actually clear from the wallet operator to a merchant account, how top-up float and P2P legs distort the timeline, cut-offs on the operator side, and which PSPs pass funds through same-day vs. hold a reserve.
Book a founding-partner call →Refund mechanics
How Google Pay refunds flow back to the payer's wallet balance vs. their funding source, partial-refund support, time windows before a refund becomes an off-platform transfer, and the exact PSP API calls used when the wallet has no native reversal.
Book a founding-partner call →Chargeback exposure
Whether Google Pay supports scheme-style chargebacks, the operator-run dispute program that sits alongside, actionable reason codes, evidence formats accepted, and observed net loss rates versus cards on the same basket.
Book a founding-partner call →PSP coverage matrix
Which acquirers, MoRs and wallet-aggregators actually process Google Pay in Global today, whether coverage is direct or piggy-backed on a scheme rail, effective pricing bands, and where the operator has restricted new merchant onboarding.
Book a founding-partner call →KYC & licensing notes
What a merchant needs to legally accept Google Pay in Global, whether the wallet operator or the PSP is the regulated entity, KYC and AML obligations that flow down to the merchant, and cross-border MoR options.
Book a founding-partner call →