Learn more about accepting payments with Google Pay.

Google Pay allows customers to make payments in your app or website using any credit or debit card saved to their Google Account, including those from Google Play, YouTube, Chrome, or an Android device. Use the Google Pay API to request any credit or debit card stored in your customer’s Google account.

Google Pay is fully compatible with Stripe products and features (e.g. recurring payments), so you can use it in place of a traditional payment method whenever possible. Use it to accept payments for tangible goods, donations, subscriptions, and more.

Payment Method Properties

• Customer Locations: Worldwide, except India

• Payment Currency: See accepted payment currencies

• Payment Confirmation: Initiated by the customer

• Payment Method Family: Wallet

• Recurring Payments: Yes

• Payout Timing: Standard payout timing applies

• Connect Support: Yes

  • Dispute Support: Yes

  • Manual Capture Compatibility: Yes

  • Refunds / Partial Refunds: Yes / Yes

Company Locations

Stripe accounts worldwide, except India, can accept Google Pay payments in local currency

Disputes

Users must authenticate payments with their Google Pay accounts, which reduces the risk of fraud or unrecognized payments. However, users can still dispute transactions after completing the payment. You can submit evidence to respond to a dispute directly. The dispute process is the same as for card payments. Learn more about how to manage disputes.

Liability Shift for Google Pay Charges

Google Pay supports liability shift worldwide. This is automatically applied to users of hosted Stripe products and those using Stripe.js.

For Visa transactions outside of a hosted Stripe product, you must enable liability shift in the Google Pay & Wallet Console. To do this:

• Go to Google Pay & Wallet Console.

• Select Google Pay API in the left navigation bar.

• Enable Liability Shift Protection for Visa device tokens to activate liability shift protection.

Three Use Cases for Google Pay Transactions:

• If a user adds a card to the Google Pay app on their mobile device, the card is stored as a Device Primary Account Number (DPAN) and supports liability shift by default.

• If a user adds a card to Chrome or a Google property (e.g., YouTube or Play), it is stored as a Funding Primary Account Number (FPAN). When you use 3D Secure, liability shift is supported globally for all major networks, including Visa. You can customize Stripe Radar rules to require 3D Secure activation.

• If a user selects Google Pay as a payment method on an e-commerce site or an app that uses Google Pay, the cards are stored as e-commerce tokens representing the registered cards. Currently, e-commerce tokens do not support liability shift or 3D Secure authentication.

For Sigma users, the charges table contains a card_token_type field that indicates the Google Pay transaction type:

• A transaction using the FPAN sets card_token_type to fpan.

• Transactions using DPAN or an e-commerce token set card_token_type to dpan_or_ecommerce_token.

Refunds

You can partially or fully refund any successful payment made with Google Pay. The refund process is the same as for card payments. Check the Refund and Cancel Payments guide for instructions on how to initiate or manage refunds.