Skip to main content
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.

buttonType and buttonColor

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.

Not supported on Google Pay

  • Recurring payment requests. Use Apple Pay’s recurringPaymentRequest for that surface; Google has no equivalent.
  • name requirement flag. Name is included with the billing address automatically when billing is required.

See also

Last modified on July 17, 2026