# Liability shift for Google Pay charges

Google Pay supports [liability shift](/questions/liability-shift-with-frictionless-flow-for-3d-secure-v2-3ds2) for all the major networks.
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 has added a card to Chrome or one of Google’s 1P properties (YouTube, Play etc), these cards are saved as Funding Primary Account Number (FPAN): Liability shift is supported for all the major networks when [3D Secure](https://stripe.com/docs/payments/3d-secure) is performed. You can customize [Stripe Radar rules](https://stripe.com/docs/payments/3d-secure#custom-rules-for-3d-secure-and-liability-shift) to request the activation of 3D 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.