Post payment activities can include disputes and refunds. When these use cases happen, learn how to address disputed payments, understand the nuances of liability shifts for Google Pay charges, and manage refunds effectively.
Users must authenticate payments with their Google Pay accounts, helping to reduce 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 for all the major networks except Visa. For Visa, Google Pay supports liability shift only in Europe.
There are three use cases of Google Pay transactions:
- 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.
- If the user adds a card to Chrome or a Google property (for example, YouTube or Play), this card is saved as a Funding Primary Account Number (FPAN). Liability shift is supported for all major networks, including Visa, globally when 3D Secure is performed. You can customize Stripe Radar rules to request activation of 3D Secure.
- 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
fpan. DPAN and ecommerce token transactions set the
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.