Google Pay supports liability shift 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.
2. 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 is performed. You can customise Stripe Radar rules to request the 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.