Most retailers sign up for Buy Now Pay Later believing the provider absorbs all the downside: the customer fails to pay, and Klarna or Affirm eats the loss. That is true for credit risk. It is not true for dispute risk. When a shopper claims the jacket never arrived, the size was wrong, or the charge was fraudulent, the financial exposure routes straight back through your merchant agreement, and the rules are not the ones you learned from card processing.
The confusion is expensive. A BNPL dispute can pull funds from a settlement you already counted as revenue, weeks after the order shipped, and the documentation that would have saved a Visa case is often useless against an installment provider. Understanding exactly what you are liable for, and what the BNPL provider eats, is the difference between a 0.4% dispute rate you can budget for and a clawback problem that quietly erodes margin all quarter.
This guide breaks down the mechanics for retailers running installment payments at checkout, drawing on how card disputes work upstream of every BNPL transaction. If you want the underlying rails first, our explainer on how card networks really work behind every retail checkout covers the settlement and chargeback plumbing that BNPL providers sit on top of.
In short
- BNPL chargebacks are not card chargebacks. The provider, not Visa or Mastercard, owns the dispute process, and the deadlines, reason codes and evidence rules are set by the provider’s merchant agreement.
- You are liable for merchandise and service disputes (item not received, not as described, returns mishandled) almost exactly as you would be with a card. The provider claws the funds from your settlement.
- Fraud liability is split and provider-specific. Many BNPL networks absorb confirmed third-party fraud, but only if you followed their verification flow and did not override risk signals.
- Your win rate depends on evidence you collect at fulfillment, not at dispute time. Delivery confirmation, AVS-style identity checks and clear product descriptions decide cases.
- Reconciliation is the hidden cost. BNPL clawbacks hit net settlement in batches, so without line-item reporting you will not see which orders were reversed.
Who actually pays when a BNPL order is disputed?
In a standard installment transaction, the BNPL provider pays you upfront (minus their fee) and then collects from the shopper over time. That funding model is why merchants assume the provider owns all the risk. The reality is that the provider takes on credit risk, the chance the customer simply stops paying, while you retain most of the transactional dispute risk, the chance the customer claims something went wrong with the order itself.
When a shopper disputes, the provider investigates and, if it sides with the buyer, debits the disputed amount from your next settlement. This is functionally a chargeback, but it is governed by your contract with the provider rather than by card network rules. There is no Visa arbitration backstop, no standardized reason code library, and the timelines can be shorter and less forgiving.
The split below is the pattern across major US providers in 2026. Always confirm against your specific merchant agreement, because terms differ by provider, region and even merchant category.
| Dispute type | Typical liable party | What decides it |
|---|---|---|
| Item not received | Merchant | Delivery confirmation and tracking to the order address |
| Item not as described | Merchant | Product listing, photos, return handling records |
| Duplicate or incorrect charge | Merchant | Transaction logs, refund timing |
| Confirmed third-party fraud | BNPL provider (conditional) | Whether merchant followed the provider’s verification flow |
| Credit default (customer never pays) | BNPL provider | Provider’s underwriting, no merchant exposure |
| Buyer’s remorse / change of mind | Merchant via return policy | Your stated returns terms, not a dispute right |
The single most important line is the last fraud row. Provider-absorbed fraud is conditional, and the condition is procedural: you must have used the checkout flow the provider gave you, passed the device and identity signals back, and not manually forced an order through after a decline. Override the risk engine and you usually inherit the fraud loss.
It is worth being precise about the economics, because the credit-versus-dispute distinction is what most merchant teams get wrong in their forecasting. When a customer simply stops paying their installments, the provider already paid you in full at the point of sale, so the unpaid balance is the provider’s problem and never touches your settlement. That is genuine risk transfer, and it is what the BNPL sales pitch is really selling. A dispute is the opposite shape: the provider paid you, the customer is contesting the transaction itself, and the provider reclaims the funds it advanced. The cash flow looks identical to a card chargeback, which is exactly why so many retailers misfile BNPL losses as bad debt instead of as contestable disputes they could have won with better evidence.
That misclassification has a downstream cost. If your finance team books BNPL reversals as credit write-offs, nobody owns the dispute response, the win-back evidence never gets submitted, and a recoverable loss becomes permanent. Treating reversals as disputes from the start puts them in front of the person who can actually contest them.
One nuance for higher-risk categories. Some providers carve out fraud protection entirely for certain merchant categories (digital goods, gift cards, high-resale-value electronics) where chargeback abuse is common. If you sell in those segments, do not assume the standard fraud-absorption clause applies; the carve-out is usually buried in an addendum, and discovering it after a fraud wave is an expensive way to learn.
How a BNPL dispute differs from a card chargeback
Retailers who have run card payments for years carry assumptions that quietly sabotage BNPL cases. The biggest one is the reason code. Card chargebacks arrive with a standardized code (10.4 for fraud, 13.1 for non-receipt) that tells you exactly what evidence the network wants. BNPL disputes arrive in the provider’s own taxonomy, which is often vaguer and reviewed by a human against the provider’s policy rather than a card scheme rulebook.
The second assumption is the timeline. Card networks give you a representment window, frequently 20 to 45 days depending on the network and code. Several BNPL providers compress this to 7 to 14 days, and a missed response is an automatic loss with no second cycle. The third is the evidence channel: you upload documentation through the provider’s merchant portal, not a processor gateway, and formatting requirements vary.
Here is the practical sequence a BNPL dispute follows, and where you can act:
- Shopper opens a dispute with the provider, often through the same app they pay their installments in. You are not in this conversation.
- Provider provisionally debits the amount from your pending settlement or flags it for clawback. Cash leaves before you have argued anything.
- You receive a notification with the provider’s dispute reason and a response deadline. This is the moment the clock that matters starts.
- You submit evidence through the merchant portal: tracking, signed delivery, product description, communication history, refund records.
- Provider rules and either reverses the debit (you win) or finalizes it (you lose). Some providers allow one appeal, many do not.
- You reconcile the outcome against settlement, which is where most merchants lose visibility entirely.
Because the funding sits on card and wallet rails underneath, a customer can sometimes attack from two directions at once: dispute through the BNPL app and chargeback the underlying card or wallet used to repay installments. Our breakdown of Apple Pay, Google Pay and PayPal at retail checkout explains why wallet-funded repayments add a second liability layer you need to watch for double exposure.
What evidence actually wins a BNPL dispute
The uncomfortable truth is that BNPL disputes are won or lost at fulfillment, not at response time. By the time the notification lands, the evidence either exists or it does not, and there is no retroactive way to prove a package arrived if you shipped without tracking. The winning posture is to treat every BNPL order as if it will be disputed and capture the proof by default.
For item not received claims, the decisive artifact is end to end tracking that shows delivery to the address on the order, ideally with a signature or photo for higher-value items. A carrier scan that simply says “delivered” to a city is weak; a scan tied to the exact shipping address is strong. For not as described claims, the listing itself is your evidence, so vague or aspirational product copy works against you. Concrete dimensions, materials and accurate photos give the reviewer something objective to weigh.
For suspected fraud, the record that matters is your adherence to the provider’s verification flow, the IP and device data passed at checkout, and any address mismatch you flagged. The table below maps dispute reasons to the evidence that moves the needle.
| Dispute reason | Evidence that wins | Common reason merchants lose |
|---|---|---|
| Item not received | Address-matched tracking, signature or delivery photo | Shipped without tracking, or tracking shows wrong address |
| Not as described | Detailed listing, accurate photos, spec sheet | Marketing copy that overpromises, no photos |
| Return not refunded | Refund timestamp, return policy, RMA log | Refund issued late or to a different method |
| Fraudulent order | Passed provider verification, device and IP match | Manual override of a declined or flagged order |
| Duplicate charge | Single transaction log, void confirmation | Two captures on one authorization |
One operational point is worth bolding: refund through the BNPL provider, never around it. If a shopper returns an item and you refund their card directly instead of through the provider’s flow, the installment plan keeps running, the customer disputes the ongoing charges, and you have now paid twice with no clean record. Always reverse through the same provider that funded the order.
Building BNPL dispute defense into your stack
Disputes are a process problem before they are a payments problem. The merchants with sub-0.5% BNPL dispute rates are not luckier; they have wired prevention into fulfillment and reconciliation. If you are still in the setup phase, the architecture decisions you make now determine how defensible you are later, which is why we walk through provider selection and checkout placement in our guide to adding BNPL to a Shopify or WooCommerce store the smart way.
Three controls do most of the work. First, tracking on every order, with signature capture above a value threshold you set against your average order value and fraud history. Second, a reconciliation process that ingests provider settlement files at line-item level so a clawback never hides inside a net deposit. Third, a response SLA: assign an owner, set an internal deadline two days inside the provider’s window, and template the evidence packet per reason code so nobody scrambles.
The reconciliation point deserves emphasis because it is where margin silently leaks. BNPL providers settle net of disputes, fees and refunds, so a daily deposit can already have clawbacks baked in. Without parsing the detail file, you book the gross as revenue and never notice the reversals. Match every disputed order ID against fulfillment and you turn an invisible cost into a measurable, contestable one.
A useful exercise for any merchant past their first BNPL quarter is to calculate a true BNPL dispute rate the way the provider does: disputed transactions divided by total BNPL transactions, tracked monthly. If that number drifts above roughly 0.5%, you are heading toward the zone where providers raise fees, hold reserves or reconsider the relationship, much as card networks place merchants in monitoring programs above their own thresholds. Catching the trend early, while it is still three or four orders a month, is far cheaper than reacting after a reserve is imposed.
Finally, do not let the operational burden tempt you into manual order overrides to chase conversion. The team that approves a flagged BNPL order to save a sale is the same team that absorbs the fraud loss and the dispute response cost when it goes wrong. The disciplined posture, pass the provider’s signals, ship with tracking, refund through the provider, reconcile at line level, is unglamorous, but it is what keeps the dispute rate low enough that BNPL stays the cheap, high-conversion payment method it is supposed to be.
Common mistakes
Assuming the provider eats every loss. The BNPL pitch leans on “we take the risk,” and merchants generalize that to all risk. Credit default, yes. Merchandise and service disputes, no. Budget for a dispute rate just as you would with cards.
Refunding outside the provider’s flow. Issuing a direct card refund on a BNPL order leaves the installment plan live, triggers downstream disputes, and double-charges your books. Always refund through the provider.
Treating BNPL deadlines like card deadlines. The shorter response windows catch teams that batch dispute handling weekly. A 7-day window and a Friday-only workflow means automatic losses.
Overriding the risk engine to save a sale. Manually pushing a flagged order through often voids the provider’s fraud liability protection, so you save one sale and inherit the fraud loss on it.
Shipping high-value BNPL orders without signature. Installment orders skew toward higher tickets, exactly the segment where unsigned delivery loses non-receipt disputes.
Not reconciling at line-item level. Net settlement hides clawbacks. If you cannot tie a reversal to an order, you cannot contest it or even see the trend.
Frequently asked questions
Is a BNPL chargeback the same as a credit card chargeback?
No. A card chargeback is governed by Visa or Mastercard rules with standardized reason codes, defined representment windows and an arbitration backstop. A BNPL dispute is governed by your merchant agreement with the provider. The provider sets the reason taxonomy, the response deadline (often shorter), the evidence format and whether you get any appeal. Functionally the money still leaves your settlement, but the rulebook is the provider’s, not the network’s, so card-trained processes need adapting.
Who is liable if a BNPL order turns out to be fraud?
It depends on whether you followed the provider’s verification flow. Most major BNPL networks absorb confirmed third-party fraud as part of their underwriting, but that protection is conditional. If you passed the device, identity and address signals through their checkout and did not manually override a declined or flagged transaction, the provider typically eats the loss. If you forced the order through against the risk engine, you usually inherit the fraud liability. Read the fraud clause in your specific agreement.
How long do I have to respond to a BNPL dispute?
Shorter than you expect. While card networks often allow 20 to 45 days for representment, several BNPL providers compress the response window to roughly 7 to 14 days, and many give no second cycle. A missed deadline is an automatic loss. Set an internal SLA at least two days inside the provider’s window and assign a named owner so disputes never sit in a weekly batch queue.
What is the best evidence to win a non-receipt dispute?
Address-matched delivery confirmation. A tracking record that shows the package delivered to the exact shipping address on the order, ideally with a signature or delivery photo for higher-value items, is the strongest evidence. A generic “delivered to city” scan is weak. Because non-receipt claims are decided on this single artifact, the practical rule is to add tracking to every BNPL order and signature capture above a value threshold tied to your average order value.
If a customer returns a BNPL item, how do I refund correctly?
Always refund through the same BNPL provider that funded the order, never directly to the card. Refunding around the provider leaves the installment plan running, the customer disputes the continuing charges, and you end up paying twice with no clean record. Process the return through the provider’s refund flow so the plan is cancelled or adjusted, then keep the refund timestamp and RMA record in case a dispute is filed anyway.
Why do BNPL clawbacks keep surprising my finance team?
Because providers settle net of disputes, refunds and fees. Your daily deposit can already have clawbacks deducted, so if you book the gross sale as revenue and never parse the detailed settlement file, the reversals are invisible. The fix is line-item reconciliation: ingest the provider’s settlement detail, match every reversed order ID against fulfillment, and surface clawbacks as a tracked metric rather than a mystery shortfall in the deposit.
Can a customer dispute the same order twice, through BNPL and their card?
Yes, and it is a real exposure. BNPL installments are usually repaid from a card or wallet, so a determined or confused customer can open a dispute in the BNPL app and separately chargeback the underlying funding instrument. You can face two parallel claims on one order. Watch for double exposure during reconciliation, respond to both channels with the same evidence packet, and flag duplicate claims to the provider explicitly.
Does a high BNPL dispute rate affect my account like card chargeback ratios do?
It can. Just as card networks place merchants in monitoring programs above roughly 0.9% to 1% chargeback ratios, BNPL providers track dispute and loss rates and can raise your fees, tighten reserves, or offboard you if disputes climb. The thresholds are provider-specific and set in your agreement. Treat your BNPL dispute rate as a managed KPI, aim well under 0.5%, and invest in fulfillment evidence before the provider forces the issue.
What’s next
Audit your last quarter of BNPL settlements at line-item level and tag every clawback by reason; the pattern usually points to one fixable gap, often unsigned high-value shipments or refunds processed outside the provider. Because BNPL disputes ultimately resolve against the card and wallet rails beneath them, it pays to revisit how those rails settle and reverse in our explainer on how card networks really work behind every retail checkout before your next provider review. For the macro picture on how payment shifts and regulation are reshaping installment risk this year, our coverage of how retail news shapes the global e-commerce industry today is a useful companion, and the US Consumer Financial Protection Bureau’s consumer protection guidance on BNPL tracks the regulatory direction that will eventually flow into provider dispute terms.