FAQ

Why is the Google Pay button not showing?

A: The button appears only when the shopper session meets all requirements: Google Pay is enabled for the merchant, the currency and country are supported, and the device/browser are compatible. See Troubleshooting for diagnostics.

Does the merchant need a separate agreement with Google?

A: No direct contract with Google is required. However, the merchant must:

● accept Google Pay Terms of Service

● complete setup in Google Pay & Wallet Console (if applicable)

● provide required business and domain information

Is this Google Hosted Checkout?

A: No. This is not Google Hosted Checkout. Google Pay is rendered and controlled by Gateway. The merchant site redirects the shopper to Gateway checkout or loads a Gateway iframe — Google Pay appears inside that Gateway environment.

Which browsers and devices are supported?

A: Google Pay is supported on Android devices and desktops with a Google account that has a saved payment method in Google Wallet.
Compatible browsers: Chrome (Android and desktop), Microsoft Edge, Mozilla Firefox, and Opera. On iOS, Google Pay is supported in Chrome and Firefox — not in Safari.

Minimum requirement: a signed-in Google account with at least one saved card or payment method in Google Wallet.

Can the merchant use Google Pay in iframe checkout?

A: Yes. Gateway supports hosted checkout and iframe checkout. Google Pay in iframe is available only when the session meets all required eligibility rules.

How does testing work without real charges?

A: Gateway provides a TEST environment where you can complete the Google Pay flow without real charges. Test credentials are separate from production credentials. See Testing and Go-Live.

Which domains must be provided?

A: The merchant must provide all domains where Gateway checkout or iframe checkout will be loaded — test and production domains. See Merchant Onboarding.

Which countries and currencies are supported?

A: Supported countries and currencies depend on Gateway's acquiring configuration and the merchant's processing agreement. Google Pay itself supports payments in over 50 countries and a wide range of currencies. The actual list available to a specific merchant is determined during onboarding. Contact Gateway support to confirm the exact list applicable to your integration.

How are refunds handled?

A: Refunds are initiated by the merchant through Gateway's merchant portal or API. Gateway processes the refund back to the original Google Pay payment method — the amount is credited to the card linked to the shopper's Google Wallet. Processing time depends on the card network and issuing bank, typically 3–5 business days. Partial refunds are supported.

How are disputes handled?

A: Disputes (chargebacks) on Google Pay transactions follow the standard card dispute process. The merchant is notified through Gateway's merchant portal when a chargeback is received. The merchant must submit a response with supporting evidence within the timeframe required by the card network. Gateway's support team assists in managing dispute documentation.

Who processes the payment data?

A: The Gateway securely processes payment data according to its payment model and Google Pay requirements. The merchant does not access raw payment data.

What is the difference between test and production credentials?

A: Test credentials work in the TEST environment and do not process real payments. Production credentials use PRODUCTION and require Google approval before use. See Integration Guide and Testing and Go-Live.

Is Google approval required before going live?

A: Yes. Before enabling the PRODUCTION environment, the integration must be reviewed and approved by Google. The review is initiated by Gateway's partnerships team through the Google Pay & Wallet Console. It includes verification of branding compliance, integration correctness, and domain registration.

The merchant must complete all items before the request is submitted. See Google Review Pack.