Google Pay Liability Shift for Non-EU Visa Cards

Google Pay Liability Shift Update — Now Available for Non-EU Visa Cards

A hand holding a smartphone displaying a Visa card screen, with icons for Google Pay and a document labeled

In a nutshell: Starting February 2024, cards issued outside the European Union are eligible for a liability shift for Google Pay Visa device token (DPAN) transactions. Merchants outside of Europe can opt to activate the liability shift feature for their eligible Visa DPAN transactions, transferring the responsibility of covering losses from fraudulent transactions to card issuers. For Mastercard DPAN transactions and Visa DPAN transactions involving EU-based card issuers, the liability shift is automatically applied.

Read on for more details and instructions on enabling the liability shift feature for your Visa Google Pay transactions.

How to activate liability shift for Google Pay non-EU cards

For merchants integrated through the Payment Form or H2H:

  1. Sign in to your Google Pay & Wallet Console.
  2. Go to the Google Pay API tab.
  3. Go to the Settings tab.
  4. Enable Fraud liability protection for Visa device tokens.

liability-shift-opt-in-flow (video)

For merchants integrated through the Payment Page: No action is required on your part; the Solidgate team will handle the activation for you.

Important: If you’re directly integrated with GooglePay, ensure that you pass a correct total price for Android and Web. Transactions where totalPrice for Android and Web is unspecified or set to $0 can’t be processed through Google Pay API. Providing an accurate price will also prevent any confusion for your customers, as they might be able to see the total amount in the payment window.

Transactions that don’t qualify for a liability shift

In the US, Visa excludes certain transactions from getting liability shift:

A table listing types of transactions that don't qualify for a liability shift, categorized under different institutions such as money transfer, non-direct institutions, and government-licensed.

How this change affects customer payment flow 

The user payment flow remains unchanged for transactions within the European Economic Area (EEA), where Strong Customer Authentication (SCA) is enforced automatically. However, enabling liability shift for transactions outside of the EEA requires users to complete an additional authentication step during checkout, which might slightly impact the checkout experience.

According to Solidgate’s data, we have observed a minor adjustment in our merchants’ payment flow:

The median time for non-EEA users to complete the payment process (from clicking the Google Pay button to confirming the payment) increased by 2-3 seconds.

Overall, activating this feature has not adversely affected the payment flow for our merchants and their customers.


What is a liability shift?

The liability shift is the transfer of liability that happens when the party with the less secure technology becomes responsible for covering losses resulting from fraudulent chargebacks. This change occurs by implementing an extra layer of security, like the EMV chip for in-person transactions or 3D security protocols for online transactions.

What are the benefits of a liability shift for merchants?

Reduced chargeback costs: The responsibility for any fraudulent transactions falls on the card issuer, which alleviates the financial burden on the merchants. Learn more about Visa/Mastercard chargeback monitoring programs.

Improved customer trust: Customers are likelier to trust services that protect their financial information. 

Higher payment acceptance rates: Transactions authenticated through 3D Secure are less likely to be fraudulent, which increases the chances of the transaction being approved by issuers. 

As a merchant, how can I tell where liability shift is applied?

If you use gateway integration like Solidgate, you don’t have visibility into the liability shift status. In this case, you can request a liability shift report from your payment service provider. Merchants with direct integration easily access this information by looking at the three_ds.eci field, which should be equal to 05 for Visa device tokens. 

Share article

Start accepting payments today

Let’s discuss your business needs and we'll give you better fees and conversion rates than you have with your current payment provider.

    By clicking "Get in touch" you agree to our Privacy Policy

    Thank you

    Thank you

    We will contact you shortly. If you have any further questions, please contact us at