Is Google Pay a PSP or an acquirer?

No. Google Pay is a digital wallet and payment method; processing, settlement, and reporting are handled by your PSP/gateway and acquirer.

What affects Google Pay approval rates and card declines?

Approvals are determined by the card issuer and influenced by your acquirer routing, transaction data quality, and risk settings. Compare decline codes and approval rates against regular card transactions to isolate differences.

Where can merchants accept Google Pay?

Typically online and in-app, subject to your PSP’s support and customer eligibility (device, browser, and region). Availability can vary by market and platform.

Does Google Pay reduce fraud or chargebacks?

It can improve security by using tokenized credentials and device-based authentication, but disputes still follow card network rules and outcomes depend on your overall risk controls.

How do refunds and disputes work with Google Pay transactions?

Refunds are initiated by the merchant through the same PSP/acquirer flow as card payments. Chargebacks and representment are managed through your PSP/acquirer under card scheme timelines.

Google Pay

Cards

Google Pay is a digital wallet payment option that enables customers to pay online or in-app using credentials stored in their Google wallet

Struggling with your approval ratio for this payment provider?

contact SmartRetry team →

Published: January 21, 2026
Last updated: May 5, 2026

2 min

Proceed payment with

About Google Pay

Product Type

Payment Method

Foundation

2018

Stock ID

NASDAQ:GOOGL

Company Type

public

Employees

150,000+

Location

USA

Channel

OnlineIn person

For developers

Status page Stack Overflow

Features

Global wallet acceptance (via PSP support)

Offer Google Pay where your payment provider supports it, for online and in-app checkout. Customer availability varies by device and browser.

Tokenized payment credentials

Uses tokenization to reduce exposure of raw card data in merchant environments. Helpful for security and compliance posture when supported by your stack.

Authorization success and decline visibility

Approval rates depend on the underlying card issuer decision and your acquirer routing. Track Google Pay vs. card form entry to spot issuer or data-quality decline patterns.

Strong customer authentication support

Can support user authentication on supported devices, which may help reduce friction where SCA is required. Exact experience depends on the card and region.

Disputes handled through card rails

Chargebacks and disputes generally follow the underlying card network rules and timelines. Manage evidence and representment through your PSP/acquirer tools.

Checkout reliability and fallbacks

When Google Pay isn’t available for a customer, you can offer standard card entry as a fallback. Monitor wallet button errors and conversion drop-offs by device/browser.

Data and reporting alignment

Transaction reporting typically appears as card payments with a wallet indicator in PSP dashboards. Ensure your analytics captures wallet usage for funnel and risk tuning.

Tip from SmartRetry If you’re seeing higher Google Pay declines than card entry, compare issuer response codes and AVS/CVC expectations with your PSP—wallet token flows can differ from manual entry and may need specific settings or routing.

Currencies

Processing currenciesUSD, EUR, GBP, JPY, AUD, CAD, CHF, SGD, HKD, SEK

Available in

Available countries

Global

FAQ

Statuses

Statuses - All
Code	Description	Level	Frequency	Resolution
Transaction State
SUCCESS	Success The payment was successfully authorized by the merchant's backend. Return this transactionState in PaymentAuthorizationResult to close the Google Pay sheet with a success confirmation.	Approved	Common	T0
ERROR	Error The payment authorization failed. Return this transactionState in PaymentAuthorizationResult alongside a PaymentDataError object specifying the reason and user-facing message. The sheet remains open for correction.	Error, Declined	Common	T2
Payment Data Error Reason
OFFER_INVALID	Offer / Promo Code Invalid The promotional or offer redemption code entered on the Google Pay sheet is invalid, expired, or cannot be applied. The sheet stays open for the user to enter a valid code or proceed without one.	Error	Occasional	T0
PAYMENT_DATA_INVALID	Payment Data Invalid The payment token, card, or payment credentials returned by Google Pay are invalid and cannot be used to process the transaction. Prompt the user to select a different payment method or retry.	Error, Declined	Occasional	T0
SHIPPING_ADDRESS_INVALID	Shipping Address Invalid The shipping address selected by the customer is invalid (e.g., missing required fields, incorrect postal code format). The payment sheet remains open for the user to correct the address.	Error	Occasional	T0
SHIPPING_ADDRESS_UNSERVICEABLE	Shipping Address Unserviceable The shipping address is valid but cannot be serviced by the merchant (e.g., delivery not available to selected country or region). The payment sheet prompts the user to pick a different address.	Error	Occasional	T0
SHIPPING_OPTION_INVALID	Shipping Option Invalid The selected shipping option is invalid for the given address (e.g., the option is no longer available or does not apply to the selected region). The sheet prompts the user to select a valid option.	Error	Occasional	T0
OTHER_ERROR	Other Error A general or unclassified error occurred during payment processing. Use when no specific PaymentDataError reason applies. Provide a descriptive message to guide the user.	Error	Occasional	T0
Payments Error Status Code
CANCELED	Canceled The user dismissed the Google Pay sheet without authorizing, the browser/Google account is unsupported, the sheet was already open, or the PaymentDataRequest config was rejected. The loadPaymentData promise is rejected; no charge was made.	Info	Common	T0
DEVELOPER_ERROR	Developer / Configuration Error A passed parameter is improperly formatted or the API request is malformed (e.g., typo in a field name, invalid enum value, missing required property). Check the browser console for details. Fix the integration before retrying.	Error	Common	T1
MERCHANT_ACCOUNT_ERROR	Merchant Account Error The site accessing the Google Pay API does not have the required permissions. Common causes: the merchant has not been approved for production use, incorrect merchantId, or the domain is not registered in the Google Pay & Wallet Console.	Error	Occasional	T1
INTERNAL_ERROR	Internal Server Error A general server-side error occurred on Google's payment infrastructure. Retry after a short delay. If the issue persists, contact Google Pay support.	Error	Occasional	T0
BUYER_ACCOUNT_ERROR	Buyer Account Error The current Google user is unable to provide payment information. This may occur due to account suspension, missing payment methods, or the user being in an unsupported region. Offer an alternative payment method.	Error, Declined	Occasional	T2