Do Apple Pay and Google Pay protect you from chargebacks?

Apple Pay and Google Pay protect you from chargebacks only in part. A wallet payment can shift liability for a fraud dispute to the card issuer in some cases, Stripe says the shift is never assured, and it does nothing for claims that goods never arrived or were not as described.

Does a wallet payment shift fraud liability?

It can, in some cases. Stripe states that the liability shift applies in some cases with equivalent cryptograms, such as those used by Apple Pay and Google Pay.

A liability shift means the issuer, not you, carries the loss on a fraud dispute. It usually comes from 3D Secure (3DS), the extra check where the bank authenticates the cardholder at checkout. Stripe says a successful 3DS authentication typically shifts liability for fraud disputes to the issuer, but that the shift is never assured.

Stripe also notes that wallets and off-session payments may not support 3DS at all. The cited Stripe page does not list which wallet transactions qualify. Look at the authentication result on each disputed wallet payment, because the wallet label alone does not settle it.

Which disputes does the shift not cover?

The shift leaves out every dispute that is not fraud. Stripe says the shift covers fraud disputes only, and a "product not received" claim follows the standard dispute process.

The same goes for claims that goods were not as described or that a subscription was cancelled. A customer who paid with a wallet and says the parcel never came has the same case as one who typed a card into a form. The evidence that wins it is the same too.

A merchant with a fraud-shifted wallet payment and an undelivered parcel still needs the delivery record. Keep tracking for every wallet order exactly as you would for a card order.

How can you lose the shift?

You can forfeit it by ignoring an inquiry. Stripe says an inquiry on a 3DS-authenticated charge must be answered, or a default chargeback can follow and void the liability shift.

Stripe lists further exceptions:

• merchants in a fraud monitoring program;
• industries Visa excludes: wire transfer and money orders, non-fiat currency and stored value.

Monitoring programs matter most for merchants with high fraud exposure. Stripe describes the Visa Secure Excessive Fraud Program in the US, triggered by 3DS fraud volume of $75,000 and a rate of 0.9%. There is no fine, but a merchant in the program loses the liability shift on domestic 3DS until it exits, so check your 3DS fraud volume against that line each month.

What evidence works when the shift fails?

Account history from the same customer is the evidence Visa's rules name. For a Visa 10.4 dispute (10.4 is Visa's reason code for card-absent fraud), the Core Rules in the edition dated 18 April 2026 list compelling evidence from earlier, undisputed transactions.

That evidence includes 3 or more matching data elements from an undisputed transaction, drawn from:

• login ID;
• delivery address;
• device ID;
• email;
• IP address;
• phone.

The rules also allow evidence of 2 prior undisputed transactions processed more than 120 days, and not more than 365 days, before the dispute. A wallet customer who has bought before from the same account and delivery address is a good candidate. The Visa 10.4 reason code page lists the elements in full.

Takeaway: what to do this week

1. Pull the authentication data. For every disputed wallet payment, check the authentication result and cryptogram data before assuming the shift applies.
2. Answer every inquiry on an authenticated charge. An unanswered inquiry can become a default chargeback that voids the shift.
3. Watch the Visa Secure line. If you sell domestically through 3DS, track fraud volume against $75,000 and 0.9%.
4. Keep account history for repeat buyers. Login IDs, devices, emails, IP addresses and delivery addresses are what a 10.4 response relies on, so build every dispute file as if the wallet were not there.

Sources: Stripe Docs, "3D Secure authentication flow"; Stripe Docs, "Dispute and fraud card monitoring programs"; Visa Core Rules, edition 18 April 2026, Tables 11-6 and 11-28. All checked 24 October 2026.