Wallets · Available
Google Pay
Google Pay is Google's wallet for a payer's cards on Android and in the Chrome browser: a card added on an Android device is tokenised, and a card saved to the Google account is passed to the acquirer for a normal authorisation with 3-D Secure where required. Either way it is a card payment with the scheme's settlement, refunds and chargeback rules, minus the card entry.
Key facts
- Countries
- United Arab EmiratesArmeniaArgentinaBrazilCanadaChileColombiaGermanyEgyptSpainFranceUnited KingdomIndiaItalyKyrgyzstanKazakhstanMexicoNetherlandsPeruPolandSaudi ArabiaThailandUnited StatesUzbekistanVietnam
- Currencies
- USD, EUR, GBP, PLN, CAD, BRL, MXN, ARS, CLP, COP, PEN, AED, SAR, EGP, INR, KZT, KGS, UZS, AMD, VND, THB
- Operations
- Pay-in · Recurring · Refund
- Settlement
- T+1
- Chargebacks
- under the scheme rules
How a payment goes through
- 1The checkout opens the wallet app or shows its button
- 2The payer confirms in the app with a PIN or biometrics
- 3The wallet confirms the payment to the provider within seconds
- 4Webhook to the merchant; a refund goes back the same way
How a payment goes through
- The checkout shows the Google Pay button in Chrome or an Android app.
- The payer picks a card and confirms on the device.
- The acquirer receives the token or the saved card, runs 3-D Secure if needed and authorises in seconds.
- Tranzify writes the result and calls the merchant’s webhook.
Google Pay against Apple Pay
| Google Pay | Apple Pay | |
|---|---|---|
| Launched | 2015 as Android Pay, Google Pay since 2018 | 2014 |
| Devices | Android, and the Chrome browser on any platform | iPhone, iPad, Mac |
| Card data | a device token, or a card saved to the Google account | a device token |
| Authentication | cryptogram for a tokenised card; 3-D Secure for a saved card where required | Face ID or Touch ID |
| Settlement and chargebacks | as the underlying card: T+1, scheme rules | the same |
| Recurring | yes, by a merchant token | yes |
Payouts and refunds
Refunds go back to the underlying card through the acquirer. Recurring charges use the token the acquirer stores after the first payment. Payouts are not part of Google Pay; card payouts go over Visa and Mastercard.
Who uses it
E-commerce, delivery and digital goods for Android payers who do not want to type a card; SaaS and travel as a one-tap option beside cards and Apple Pay.
How to connect
- 1Onboard with Tranzify and get your network, keys and back office.
- 2Enter your account with the provider in the terminal settings — Tranzify already speaks its API.
- 3Add routing rules: countries, currencies, amounts, BIN ranges, priorities and weights.
- 4Go live. Every payment, callback and retry is in the journal for five years.
Providers offering this method
Industries
Terms
Frequently asked questions
Where does Google Pay work in the catalogue?+
Is 3-D Secure needed?+
Who is the licensed party?+
Related methods
See the platform on your own flows
Thirty minutes with an engineer, not a sales deck: your providers, your routing rules, your merchants' checkout.
- ✓ Not a financial institution
- ✓ Money never passes through us
- ✓ Built to PCI DSS requirements