Google Pay · Android
Google Pay integration in a web app
A Google Pay integration means Android and Chrome customers can pay with a card stored in Google Wallet through your gateway. Like Apple Pay, it is a gateway feature in practice. You build display, fallback and a test matrix — not a secret Google acquirer. In Denmark MobilePay comes first. Google Pay is a supplement if your gateway has it enabled and you have Android-heavy traffic. The test matrix belongs in the quote: Chrome plus Android with and without Google Pay, Safari and iOS that fall back cleanly, and corporate cards that refuse tokenisation. If you only test on the developer’s Pixel, launch day will fail.
Google Pay does not replace MobilePay. It is an extra button for people who already have the card in Google. Payments.
Test matrix for a Google Pay integration
- Chrome + Android with Google Pay set up
- Chrome + Android without
- Safari / iOS — must fall back cleanly
- Corporate cards that refuse tokenisation
Detect
Gateway and browser say whether Google Pay is available.
Show or hide
No dead button on iPhone. No assumption about a Pixel.
Token
The wallet tokenises. You send the token to the gateway, not PAN.
Fallback
Card fields or MobilePay if the wallet refuses.
Google Pay or MobilePay first in Denmark
MobilePay first. Google Pay as a supplement if your gateway has it enabled and you have Android-heavy traffic. It is rarely first priority in a small package. Pricing.
Google Pay is typically the same integration as your gateway button, not a third acquirer track. Say so if you thought otherwise.
The Pixel test is not a test matrix
Write the four devices into the quote, or you will discover the corporate card on launch day. Tell us the gateway and whether Apple Pay is already enabled, so we do not build two buttons that hide each other. Contact.
FAQ: Google Pay integration
Google Pay or MobilePay first in DK?
MobilePay first. Google Pay as a supplement if the gateway has it and you have Android traffic.
Do you build directly against Google?
No. It is a gateway feature. You build display, fallback and tests.
Does Google Pay work on iPhone?
Rarely in the way customers expect. Hide the button and fall back to card or MobilePay.
Is it a separate integration in the package?
Often no if you are already building QuickPay or Stripe. Spell it in the brief so we do not count wrong.