Google Pay uses the shared wallet options described in Wallets plus a few Google-only extras.
Example
Availability
Google Pay renders on Chromium-based browsers. It requires HTTPS in production.
Merchant identity and the Google Pay environment come from your Overflow merchant configuration. You do not pass a merchant id from the SDK.
buttonSizeMode is also available; refer to Google’s platform documentation for accepted values.
Requirements
Google exposes several parameters via requirements that layer on top of the ones the SDK derives from require:
billingAddressParameters is merged on top of the derived parameters.
shippingAddressParameters is passed through verbatim.
shippingOptionRequired is passed through verbatim.
transaction is built in full
Google Pay rejects partial transactionInfo. The SDK builds the full request from transaction.{amount, currency, countryCode, label, lineItems}. Always pass all four top-level fields when you want a chargeable sheet.
Collecting the shopper’s name
Google Pay returns the shopper’s name as part of the billing address. Set require.billingAddress: true to receive it.
Recurring payment requests are Apple Pay-only.
See also
Last modified on July 29, 2026