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 viarequirements that layer on top of the ones the SDK derives from require:
billingAddressParametersis merged on top of the derived parameters.shippingAddressParametersis passed through verbatim.shippingOptionRequiredis 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
recurringPaymentRequestfor that surface; Google has no equivalent. namerequirement flag. Name is included with the billing address automatically when billing is required.