Buy now, pay later has become a standard checkout option in US retail, and most merchants integrated it the way they integrate any wallet: turn it on, watch conversion, move on. The trouble starts later, on the return desk. A BNPL order that comes back does not unwind the way a card order does, because there are two separate money flows to reverse and two different rulebooks governing them.
This guide walks through what actually happens when a BNPL order goes wrong: how refunds propagate, how partial returns rewrite an installment schedule, who the customer calls first, what fees you keep paying on money you gave back, and how disputes interact with consumer credit rules. It is written for merchants running BNPL at volume, not for shoppers.
In short
- A BNPL refund is two reversals, not one. The provider already paid you and separately extended credit to the shopper, so your refund settles the merchant leg while the provider rewrites the consumer leg on its own schedule.
- Partial returns are the hard case. Most providers recalculate the remaining installments rather than refunding cash, which means a shopper can return half an order and still owe money for weeks.
- Your merchant fee is usually not returned. Card acquirers commonly refund interchange on a refunded sale, while several BNPL providers keep the merchant discount rate, so refund-heavy categories carry a structurally worse effective take rate.
- Disputes route to the provider, not the card networks. There is no Visa or Mastercard reason code and no representment window in the usual sense, so your evidence pack has to satisfy a provider policy instead of a network rule.
- Regulatory treatment is unsettled and moving. Pay-in-four in the US has been the subject of shifting CFPB guidance, and the UK moved BNPL under FCA supervision, so any specific right or deadline should be verified at the regulator before you write it into policy.
Why a BNPL refund is not the same as a card refund
On a card sale, the money path and the credit path are the same path. The issuer funds the purchase, the acquirer settles you, and a refund pushes a credit back down that identical rail until it lands on the cardholder statement. One transaction, one reversal, one balance to correct.
BNPL splits that into two contracts that happen to fire at the same moment. The provider pays you the full order value up front, minus its fee, and takes the receivable. Separately, the provider signs a consumer credit agreement with the shopper for four payments, or six months, or whatever the plan is.
When you refund, you are only unwinding your side. You send a refund instruction to the provider, the provider claws that value back from your next settlement batch, and then the provider decides what to do with the shopper’s outstanding schedule. Those two events are not synchronous and often are not even the same amount.
That asymmetry is the root of nearly every BNPL refund complaint. The shopper watched the return get scanned at your warehouse, saw your confirmation email, and then got debited for installment three anyway because the provider had not processed the adjustment yet. From the shopper’s point of view you took the money. From your point of view you refunded on time.
The same structural gap shows up in fraud handling, where the party holding the liability is not always the party the customer is talking to. Our payment fraud and chargeback prevention guide covers the card-side version of that problem in depth, and the BNPL case is the same shape with a different counterparty.
The three timelines that never line up
It helps to name the clocks explicitly, because support teams tend to quote whichever one they can see. There are three, and each is controlled by a different party.
The merchant clock starts when you mark the return received and issue the refund in your order management system. The provider clock starts when the provider ingests that refund and recalculates the plan, which can lag by one to three business days depending on integration type. The bank clock starts only if cash actually has to move back to the shopper’s funding card, and that adds the usual settlement time on top.
A shopper who returns an item on day one may therefore see the plan corrected on day three and cash back on day seven, while your own dashboard says “refunded” on day one. Publishing all three numbers, rather than the first one, removes most of the escalation volume on its own.
What the comparison actually looks like
| Dimension | Card refund | BNPL refund |
|---|---|---|
| Parties to unwind | One flow: acquirer to issuer to cardholder | Two flows: merchant settlement plus consumer credit schedule |
| Who holds the consumer relationship | Card issuer | BNPL provider, contractually separate from you |
| Partial refund handling | Straight partial credit to the same account | Usually a schedule recalculation, cash only if already overpaid |
| Typical visibility to shopper | Pending credit on statement | Provider app, often updated on a batch cycle |
| Dispute venue | Card network reason codes, defined representment window | Provider dispute policy, plus applicable consumer credit rules |
| Merchant fee on refunds | Interchange commonly returned, scheme fees vary | Merchant discount rate frequently retained by the provider |
| Chargeback exposure | Direct, network governed | Indirect, plus a possible card chargeback on the funding instrument |
Read the last row twice. A shopper who pays a BNPL installment with a debit card and then gets no resolution can still file a card dispute against that installment. You can end up with a provider dispute and a card chargeback about the same order, from different rails, at different times.
Partial returns and how installment plans get recalculated
Full returns are boring. The provider cancels the remaining schedule, refunds anything already collected, and everyone moves on. Partial returns are where policy documents go to die.
Suppose a shopper buys four items for $400 on a pay-in-four plan of $100 every two weeks. They pay installment one, then return two items worth $180. You issue a $180 refund. What should the shopper’s remaining balance be, and when should they feel it?
Reduce the tail, not the head
The dominant provider convention is to apply the refund against the last scheduled payments first, working backwards. In the example above, the $300 still outstanding becomes $120, so installment four disappears entirely and installment three shrinks. Installment two is untouched and still collects on schedule.
This is the single most common source of “you charged me after my return” complaints. The shopper expected the next debit to stop. Instead the next debit ran in full and the relief landed weeks later at the end of the plan.
A minority of providers, and some longer-term financing products, instead re-amortize the whole plan so every remaining payment shrinks proportionally. Neither approach is wrong. What matters is that your support team knows which one your provider uses, because the two produce completely different answers to “when do I stop being charged”.
When cash actually comes back
Cash only returns to the shopper when the refund exceeds what they still owe. If the shopper in our example had paid three installments ($300) before returning $180 of goods, the outstanding $100 is cleared and $80 goes back to their original funding method.
That cash leg reintroduces normal payment settlement time, which is why the total shopper-side wait can be longer for a partial return than for a full one. It is counterintuitive and worth saying out loud in your returns policy.
Shipping, discounts and the allocation problem
Partial returns force an allocation decision that most merchants never make explicitly. If the order had a 20% cart-level discount and a shipping charge, how much of each attaches to the returned items?
Get this wrong and you refund more than you should, which the provider will happily pass along, or less than you should, which generates a dispute. Encode the rule in your order management system rather than leaving it to a returns agent, and make sure the refund line items you send the provider reflect the same allocation you booked internally.
Exchanges are not returns
An even exchange is the cleanest possible outcome because the plan does not need to change at all. Most providers support keeping the original plan intact if the replacement order value matches. An uneven exchange, however, usually cannot be handled as an amendment: the standard pattern is refund in full, then originate a new plan for the new item, which restarts the schedule and can fail if the shopper’s spending limit has since been consumed.
Teams that treat exchanges as a refund plus a re-purchase without warning the shopper create a specific and avoidable failure mode: a customer who wanted a size swap and instead got declined at re-checkout.
Who the customer complains to first, and who resolves it
Almost always the customer complains to you first, and almost always the resolution sits with the provider. That gap is the operational core of BNPL support.
The shopper’s mental model is simple: they bought a jacket from your store, so the jacket problem is your problem. They do not distinguish between the merchant of record and the credit provider, and telling them to “contact Klarna” reads as a brush-off even when it is factually correct.
The workable division is this. You own the goods question: was the item shipped, was it received, was it faulty, was the return accepted. The provider owns the money question: what the schedule now says, when the debit stops, whether a late fee is waived.
Most escalations happen when a merchant answers only the goods question and stops. The shopper still does not know when the charging ends, so they escalate. Answering both, and explicitly saying which part the provider controls, cuts repeat contacts substantially.
When the complaint is really a fraud claim
A meaningful share of “I did not authorize this” BNPL contacts are not third-party fraud at all. They are customer regret, buyer’s remorse, or a family member using the account, and they arrive dressed as fraud because that is the fastest route to a reversal. The pattern is well documented on the card side and it transfers cleanly to BNPL, as covered in our piece on telling customer regret apart from card theft.
The practical difference is that BNPL onboarding is thinner than card issuance, so genuine account takeover is a real risk and you cannot dismiss the claim on volume alone. Treat the delivery evidence, device signals and account age as the deciding factors rather than the customer’s framing.
Authentication step-ups matter here too. Where a plan was originated with a strong authentication event on the funding instrument, the liability picture changes, which is the same logic explained in our walkthrough of 3-D Secure 2 without wrecking your conversion rate.
A routing table worth putting on the wall
| Customer says | Owner | First action |
|---|---|---|
| “My order never arrived” | Merchant | Confirm tracking, then refund or reship; notify provider on refund |
| “I returned it and I am still being charged” | Shared | Confirm return received, give the provider processing window in days |
| “The amount on my plan is wrong” | Provider | Send the refund reference and line-item breakdown to the provider |
| “I was charged a late fee” | Provider | Merchant cannot waive; refer with context, ask for goodwill review |
| “I did not open this plan” | Provider | Treat as suspected fraud, hold shipment if possible, preserve evidence |
| “The item is faulty” | Merchant | Standard warranty path; refund triggers plan adjustment automatically |
| “I want to cancel before shipping” | Merchant | Void rather than refund where the provider supports it, which is cleaner |
Voiding is underused. If the order has not shipped and the provider supports a void or cancellation before capture, use it. A void avoids the fee-retention question entirely on most provider contracts and leaves no residual schedule to explain.
Merchant fees on refunded BNPL orders
Here is the line that surprises finance teams. On a card refund, interchange is commonly returned to the merchant, so the economic damage of a refund is mostly the lost margin plus handling. On BNPL, several providers retain the full merchant discount rate on a refunded order.
At a 4% to 6% merchant discount rate, which is the typical BNPL band for pay-in-four in the US market, a 30% return rate means you are paying that rate on gross rather than net sales. In apparel, where returns routinely run above 30%, the effective take rate on kept revenue is materially higher than the headline rate on the contract.
The correct way to model this is not the quoted rate. It is the quoted rate divided by one minus your return rate, adjusted for whichever fee components the provider actually gives back.
| Scenario | Gross sales | Returns | Net sales | Fee if MDR retained (5%) | Effective rate on net |
|---|---|---|---|---|---|
| Low-return category | $100,000 | 8% | $92,000 | $5,000 | 5.43% |
| Mixed catalog | $100,000 | 18% | $82,000 | $5,000 | 6.10% |
| Apparel and footwear | $100,000 | 32% | $68,000 | $5,000 | 7.35% |
| High-return, bracketed sizing | $100,000 | 45% | $55,000 | $5,000 | 9.09% |
Those figures assume the provider retains the full fee, which is a contractual matter and varies by provider, region and negotiated agreement. Some providers return a portion, some return nothing, some return the full fee if the refund happens within a short window such as a few days after capture. Check your own merchant agreement rather than assuming the table applies to you.
The short-window clause is worth hunting for
Where a provider does refund fees inside a defined early window, the operational implication is concrete: cancel-before-ship should be processed the same day, not batched overnight. A twelve-hour delay in your cancellation queue can be the difference between a fee returned and a fee retained, repeated across every cancellation you handle.
Other charges that survive a refund
Beyond the discount rate, watch for per-transaction fixed fees, dispute handling fees and, on some longer-term financing products, a subsidised interest cost you already paid to buy down the shopper’s rate. Subsidised-rate promotions are the sharpest version of this: you paid for a 0% offer, and if the goods come back, that subsidy is generally not recoverable.
Disputes, consumer credit rules and what providers must do
BNPL disputes do not run on card network rails. There is no reason code taxonomy, no fixed representment deadline set by a scheme, and no arbitration tier. What exists instead is a provider dispute policy, sitting on top of whatever consumer credit law applies in the market.
That makes the process feel less predictable than a card chargeback even though it is often faster. Providers generally ask the shopper to contact the merchant first, pause the affected installments while the case is open, request evidence from the merchant within a stated window, and then decide.
Where US regulation currently sits
The Consumer Financial Protection Bureau issued an interpretive rule in May 2024 treating pay-in-four BNPL lenders as credit card providers for certain purposes under Regulation Z, including dispute and refund handling obligations. The agency subsequently signalled changes in its enforcement posture toward that rule, and its status has been contested since.
Because that position has moved more than once, treat any specific obligation as something to verify at the source before you build policy around it. The CFPB publishes current rules and guidance, and the underlying statute is the Truth in Lending Act as implemented by Regulation Z. Do not quote a right or a deadline to a customer from a blog post, including this one, without checking it there first.
The practical merchant takeaway is stable even while the legal position is not. Providers already operate dispute processes that resemble card dispute processes, and building your evidence discipline to that standard protects you regardless of how the rulemaking settles.
The UK went a different way
The United Kingdom moved buy now, pay later into the Financial Conduct Authority’s regulatory perimeter, bringing affordability checks, information requirements and access to the Financial Ombudsman Service for consumers. That is a materially stricter regime than the US position, and merchants selling into both markets should not assume one policy covers both. We looked at the checkout-volume consequences in our report on the FCA regulating buy now, pay later.
If you operate cross-border, version your BNPL returns policy by market. A single global page that quotes US practice will be wrong in the UK and vice versa.
Evidence packs that actually decide cases
The evidence that wins a BNPL dispute is nearly identical to what wins a card representment, which is convenient because you probably already collect it. Order confirmation with the item and price, proof of delivery with timestamp and address match, your returns policy as it appeared at purchase time, the returns communication trail, and the refund reference with amount and date.
What differs is the framing. A card representment argues against a specific reason code. A BNPL dispute argues against a narrative, so a short factual chronology at the top of the pack does more work than it would on the card side. Our guide to building chargeback evidence that actually wins covers the underlying discipline, and the same file structure serves both.
Keep one thing separate: the funding-instrument chargeback. If a shopper disputes an installment debit with their own bank, that case runs on card rails against the provider, not against you, but providers commonly pass the cost through contractually. Read that clause before you sign.
Support scripts and policy wording that prevent escalation
Most BNPL escalation is caused by wording, not by money. The customer is not angry that a process takes five days. They are angry that nobody told them it would.
Three wording changes remove the majority of repeat contacts. Name the provider explicitly rather than saying “your payment method”. Give a date range in days rather than saying “shortly”. Say what will happen to the next scheduled payment, because that is the thing the customer is actually worried about.
Returns page wording
Your returns page should carry a BNPL-specific paragraph, not a generic refund promise. Something close to this works: refunds for orders paid with a buy now, pay later plan are sent to the provider within one business day of the return being received, the provider then updates the payment schedule, which typically takes a further one to three business days, and any payment already scheduled inside that window may still be collected before the adjustment lands.
That last clause is doing the heavy lifting. It sets the expectation before the debit rather than explaining it afterwards.
Agent macro for the most common case
For “I returned it and I am still being charged”, the sequence that resolves fastest is: confirm the return was received and give the date, confirm the refund amount and the reference sent to the provider, state the provider’s typical processing window in days, explain that the refund reduces the final payments first if that is how your provider works, and give the provider’s contact route for schedule questions and fee waivers.
Note what is missing: an apology for a delay that is not a delay, and any promise about the exact debit date, which you do not control. Overpromising on the provider’s behalf converts one contact into three.
What not to say
Avoid “we have refunded you”, because on a partial return the shopper may receive no cash at all. Say “we have sent the refund to the provider and it reduces your outstanding balance”. Avoid “contact the provider” as a standalone answer. Avoid quoting late fee policy, since fees belong to the provider and a merchant guess that turns out wrong becomes a legitimate complaint.
Reconciliation: matching BNPL settlements to refunds
Finance teams discover the reconciliation problem about a quarter after launch, usually as an unexplained variance between order value and cash received. The cause is almost always that the refund and the settlement adjustment appear in different periods, at different granularity, under different identifiers.
BNPL settlement files are batch documents. A single payout can contain new orders, refund clawbacks from earlier orders, fee lines, dispute holds and adjustments, all netted into one bank credit. If your accounting integration books the bank credit as revenue, the numbers will never tie.
Match on the provider reference, not the order number
The most common integration mistake is reconciling on your own order number. Refund clawbacks frequently carry the provider’s own plan or capture identifier rather than your order id, especially where a single order produced multiple captures or a partial refund.
Store the provider’s identifier on the order record at authorization time and index on it. That one change resolves the majority of unmatched lines.
Book the fee separately from the refund
If the provider retains its fee on a refunded order, the accounting reality is a full revenue reversal plus a retained expense, not a reduced refund. Netting them hides the cost and makes the refund-rate impact on margin invisible to whoever is choosing which payment methods to promote.
The reconciliation fields that matter
| Field | Source | Why it matters |
|---|---|---|
| Provider plan or capture id | Authorization response | Primary key for matching clawbacks to originals |
| Refund reference and timestamp | Refund API response | Proves the refund date in disputes and in support replies |
| Refund line items | Order management system | Lets the provider allocate discounts and shipping correctly |
| Fee retained flag | Settlement file | Separates true refund cost from retained processing cost |
| Settlement batch id | Settlement file | Ties the netted bank credit back to component transactions |
| Dispute hold amount | Settlement file | Explains cash held against open cases, not lost |
| Currency and FX rate | Settlement file | Cross-border variance is otherwise attributed to refunds |
Close the loop monthly, not quarterly
Run a monthly exception report on refunds issued in your system with no matching provider clawback, and clawbacks with no matching refund. Both directions matter. The first catches refunds the provider never ingested, where a customer is still being debited for goods you already took back. The second catches double refunds, where a customer got both a provider adjustment and a manual cash refund from an agent trying to be helpful.
Double refunds are quietly expensive and are almost never detected by looking at the order alone. The same reconciliation discipline that catches them also supports the loss-prevention work described in our payment fraud and chargeback prevention guide, since the exception patterns overlap heavily.
This article is general information, not legal or financial advice
Everything above describes how BNPL refunds and disputes generally work as an operational matter. It is education, not advice, and it is not a substitute for professional guidance on your own situation.
Consumer credit rules differ by country and by state, they apply differently depending on the product structure, and the US position on pay-in-four in particular has changed more than once in recent years. Fee treatment, dispute windows and refund mechanics are governed by your specific merchant agreement, which will not match every general description here.
Before you publish a returns policy, respond to a regulatory inquiry or rely on a particular consumer right, consult a qualified consumer credit attorney or a compliance advisor licensed in the relevant jurisdiction, and verify current rules directly with the regulator. Background material on the broader product category is available on Wikipedia, which is a useful orientation but is likewise not a legal source.
FAQ on BNPL refunds
How long does a BNPL refund take?
Expect three separate stages. The merchant issues the refund, typically within one business day of receiving the return. The provider ingests it and updates the schedule, commonly a further one to three business days. If cash is owed back to the shopper, normal card settlement time applies on top, which is usually several more days. Providers publish their own service levels, so quote your provider’s figure rather than a generic one.
Why is a customer still being charged after returning an item?
Two reasons dominate. Either the refund had not reached the provider before the next scheduled debit ran, or the return was partial and the provider applied the refund to the final installments first, leaving the next one intact. Both are normal behaviour rather than errors, but both need to be explained before the debit rather than after.
Do merchants get their BNPL fee back on a refund?
Often not. Several providers retain the merchant discount rate on refunded orders, unlike card interchange which is commonly returned. Some return the fee if the refund happens inside a short window after capture. This is a contractual term, so check your merchant agreement rather than assuming either outcome.
Can a shopper file a chargeback on a BNPL order?
Not against the plan itself, because the plan is not a card transaction. They can dispute with the BNPL provider under its dispute policy, and they can separately file a card chargeback against an individual installment debited to their funding card. Many merchant agreements pass the cost of that second route back to the merchant.
What happens to a BNPL plan on a partial return?
Most providers reduce the outstanding balance by applying the refund to the last scheduled payments first, so late installments shrink or disappear while the next one is unchanged. Some products re-amortize instead, reducing every remaining payment proportionally. Cash goes back to the shopper only when the refund exceeds what they still owe.
Who is responsible when a BNPL order never arrives?
The merchant owns the delivery question and should refund or reship as it would for any other payment method. The provider owns the resulting schedule adjustment and any fee waiver. Answering only the delivery half is the most common cause of escalation.
Are BNPL providers regulated in the United States?
The picture has shifted. The CFPB issued an interpretive rule in May 2024 applying certain Regulation Z credit card provisions, including dispute and refund handling, to pay-in-four lenders, and its enforcement posture toward that rule has since changed. State-level licensing also applies in various forms. Verify the current position directly with the CFPB and with counsel before relying on any specific obligation.
How should exchanges be handled on a BNPL order?
An even exchange can usually keep the original plan intact, which is the cleanest outcome. An uneven exchange normally requires a full refund and a brand new plan, which restarts the schedule and can be declined if the shopper’s available limit has been consumed in the meantime. Tell the customer this before processing, not after a decline.
Should a merchant cancel or refund an unshipped BNPL order?
Cancel or void where the provider supports it. A void before capture usually avoids the fee retention question entirely and leaves no residual schedule to explain to the shopper. Processing cancellations same-day rather than in an overnight batch is one of the few BNPL cost levers a merchant fully controls.