BNPL Dispute Evidence: Build Order-Level Packets for Delivery, Returns and Billing Claims

BNPL dispute evidence is the set of order, shipping, support and payment records a merchant sends to a buy now, pay later provider to answer a customer dispute. A strong packet ties the case to the exact items, captures and refunds involved.

There is no shared BNPL dispute form. Klarna, Afterpay, Affirm and Sezzle each set their own deadlines, reasons and upload rules. This guide gives you:

• A side-by-side table of provider deadlines and evidence rules.
• A case index that ties every record to the disputed items.
• Three worked packets: a split shipment, a partial return and a disputed invoice amount.

Still choosing a provider? Start with Chargeflow's BNPL comparison. This article covers what goes inside the packet once a case arrives.

Why BNPL Disputes Need Their Own Evidence Packet

BNPL disputes are not rare. The CFPB found that more than 13% of BNPL transactions involved a return or dispute. Shoppers disputed or returned $1.8 billion in purchases at five large lenders in 2021.

Loan counts and average value come from the Federal Reserve Bank of Atlanta summary of the same CFPB study.

Most teams learn disputes through card networks. If you need a refresher on the chargeback meaning and lifecycle, start there. BNPL cases differ in three ways:

• The provider decides. The shopper files in the Klarna, Afterpay, Affirm or Sezzle app, and that provider reviews your evidence.
• The shopper may stop paying. Affirm pauses customer payments while a dispute is open. Klarna pauses repayments when a shopper files an inquiry.
• You often get one shot. Afterpay's API and Klarna disputes through Stripe accept a single round of evidence. There is no draft step.

US rules do not fill the gap. In May 2024 the CFPB issued an interpretive rule that treated BNPL lenders like credit card issuers. It covered dispute investigations, payment pauses and refund credits. The Bureau withdrew that rule effective May 12, 2025. Today, provider terms and your merchant agreement set the process.

Fraud claims follow the same provider route. For stolen identities and account takeover, see our guide to buy now, pay later fraud. For adoption and market data, see the latest BNPL statistics.

BNPL Dispute Deadlines and Evidence Rules by Provider

Each provider runs its own clock. Use this table to set internal due dates, then confirm the exact date on the live notice.

Sources: Klarna dispute states and evidence gathering, Stripe Klarna disputes, Afterpay Online disputes, Affirm US dispute resolution and Sezzle merchant help. Reviewed October 25, 2026.

Set your internal deadline two to three days before the provider's. That leaves time to chase a carrier record or a missing refund reference.

Still weighing providers? Compare plans and merchant fees in Klarna vs Afterpay and Sezzle vs Affirm.

Identify the Provider, Product and Case Route

A customer may call it a "Klarna chargeback" or an "Afterpay dispute." Neither label tells you where to respond. Read the notice first.

A direct integration and the same payment method sold through a processor can run different workflows. Klarna through Stripe is a clear example: evidence goes in through Stripe, and only after the inquiry escalates. Our Klarna chargeback guide covers the direct route.

Keep three cases apart: a merchandise complaint to the provider, a repayment question from the shopper, and a card dispute on the card used to repay. Only the first asks you for an order packet.

Build One Case Index Before You Collect Attachments

Give each packet an index. It links your records so a reviewer can follow them without knowing your systems. Use real IDs; the labels below describe records, not API field names.

Follow these rules as you fill the index:

• If an order has several captures, list each one. Do not attach the latest capture as the full payment history.
• If a parcel holds one item, name that item. Do not claim the whole order was delivered.
• If records do not join on their own, add the invoice or fulfillment row that connects them.
• Keep status words exact. "Refund approved," "refund submitted" and "refund completed" are three different events.

Our chargeback evidence source map shows where each record usually lives across store, carrier, support and payment systems.

Match Each Piece of Evidence to the Dispute Reason

Evidence only helps when it answers the stated claim. Proof of delivery wins a not-received case. It does nothing for a missing refund.

Sources: Klarna evidence requirements, Affirm evidence examples and Stripe evidence fields for Klarna.

Card networks follow the same logic. See how to tailor chargeback evidence to each reason code for the card-side version. Log friendly fraud patterns too, such as a shopper who disputes after a confirmed delivery.

{{cta}}

Packet 1: A Delivery Claim on a Split Shipment

Hypothetical example. Store order O-210 holds a $120 jacket and $60 shoes, with no tax, shipping fee or discount. Provider order B-210 has two captures: C-211 for the jacket and C-212 for the shoes.

The customer disputes $60 because the shoes never arrived. You only have delivery proof for the jacket.

Completed Working Packet

• Case index: D-210, item not received, $60 disputed. O-210 to B-210 to C-212 to shoes to parcel S-212.
• Finding: Parcel S-211 delivered the jacket. Parcel S-212 has no confirmed delivery for the shoes.
• Exhibits: (A) itemized order, (B) capture tying $60 to the shoes, (C) the shoes' carrier record, (D) dated messages about the missing parcel, (E) any completed refund or replacement record.
• Decision: Escalate the missing parcel to fulfillment. Resolve or accept the claim through the provider's workflow. Never submit the jacket's proof of delivery for the shoes.

If the shoes' delivery record turns up before the deadline, update the finding and attach it. Klarna expects proof of delivery as a file, not a link. Our guide to delivery confirmation covers which carrier proof holds up.

If a warehouse partner ships for you, set up 3PL chargeback evidence handoffs so parcel records come back in time.

How This Maps to the Afterpay Dispute API

For an eligible Afterpay Online not-received case, the Respond to Dispute endpoint accepts fields such as shippingDocumentation, shippingAddress, shippingDate, shippingCarrier and shippingTrackingNumber. Fill them with records for the disputed item only.

That call submits your challenge at once and moves the case to under_review. There is no save step and no second chance, so review the packet first.

Packet 2: A Partial Return With a Missing Credit

Hypothetical example. Store order O-320 has three items at $80, $70 and $50, captured for $200. The customer returned the $70 item. Warehouse return R-320 confirms receipt, and support approved it.

The customer says the credit is missing. Payment records show no completed provider refund yet.

Treat the $70 as the whole case, as you would for partial chargebacks on cards. The original delivery proof does not answer this claim. Neither does a warehouse receipt or an internal approval.

Completed Working Packet

• Case index: D-320, refund not processed, $70 affected. Kept items total $130.
• Finding: Receipt and approval are verified. A completed provider refund is not.
• Exhibits: (A) itemized order, (B) return authorization and warehouse receipt, (C) approval message, (D) provider refund record with its real status, (E) later confirmation or failure record.
• Response note: "The returned item is the $70 line on O-320. Return R-320 was received and approved. We have not yet confirmed a completed provider credit. Our payments team is checking it now."

Once the refund completes, save its reference, amount and order link. Then check the case again, because a completed refund does not always close it. Klarna, for example, starts an automatic chargeback if you accept a return and do not refund within 96 hours.

Refunding outside the case can also lead to a double refund chargeback if the provider later rules against you. See what to do when receiving a chargeback after a refund.

If an order-level promotion changes the refund amount, show the real split. An unexplained gap between item price and refund can start a new billing complaint.

Packet 3: A Customer Says the Invoice Amount Is Wrong

Hypothetical example. Store order O-430 has items worth $150. A $20 discount applies, shipping is $10 and tax is $12. The order total and the capture are both $152. The customer says the charge should be $132.

Show the math and the price the customer saw at checkout. Compare checkout, the confirmation email and the capture before you call it confusion. A product page screenshot taken today may not match the offer at purchase.

Hypothetical amounts: $150 − $20 + $10 + $12 = $152. Use your real purchase-time invoice.

Completed Working Packet

• Case index: D-430, incorrect amount. O-430 to B-430 to C-430. Record the disputed amount from the notice; do not assume the full $152.
• Finding: Checkout and confirmation both show $152, and the capture matches. The $132 expectation still needs a look. It may point to a second promo, an earlier credit or a side agreement.
• Exhibits: (A) purchase-time offer and promo terms, (B) itemized invoice, (C) order confirmation sent to the customer, (D) capture record, (E) the customer's message and your reply, (F) any related credit.
• Response note: "C-430 captured $152 for O-430. The attached invoice shows $150 in items, a $20 discount, $10 shipping and $12 tax."

Affirm lists the purchase-time price and an itemized invoice as evidence for incorrect and duplicate charges. Klarna's incorrect-amount form asks for proof the amount is right, such as why a discount did not apply.

Assemble a Packet a Reviewer Can Follow

Reviewers handle many cases a day. Make yours easy to check.

A saved attachment is not a submitted response. If an upload fails, confirm whether the provider received it before you send it again.

Reconcile the Decision With the Money

A submitted response is not a win. A case marked "won" does not prove the money moved. Track three checkpoints: response status, decision and settlement.

Klarna's acquirer settlement documentation shows why. Entries depend on the hold policy, and corrections are not the same as dispute outcomes. Afterpay's reporting adds a separate record per dispute, with the order ID, dispute ID and adjustment. Match each case to its own entries.

For partial outcomes, keep the disputed amount, any upheld part, returned principal, refunds and fees on separate lines. Never count a refund as recovered money. Our chargeback reconciliation guide walks through the full matching process.

Turn Every BNPL Case Into a Faster Next Response

Look back at the three packets. The delivery case needed parcel-to-item mapping. The return case needed a completed refund. The pricing case needed the offer as the customer saw it. Each gap is a data task to fix before the next dispute.

• Ecommerce owns the itemized order.
• Fulfillment owns parcel contents and returns.
• Support owns promises and complaints.
• Payments owns captures, refunds and case submissions.

Track four numbers by provider, route and reason: cases with a full order-to-case join, days lost waiting on records, on-time submissions and unreconciled outcomes. A strong result on delivery cases does not prove your return workflow is strong too.

Chargeflow Automation collects order, shipping and customer data for each dispute and submits the response for you. It backs that with a 100% submission rate and a 4X ROI guarantee. Its inquiry automation also handles pre-dispute inquiries on BNPL platforms such as Klarna and Afterpay.

Connect your Klarna, Afterpay, Affirm or Sezzle integration and stop building packets by hand.

{{cta}}

BNPL Dispute Evidence FAQ

What evidence do you need for a BNPL dispute?

BNPL dispute evidence depends on the dispute reason. For an item-not-received claim, send carrier proof of delivery for the disputed item. For a refund claim, send the return receipt and a completed refund record. For a wrong amount, send the purchase-time price and an itemized invoice. Each provider lists its own rules on the notice.

How long does a merchant have to respond to a BNPL dispute?

BNPL response windows vary by provider. Afterpay Online gives merchants 13 days, and Affirm US usually allows 15 days. Klarna's direct process allows 21 days, or 7 for unauthorized purchases. Klarna through Stripe adds a 21-day inquiry, then 12 days for evidence. Sezzle shows its timing on each case.

How long does an Afterpay dispute take?

An Afterpay dispute gives the merchant 13 days from notification to submit evidence. Afterpay then has 30 days from that submission to decide. If the merchant sends nothing in time, Afterpay closes the dispute in the customer's favor.

Can a customer dispute a Klarna charge with their bank?

A shopper can contact their bank about the card payment they made to Klarna, but that card payment is between the shopper and Klarna. Complaints about the goods reach the merchant through Klarna's own dispute process. That is why merchants send Klarna dispute evidence to Klarna, or to the processor that offers Klarna, not to a card issuer.

Do customers keep paying while a BNPL dispute is open?

Often they do not. Affirm says customers do not have to make payments while a dispute is open, and it withholds the disputed amount until the case ends. Klarna pauses outstanding repayments when a shopper files an inquiry. Merchants should expect that money to stay on hold until the provider decides.

Sources reviewed October 25, 2026. All orders, IDs and amounts in the packets are hypothetical. Provider rules change, so check the live case before you submit.