Accept Google Pay
Offer Google Pay on the hosted payment page: what your payment provider needs, how the payment flows and what to test before going live.
Mintcash supports Google Pay wherever the underlying payment provider does, and what you need to set up depends on that provider. This guide walks through what it requires of you, the integration path, and what to test.
Before you start
You need a payment provider with Google Pay enabled, and your Google Pay merchant ID, gateway ID and credentials set up on their side. Send these to your account manager, and that's it: we handle all the configuration on our side.
Integration
Your integration is exactly the one-time payment flow — create the payment, send the customer to the redirectUrl, fulfil on the webhook. When Google Pay is enabled and the customer's browser supports it, the payment page shows a Google Pay button alongside the card form.
- You create the payment; we respond with the
redirectUrl. - The payment page displays the available payment methods, including Google Pay.
- Google Pay authenticates the customer and returns the encrypted payment data, which we pass to the provider.
- If the issuer requires extra verification (3DS or OTP), the customer completes it in place on the page — Google Pay charges backed by an on-file card (rather than a device-bound token) step up to 3DS routinely.
- We send the webhook to your
callbackUrlwith the final state.
Google Pay is for one-time payments
Google Pay charges are not tokenised for reuse — they never produce a saved card token, and they can't fund a subscription's renewals. Use the card flow for subscriptions and saved-card charges.
A Google Pay-only page or frame
To offer Google Pay on its own, create the payment with methods: ["wallets"] and open the page with ?view=google_pay, or embed that URL as one frame of your own checkout next to a card frame of the same payment. A wallet-only frame posts mintcash:wallet with wallet: "google_pay" once it knows whether Google Pay works on the customer's device, so you can hide it when it doesn't. The rules are in Choose what the checkout offers; the behaviour of a wallet-only page is described under Accept Apple Pay and is the same for Google Pay.
What to test
Run each flow you plan to ship in sandbox before going live:
- Happy path — a Google Pay authorisation that lands on
payment.succeeded. - 3DS challenge — confirm the challenge renders and finalises successfully.
- Webhook delivery — confirm your endpoint receives the final event.
Accept with a saved card
Charge a returning customer's saved card with its token, server to server: no hosted page and no redirect.
Accept Apple Pay
Offer Apple Pay on the hosted payment page, as a wallet-only page or as a standalone button: what to send your account manager, how the payment flows and what to test before going live.