Google Pay gives customers a way to pay using payment methods saved to their Google Account or Google Wallet without manually entering their card details each time.
For merchants, Google Pay can form part of:
- website checkout;
- mobile apps;
- payment links or hosted payment pages where supported;
- subscriptions and recurring-payment journeys in some configurations; and
- face-to-face contactless payments.
However, Google Pay is not a replacement for the merchant's payment gateway or acquiring arrangement.
The merchant still needs a payment provider capable of processing the payment credentials returned through Google Pay.
The practical question for a business is therefore not simply whether it can display a Google Pay button, but whether its gateway, processor, ecommerce platform and acquiring setup support the required Google Pay journey correctly.
What is Google Pay?
Google Pay is a payment service that allows customers to use supported payment methods saved to their Google Account or Google Wallet.
For online merchants, the Google Pay API can allow customers to select a saved payment method through a faster checkout journey rather than manually typing card details.
For face-to-face payments, customers can use supported Android devices to make contactless payments through Google Wallet wherever compatible contactless payments are accepted.
These are different merchant environments, even though both may be described as Google Pay.
Online
The merchant integrates Google Pay through its website, app, gateway or payment service provider.
Face to face
The customer can use a compatible Android device to make a contactless payment at an enabled terminal.
A business may support one or both of these payment journeys depending on its payment providers and technology.
How does Google Pay work for online merchants?
In a typical ecommerce Google Pay journey:
- The customer reaches the merchant's checkout.
- Google Pay is displayed as an available payment option.
- The customer selects a supported payment method saved to their Google Account.
- Google Pay returns encrypted payment information for processing.
- The merchant's gateway or payment processor handles the payment authorisation.
- The transaction then follows the merchant's normal acquiring and settlement process.
The Google Pay API therefore sits within the wider payment stack rather than replacing it.
Google's documentation describes payment-gateway tokenisation as the most common merchant implementation.
In that structure, the Google Pay integration is configured with the merchant's supported gateway and gateway merchant ID so the payment credential can be processed through the existing provider.
Google Pay does not replace your payment gateway
This is one of the most important points for merchants.
Google Pay can improve the way a customer supplies a payment credential at checkout, but the merchant still requires payment infrastructure behind it.
That can include:
- a payment gateway or PSP;
- merchant acquiring;
- fraud and risk controls;
- authorisation;
- settlement;
- refund functionality;
- reporting; and
- reconciliation.
For the wider setup, see our Payment Gateway guide .
Google Pay and payment tokenisation
Google Pay is often described as a digital wallet, but merchants should also understand the role of tokenisation.
Google's payment API can return either card information or tokenised card credentials depending on the customer, device, card and integration.
For supported device-token transactions, a tokenised payment credential can be used rather than exposing the customer's underlying physical card number through the checkout journey.
This forms part of the wider move toward network tokenisation across digital payments.
For a more detailed explanation, read our guide to network tokenisation .
Does Google Pay use debit and credit cards?
Often, yes.
A customer can use supported debit or credit cards through Google Pay where the relevant card issuer, network, device and merchant setup support the transaction.
This means Google Pay should not automatically be described as a non-card payment method.
From the customer's perspective, the checkout looks different because they select a saved payment method rather than entering card details manually.
But the underlying merchant payment can still use card-network and acquiring infrastructure.
This is why Google Pay sits within the broader category of alternative payment methods while still frequently relying on card processing underneath.
Need a payment gateway that supports Google Pay?
Tell us about your website, ecommerce platform, app, existing gateway and other payment methods you need to support.
Merchant Advice Service can help you understand the gateway requirement and identify providers that may support Google Pay alongside the rest of your payment setup.
Find suitable gateway providers
Does Google Pay support Strong Customer Authentication?
Google Pay transactions can interact with Strong Customer Authentication differently depending on the payment credential returned and how the merchant's payment provider handles the transaction.
Google's current documentation distinguishes between payment credentials including:
- PAN_ONLY card credentials; and
- CRYPTOGRAM_3DS device-token credentials.
Google states that tokenised card payloads can be processed without an additional step-up or challenge in supported circumstances.
Where a PAN-based credential is returned, the merchant or PSP may need to apply 3D Secure or other appropriate authentication in the same way it would for a conventional online card payment.
The exact implementation should therefore be confirmed with the payment gateway and acquirer.
For the wider UK authentication framework, see our guide to Strong Customer Authentication and 3D Secure .
Does Google Pay cost merchants more?
Google states that it does not charge merchants an additional fee simply for accepting Google Pay through the Google Pay API.
However, that does not mean the transaction is free.
The merchant's normal payment costs can still apply, including:
- merchant acquiring charges;
- interchange;
- card-scheme fees;
- gateway charges;
- PSP transaction fees;
- international card fees;
- currency-conversion costs where applicable;
- fraud-management charges; and
- other provider-specific fees.
The actual cost therefore depends on the merchant's wider gateway and acquiring arrangement rather than Google Pay alone.
For wider online-payment pricing, see our Payment Gateway Fees guide .
Does Google Pay improve checkout conversion?
Google Pay can reduce the amount of payment information some customers need to enter manually.
That can create a shorter checkout journey for customers who already use Google Pay.
However, merchants should avoid assuming that simply adding Google Pay will automatically improve conversion.
Actual performance depends on factors including:
- customer device;
- customer adoption of Google Pay;
- merchant sector;
- checkout design;
- mobile traffic;
- authentication;
- transaction approval rates;
- other payment methods offered; and
- how well the Google Pay journey is implemented.
Merchants should measure actual usage and conversion rather than relying solely on general claims about wallet performance.
Google Pay for ecommerce websites
Businesses can offer Google Pay through supported ecommerce gateways and payment service providers.
The integration route depends on the merchant's technology.
Possible routes can include:
- native ecommerce-platform support;
- a payment gateway plugin;
- a PSP-hosted checkout;
- a direct Google Pay API implementation; or
- a custom gateway integration.
Before choosing a provider, establish:
- whether Google Pay is supported;
- whether it requires separate activation;
- which card networks are supported;
- which countries are supported;
- how authentication is handled;
- how refunds work;
- how Google Pay appears in reporting;
- whether recurring payments are required; and
- whether the integration works with the merchant's ecommerce platform.
Google Pay for mobile apps
Google also provides APIs for merchants taking payments within mobile applications.
For app-based businesses, the payment decision should form part of the wider app architecture rather than being treated as a standalone button.
Consider:
- gateway compatibility;
- Android integration;
- customer authentication;
- tokenisation;
- stored credentials;
- subscriptions;
- refunds;
- app testing;
- reporting; and
- the merchant's wider payment stack.
Businesses operating across both web and apps should also decide whether the same PSP and acquiring arrangement should support both channels.
Can Google Pay be used for recurring payments?
Potentially, yes.
Google's current merchant guidance says recurring billing can be supported depending on the payment method returned through the Google Pay API and the merchant's payment gateway setup.
The recurring-payment relationship is then managed through the merchant's payment provider rather than by repeatedly calling Google Pay for every future charge.
Merchants still need to comply with:
- card-network stored-credential rules;
- merchant-initiated transaction requirements where relevant;
- customer consent;
- clear subscription terms;
- cancellation requirements; and
- the payment provider's recurring-payment setup.
Businesses should confirm recurring Google Pay support with the gateway before assuming a wallet integration automatically supports subscriptions.
How do refunds work with Google Pay?
Google Pay is not generally the system that manages the merchant's post-purchase money movement.
Google's documentation explains that once the initial transaction has taken place, refunds and other post-purchase operations are managed through the merchant's payment service provider.
That means merchants should check their gateway or PSP for:
- full refunds;
- partial refunds;
- refund timing;
- reporting;
- customer references;
- reconciliation; and
- any refund charges.
The operational process should ideally be tested before Google Pay is made available to customers.
Google Pay for face-to-face payments
Google Pay can also be used for contactless payments in physical locations.
Customers with supported Android devices can make payments through Google Wallet at compatible contactless terminals.
For merchants, this generally means that an existing contactless-enabled payment terminal may already be capable of accepting supported Google Pay transactions.
However, merchants should confirm support with their terminal and acquiring provider rather than assuming every device and configuration is identical.
Face-to-face Google Pay and online Google Pay should also be considered separately.
A merchant might be able to accept Google Pay at its physical terminal while its ecommerce gateway does not yet have Google Pay enabled, or vice versa.
Google Pay vs Google Wallet
The two names are closely related but describe different parts of the customer experience.
Google Wallet is the wallet application where customers can store supported payment cards and other digital items.
Google Pay refers to the payment experience merchants can accept online, in apps and in supported contactless environments.
For merchants, the practical focus should be whether the payment provider supports Google Pay rather than the historical branding of earlier Android payment products.
The old Android Pay name is no longer useful when specifying a new merchant integration.
Google Pay and PCI DSS
Using Google Pay does not mean merchants can ignore PCI DSS.
The merchant's PCI DSS position depends on the complete payment architecture and how payment data is handled.
A merchant using a supported PSP or gateway tokenisation integration can have a different payment-data environment from a business implementing direct tokenisation and receiving payment-card information itself.
Google specifically warns merchants using direct integrations that they must have the appropriate PCI DSS compliance and secure infrastructure for handling payment credentials.
Businesses should therefore confirm their PCI DSS requirements with their acquiring bank, payment provider or qualified PCI adviser rather than assuming Google Pay automatically removes PCI responsibilities.
Google Pay and fraud controls
Google Pay includes security features around payment credentials and authentication, but merchants should not treat the wallet as a replacement for their own payment-risk controls.
Google's merchant documentation specifically advises businesses to continue applying their existing risk checks and controls to Google Pay transactions.
Depending on the merchant, that can include:
- gateway fraud screening;
- transaction monitoring;
- velocity controls;
- 3D Secure where required;
- customer and device information;
- chargeback monitoring;
- refund controls; and
- business-specific fraud rules.
The objective should be to balance security with successful authorisation and customer experience.
Can every merchant accept Google Pay?
Not automatically.
Whether Google Pay is available can depend on:
- payment gateway;
- payment processor;
- acquirer;
- merchant location;
- customer location;
- supported card networks;
- ecommerce platform;
- technical integration;
- business sector; and
- the provider's merchant eligibility rules.
A payment gateway advertising Google Pay support does not necessarily mean every merchant can switch it on immediately.
The merchant should confirm the actual implementation route with the provider before making technical changes.
What should merchants compare when choosing a Google Pay gateway?
Google Pay support
Is Google Pay supported for the merchant's website, app or required payment journey?
Integration
Does the provider offer a native plugin, hosted checkout, API or another suitable integration?
Acquiring
Will Google Pay transactions run through the merchant's existing acquiring arrangement or require a different setup?
Authentication
How does the provider handle tokenised credentials, PAN-based transactions, 3D Secure and SCA?
Recurring payments
Can the required subscription or stored-credential model be supported?
Other payment methods
Does the same gateway also support Apple Pay, cards, Open Banking, BNPL or other methods the business needs?
Pricing
What gateway, acquiring and transaction charges apply?
Settlement
When are Google Pay transactions paid to the merchant?
Refunds
Can full and partial refunds be managed easily through the same reporting environment?
Reporting and reconciliation
Can Google Pay transactions be identified clearly alongside the merchant's other payment channels?
Google Pay should fit the wider payment setup
Adding Google Pay is usually only one part of the gateway decision.
Consider your ecommerce platform, acquiring arrangement, customer locations, recurring-payment requirements and any other wallets or alternative payment methods you need to support.
Find suitable gateway providers Explore payment gateway providers
How Merchant Advice Service helps with Google Pay
Merchant Advice Service does not operate Google Pay or determine which cards customers can add to Google Wallet.
Our role is to help businesses understand their payment and gateway requirements before identifying providers that may be suitable.
For Google Pay enquiries, that can include:
- existing payment gateway;
- merchant acquiring;
- ecommerce platform;
- website or app requirements;
- Google Pay support;
- Apple Pay and other wallets;
- other alternative payment methods;
- recurring payments;
- customer countries;
- currencies;
- processing volume;
- transaction values;
- settlement;
- refunds;
- reporting;
- reconciliation; and
- technical integration.
For the wider APM decision, see our Alternative Payment Methods guide .
Editorial & Commercial Disclosure
This guide provides general information about accepting Google Pay through payment gateways, apps and contactless payment environments.
Google Pay availability, supported cards, payment-provider integrations and technical functionality can vary by country, payment provider and merchant setup.
Google does not charge merchants an additional Google Pay API acceptance fee, but ordinary gateway, acquiring, card-processing and other provider charges may still apply.
Merchant Advice Service does not operate Google Pay, Google Wallet, payment gateways or card-acquiring services.
MAS is an independent payments information and provider-matching service. MAS may receive a referral fee or commission from some payment providers where a business proceeds following an introduction. Commercial relationships do not determine the factual information or provider-selection principles contained within this guide.
Merchants should confirm current Google Pay functionality, authentication, PCI DSS requirements, pricing and contractual terms with their payment gateway and acquiring provider.
Information is provided for general guidance and should not be treated as legal, regulatory or information-security advice.
