# Google Pay Learn how to accept payments using Google Pay. For information on payment method transaction fees, refer to [pricing details](https://stripe.com/pricing/local-payment-methods). 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’s products and features (for example, recurring payments), allowing you to use it in place of a traditional payment form whenever possible. Use it to accept payments for physical goods, donations, *subscriptions* (A Subscription represents the product details associated with the plan that your customer subscribes to. Allows you to charge the customer on a recurring basis), and so on. > #### Google Pay terms > > By integrating Google Pay, you agree to Google’s [terms of service](https://payments.developers.google.com/terms/sellertos). #### Payment method properties - **Customer locations** Worldwide except India - **Presentment currency** See [supported presentment currencies](https://docs.stripe.com/currencies.md#presentment-currencies) - **Payment confirmation** Customer-initiated - **Payment method family** Wallet - **Recurring payments** Yes - **Payout timing** Standard payout timing applies - **Connect support** Yes - **Dispute support** [Yes](https://docs.stripe.com/google-pay.md#disputed-payments) - **Manual capture support** Yes - **Refunds / Partial refunds** [Yes / Yes](https://docs.stripe.com/google-pay.md#refunds) #### Business locations Stripe accounts worldwide except India can accept Google Pay payments with local currency settlement. #### Product support - Connect - Checkout - Payment Links - Elements - Subscriptions - Invoicing ## Using Stripe and Google Pay versus the Google Play billing system This guide explains how to configure your app to accept Google Pay for physical goods, services, and other eligible items. Stripe processes these payments, and you pay only Stripe’s [processing fees](https://stripe.com/pricing). For digital products, content, and subscriptions sold in the US or the European Economic Area (EEA), your Android app can accept payments directly in-app through a third-party payment processor such as Stripe. You can use these payment UIs: - [Mobile Payment Element](https://docs.stripe.com/payments/mobile.md) to accept payments directly in-app - [Stripe Checkout](https://docs.stripe.com/mobile/digital-goods/checkout.md) to redirect customers to a Stripe-hosted payment page - [Payment Links](https://docs.stripe.com/mobile/digital-goods/payment-links.md) for a limited number of products and prices For more information about which purchases must use the Google Play billing system, see Google Play’s [developer terms](https://support.google.com/googleplay/android-developer/answer/10281818). # Web ## Accept Google Pay on the web You can accept Google Pay payments on the web using [Checkout](https://docs.stripe.com/payments/checkout.md) or [Elements](https://docs.stripe.com/payments/elements.md) by enabling Google Pay in your [payment methods settings](https://dashboard.stripe.com/settings/payment_methods). Using Google Pay in Checkout requires no additional code implementation. For Elements, refer to the [Express Checkout Element](https://docs.stripe.com/elements/express-checkout-element.md) or [Accept a payment](https://docs.stripe.com/payments/accept-a-payment.md?payment-ui=elements&api-integration=checkout) guides to learn how to add Google Pay to your site. You need to serve from an HTTPS webpage with a TLS domain-validated certificate to accept Google Pay payments on the web. ### Register your domain with Google Pay To use Google Pay, you must register all of your web domains that show a Google Pay button. That includes top-level domains (for example, **stripe.com**) and subdomains (for example, **shop.stripe.com**), in production and testing. > #### Subdomains > > `www` is a subdomain (for example, **www.stripe.com**) that you must also register. Register your domain on the [Payment methods domains page](https://dashboard.stripe.com/settings/payment_method_domains) in the Dashboard or use the API with your live secret key, as shown in the following example. Register your domain only once per account. ```curl curl https://api.stripe.com/v1/payment_method_domains \ -u "<>:" \ -d "domain_name=example.com" ``` When using [Direct charges](https://docs.stripe.com/connect/direct-charges.md) with *connect* (Connect is Stripe's solution for multi-party businesses, such as marketplace or software platforms, to route payments between sellers, customers, and other recipients), you need to configure the domain for each connected account using the API. This isn’t a requirement for connected accounts using other charge types. After registering your domains, you can make payments on your site with your live API keys. ## Test Google Pay Google allows you to make test payments through their [Test card suite](https://developers.google.com/pay/api/android/guides/resources/test-card-suite). You can use Stripe [test cards](https://docs.stripe.com/testing.md) with the test suite. Before you can use a Stripe test card, you must add a real card to your wallet to make Google Pay display. If you don’t meet device and integration requirements, Stripe doesn’t render Google Pay as a payment option. To troubleshoot rendering issues with Google Pay, use our [test page](https://docs.stripe.com/testing/wallets.md). ## Disputes Users must authenticate payments with their Google Pay accounts, which reduces the risk of fraud or unrecognised payments. However, users can still dispute transactions after they complete payment. You can submit evidence to contest a dispute directly. The dispute process is the same as that for card payments. Learn how to [manage disputes](https://docs.stripe.com/disputes/responding.md). ### Liability shift for Google Pay charges Google Pay supports [liability shift](https://docs.stripe.com/payments/3d-secure/authentication-flow.md#disputed-payments) globally. This is true automatically for users on Stripe-hosted products and using Stripe.js. For Visa transactions outside of a Stripe-hosted product, you must enable liability shift in the Google Pay & Wallet Console. To do so, go to your ***Google Pay & Wallet Console***, select ***Google Pay API*** in the navigation bar on the left and then enable ***Fraud Liability Protection for Visa Device Tokens*** for liability shift protection. There are three use cases of Google Pay transactions: 1. If the user adds a card to the Google Pay app using their mobile device, this card is saved as a Device Primary Account Number (DPAN), and it supports liability shift by default. 1. If the user adds a card to Chrome or a Google property (for example, YouTube, or Play), it’s saved as a Funding Primary Account Number (FPAN). When you use [3-D Secure](https://docs.stripe.com/payments/3d-secure.md), we globally support liability shift for all major networks, including Visa. You can customise [Stripe Radar rules](https://docs.stripe.com/radar/rules.md#request-3d-secure) to request activation of 3-D Secure. 1. If the user selects Google Pay as the payment method on an e-commerce site or in an app that pays with Google Pay, the cards are saved as e-commerce tokens that represent the cards on file. Neither liability shift nor 3D Secure are supported for e-commerce tokens at this time. For Sigma users, the `charges` table contains a `card_token_type` field that indicates the Google Pay transaction type. An FPAN transaction sets the `card_token_type` to `fpan`. DPAN and e-commerce token transactions set the `card_token_type` to `dpan_or_ecommerce_token`. ## Refunds You can partially or fully refund any successful Google Pay payment. The refund process is the same as that for card payments. See [Refund and cancel payments](https://docs.stripe.com/refunds.md) for instructions on initiating or managing refunds.