Consumer Payment Preferences: What Each Payment Method Changes About Dispute Risk

Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
TL;DR:
- Quick answer: Each payment method carries its own chargeback liability model: cards can shift fraud liability to the issuer under chip and 3D Secure 2 authentication, while BNPL, bank transfers, and crypto carry little or no built-in liability shift.
- BNPL usage keeps climbing, with roughly 96 million U.S. users expected in 2026, and a forgotten installment is now one of the most common merchant-side disputes.
- A digital wallet transaction still follows the underlying card rules, so it counts toward the same Visa and Mastercard chargeback ratio thresholds as any other card volume.
- Crypto payments have no chargeback mechanism on-chain; liability only surfaces at the card used to fund the fiat on-ramp.
- Matching prevention, deflection, or evidence to the payment method used, instead of running one generic dispute process, is what keeps chargeback ratios under control as payment mix diversifies.
Consumer payment preference decides dispute exposure as much as fraud rate does: a card, a digital wallet, a Buy Now Pay Later (BNPL) plan, a bank transfer, and a crypto payment each carry a different liability model, a different evidence trail, and a different route to resolution once a customer disputes a charge.
Not long ago the checkout question was simple: cash or credit? That single choice decided who covered a bad transaction and how a dispute got resolved. Now a shopper can pay with a card, an e-wallet, a peer-to-peer transfer, or a BNPL plan, and each option resets who owns the risk.
Consumers have moved decisively toward digital payment options: Nine out of ten consumers said they used some form of digital payment in a recent survey year, and demand for more choice keeps rising as alternative payment methods (APMs) have skyrocketed in popularity, with transaction values estimated to grow by compound annual rates above 11 percent.
That demand is exactly why payment preference now belongs in the same conversation as prevention, deflection, evidence, liability, and recovery. Offering more ways to pay grows revenue, but each new method also comes with its own chargeback process, its own evidence format, and its own filing deadline for the merchant to track.
What Changes When a Customer Picks a Different Way to Pay
Every alternative to a plain card swipe changes three things at once: who your customer disputes to, what evidence exists to fight it, and who eats the loss by default.
- Cryptocurrency: Merchants can accept crypto such as Bitcoin, Ethereum, Bonk, and other tokens, settled over a public ledger that transfers value directly between parties without a card network in the middle. Many tokens move faster and at a lower cost than a card rail, and consumers cite the privacy, security and innovative possibilities of paying this way. Adoption is still small (0.2% of global eCommerce value), with the market forecast to expand at a CAGR of 17% till 2030. But a confirmed crypto transfer has no chargeback mechanism at all: the liability question only ever surfaces one step earlier, at the card used to fund the fiat on-ramp.
- Buy Now, Pay Later (BNPL): A BNPL provider splits a purchase into installments at checkout instead of billing the full amount up front. Surveyed users report they find BNPL more convenient than other payment methods. Some 85% of respondents said Buy Now Pay Later made it easier to make ends meet. Easy access to low-interest or interest-free loans is also a key selling point. That demand has already given BNPL a 5% market share in the United States, with transaction value estimated to reach 565 Billion by 2026 after the 400% growth spurt between 2019 and 2021. More recent tracking puts U.S. BNPL usage at roughly 96 million people heading into 2026; see Chargeflow's own current BNPL market data for the full breakdown. Because a BNPL plan spreads payment across weeks or months, the most common merchant-side dispute is a forgotten installment: by the time it is filed, the transaction has long since aged out of the merchant's own checkout logs.
- Digital and Mobile Wallets: A wallet like Apple Pay or Google Pay tokenizes the underlying card, so the merchant never touches the primary account number. Adoption reflects that convenience: over half (53%) of surveyed Americans said they would use a digital wallet over a traditional payment method, and wallet volume is projected to grow at a CAGR of 15% between 2023 and 2027, making it the fastest-growing global payment option tracked. A wallet transaction is still a card transaction underneath, though: your payment service provider settles it against the same card rules regardless of which wallet initiated it, and it counts toward the same chargeback threshold limits, including the Visa Acquirer Monitoring Program ratio, that any other card volume does.
Why More Payment Choice Means More Dispute Complexity
Accepting more payment types is good for conversion and bad for uniformity: each method routes disputes back to the merchant through a different door, on a different timeline, with a different chargeback time limit attached.
With crypto, the irreversible ledger is the whole problem. A fraudster can buy tokens with a stolen credit card, and the token itself is unrecoverable while the cardholder can still dispute the original card charge. That mismatch shifts liability onto the merchant even though the merchant never touched the card fraud directly.
With BNPL, the open question is who is liable when a customer disputes an installment: the BNPL provider or the merchant. The answer depends entirely on the provider's own merchant agreement, not on a card network rule, which is exactly why a BNPL dispute often needs a different playbook than a card chargeback.
With mobile wallets, a stolen or unlocked phone can authorize a payment the actual cardholder never approved. Because contactless wallet payments do not always carry the same authentication data as a chip-and-PIN transaction, an account takeover through a wallet can look, from the issuer's side, identical to ordinary card-not-present fraud. Broader ecommerce fraud prevention controls still have to cover all of it at once.
The table below lines up each method on the same four questions, so the comparison stays apples to apples: what the default liability rule is, how likely the customer is to recognize the charge, what evidence is actually available, and where the dispute gets filed.
| Payment Method | Default Fraud Liability | Customer-Recognition Risk | Evidence You Can Produce | Typical Dispute Route |
|---|---|---|---|---|
| Cards (credit and debit) | Shifts to the issuer only when chip and 3D Secure 2 authentication both complete; unauthenticated card-not-present fraud stays with the merchant | Low: the merchant name on the statement is usually clear | AVS and CVV match, device and IP data, authentication result, delivery confirmation | Card network chargeback process with a network-set response deadline |
| Digital wallets | Follows the underlying card's rules; tokenization does not create a separate liability shift | Medium: wallet display names can differ from the card statement name | Device biometric or token authentication log plus the underlying card's AVS/CVV data | Same card network chargeback process as the underlying card brand |
| Buy Now, Pay Later | Set by the BNPL provider's own merchant agreement, not a card network rule | High, especially by the third or fourth installment | Installment schedule, delivery or fulfillment proof, provider dispute-portal records | Provider's own dispute process first; card network chargeback only if the plan was card-funded |
| Bank transfer, ACH, open banking | No card network chargeback right exists; a dispute here is a bank recall, not a chargeback | Low once authenticated, but authorized-push-payment fraud is a real gap | Payment authorization record, delivery confirmation, correspondence | Bank-initiated recall or reversal request, slower and less standardized than card disputes |
| Cryptocurrency | No mechanism on-chain; liability only surfaces at the fiat on-ramp card transaction | Low for the crypto leg, higher for the card-funding leg | Wallet address, transaction hash, on-chain confirmation | None for the transfer itself; a card dispute can still hit the funding transaction |
Note what this table deliberately does not do: it never places a liability percentage from one network next to a market-share percentage from another, or a 2023 survey figure next to a 2026 one, as if they measured the same thing. Each row uses the same four qualitative categories, so the comparison holds up method to method.
Turning Payment Complexity Into a Recovery Advantage
None of this means you should limit the ways customers can pay. Merchants who don't adapt risk losing share to competitors who accept more of what customers want. It means matching your response to the payment method instead of running one generic process for every dispute, whatever what is a chargeback looks like for that particular rail.
For crypto, the highest-leverage move is identity verification at the fiat on-ramp: confirming who is buying tokens with a card limits the fraud that eventually surfaces as a card chargeback (we even have crypto-based chargeback experts to support you).
For BNPL and wallets, prevention still comes first: securing the transaction infrastructure, watching for account takeovers, and flagging suspicious velocity before a dispute is even filed. Chargeflow can automate your dispute response across every one of these rails from a single system, so the evidence format and filing deadline change automatically with the payment method, not the workflow.
How to Match Your Response to Each Payment Method
- If it's a card or wallet dispute, lead with prevention: chargeback prevention alerts and active ratio monitoring keep you under the network's threshold before a dispute is even filed.
- If it's a BNPL dispute, lead with deflection: resolve it inside the provider's own portal before it can escalate into a card network chargeback.
- If it's a bank transfer or crypto dispute, lead with evidence: there is no automatic liability shift on these rails, so a clean authorization and delivery record is your only real defense.
- If the pattern looks like friendly fraud rather than criminal fraud (a forgotten BNPL installment, a wallet charge the cardholder simply doesn't recognize), automate the response so the fix scales with order volume instead of headcount.
Payment Preference Is a Liability Decision, Not Just a Checkout Feature
Every new payment method you add is really a new liability agreement you're accepting on your customers' behalf. Cards shift some fraud liability to the issuer under the right conditions. Wallets inherit whatever the underlying card does. BNPL liability is contractual, not network-based. Bank transfers and crypto carry almost no built-in liability shift at all. Treating all of it as one dispute pipeline is what turns manageable payment growth into unmanaged chargeback growth.
Frequently Asked Questions
Which payment method carries the least chargeback risk for merchants?
Cards authenticated with chip-and-PIN or 3D Secure 2 carry the most built-in protection, because a completed authentication shifts most fraud liability to the card issuer. BNPL, bank transfers, and crypto carry comparatively less structural protection because none of them run through a card network's dispute rules by default.
Do digital wallets like Apple Pay reduce chargebacks?
Wallets reduce certain types of card-data theft because the merchant never sees the primary account number, but they do not change chargeback liability. A wallet transaction is settled under the same card brand rules as the underlying card, and it counts toward the same chargeback ratio thresholds.
Who is liable when a BNPL installment gets disputed?
It depends on the BNPL provider's own merchant agreement rather than a card network rule. Some providers absorb fraud losses on approved plans; others pass the dispute back to the merchant. Merchants should confirm this in their BNPL contract before treating an installment dispute like a standard card chargeback.
Can a merchant get a chargeback on a crypto payment?
Not on the crypto transfer itself. Blockchain transactions are irreversible and have no card-network dispute mechanism. Disputes only arise on the separate credit card transaction a buyer may have used to purchase the crypto in the first place.
Does 3D Secure 2 protect against every type of dispute?
No. A successful 3D Secure 2 authentication shifts liability for fraud disputes to the issuer, but it does nothing for non-fraud disputes like product-not-received, billing errors, or subscription cancellation complaints. Merchants remain liable for those regardless of authentication.
Chargeflow tailors automated dispute handling to the liability rules of every payment method you accept: request a demo and see how fast it can start clearing disputes across cards, wallets, BNPL, and beyond.

Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.














.png)
%20(1).webp)
.webp)
.webp)