Accéder directement au contenu
Créez un compte
 ou
connectez-vous
Le logo de la documentation Stripe
/
Créer un compte
Connectez-vous
AperçuMettre votre intégration à niveau
Paiements en ligne
AperçuTrouver votre cas d'usageManaged Payments
Moyens de paiement
Interfaces de paiement
Scénarios de paiement
Paiements en personne
Au-delà des paiements

Google Pay

Learn how to accept payments using 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’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, and so on.

Google Pay terms

By integrating Google Pay, you agree to Google’s terms of service.

  • Customer locations

    Worldwide except India

  • Presentment currency

    See supported 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

  • Manual capture support

    Yes

  • Refunds / Partial refunds

    Yes / Yes

Using Stripe and Google Pay versus the Google Play billing system

For sales of physical goods and services, your app can accept Google Pay or any other Stripe-supported payment method. Those payments are processed through Stripe, and you only need to pay Stripe’s processing fees. However, in-app purchases of digital products and content must use the Google Play billing system. Those payments are processed by Google and are subject to their transaction fees.

For more information about which purchases must use the Google Play billing system, see Google Play’s developer terms.

Accept Google Pay on the web

You can accept Google Pay payments on the web using Checkout or Elements by enabling Google Pay in your payment methods settings. Using Google Pay in Checkout requires no additional code implementation. For Elements, refer to the Express Checkout Element or Accept a payment 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.

Command Line
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node
Go
.NET
No results
curl https://api.stripe.com/v1/payment_method_domains \
  -u "
sk_test_BQokikJOvBiI2HlWgH4olfQ2
:" \
  -d domain_name="example.com"

When using direct charges with Connect, 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. The test suite supports using stripe test cards.

If you aren’t meeting device and integration requirements, Stripe doesn’t render Google Pay as a payment option. Use our test page to help you troubleshoot.

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 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.

Liability shift for Google Pay charges

Google Pay supports liability shift 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.
  2. 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 3D Secure, we globally support liability shift for all major networks, including Visa. You can customize Stripe Radar rules to request activation of 3D Secure.
  3. 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 ecommerce 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 for instructions on initiating or managing refunds.

Cette page vous a-t-elle été utile?
OuiNon