Buy now, pay later (BNPL) can lift conversion, especially for higher-ticket carts. But it also changes who your customer thinks they are paying, how refunds get routed, and what happens when the buyer files a dispute.
If you are adding BNPL to checkout or already running it, the practical question is simple: what happens when something goes wrong, and how do you keep your dispute rate, refund flow, and compliance risk under control?
In this guide, I will break down how BNPL disputes and refunds typically work, what the CFPB said about applying parts of Regulation Z to certain BNPL accounts, and the merchant-side setup choices that reduce chargebacks without killing conversion.
A BNPL dispute is a complaint the buyer files with the BNPL provider about the underlying purchase, the plan, or the merchant performance. A credit card chargeback is a network-driven dispute initiated through the cardholder's issuer.
In many BNPL setups, you can still end up dealing with a chargeback even if the customer started inside the BNPL app, because the BNPL provider may have funded the purchase with a virtual card and then mapped the consumer experience to its own dispute process.
Merchant takeaway: treat BNPL as a second dispute intake channel, not a replacement for card network disputes.
Most BNPL programs sit in one of two rails:
With provider-funded card rails, your processor's chargeback rules still apply because the transaction is on card rails. With provider-settled rails, the provider may handle most disputes contractually, but you still have card network exposure if the provider itself used a card instrument upstream.
Practical steps:
In its interpretive rule on "Use of Digital User Accounts to Access Buy Now, Pay Later Loans," the CFPB said certain BNPL lenders that issue digital user accounts are "creditors" subject to Subpart B of Regulation Z, including provisions governing periodic statements and billing disputes. (That interpretive rule is commonly discussed as applying "credit card-style" protections to covered BNPL accounts.)
Separately, the CFPB later stated it would not prioritize enforcement actions taken on the basis of that Regulation Z interpretive rule, citing 89 Fed. Reg. 47,068 (May 31, 2024).
Merchant takeaway: regardless of shifting enforcement posture, expect BNPL providers to keep building dispute workflows that look more like card billing disputes, meaning you should be ready for structured evidence requests, timelines, and temporary payment pauses.
The fastest way to lose a BNPL dispute is to treat it like a vague customer service ticket. Providers and issuers want time-stamped proof.
Build an evidence packet template you can produce in under an hour:
If you sell digital goods, add:
Refund risk is higher with BNPL because there are more entities that can initiate money movement.
Common failure modes:
Best practice is to route refunds through the same path the original payment took:
Operational controls that help:
Your BNPL provider will handle its own loan disclosures, but merchants still control the product-side terms that drive disputes.
The highest-impact items to make explicit before purchase:
A useful mental model is the FTC's focus in negative option cases: clear and conspicuous disclosure of material terms, express informed consent, and simple cancellation mechanisms.
Even if you do not sell a subscription, BNPL buyers are more likely to feel "locked in" because they are still paying after a return goes wrong. That feeling turns into disputes.
They can be, depending on your vertical.
Reasons BNPL can raise dispute volume:
Reasons BNPL can lower chargebacks:
The right approach is measurement, not guessing.
| Metric | Why it matters | How to measure |
|---|---|---|
| BNPL share of orders | Context for risk | % of paid orders using BNPL |
| BNPL dispute rate | Early warning | disputes / BNPL orders |
| Card chargeback rate (overall) | Network thresholds | chargebacks / total transactions |
| Refund time to completion | Friction driver | days from request to completed refund |
| "Item not received" volume | Shipping exposure | INR cases / shipped orders |
BNPL providers have different risk appetites, but a few patterns show up:
If you operate in a higher-risk vertical, do not assume BNPL will be approved just because standard card processing works for you. Some providers restrict underwriting, MCCs, or refund timelines.
Start with fixes that improve customer clarity instead of adding friction.
Then add targeted controls for risky orders:
Most merchants sign BNPL terms without aligning them to how their store actually works.
Key items to confirm in writing:
If the provider funds via card rails, also confirm how virtual card chargebacks will appear in your processor portal so your ops team does not miss them.
If you sell a continuity program, membership, or any offer where the buyer can be charged again unless they cancel, your dispute risk rises.
The FTC has repeatedly emphasized three themes in negative option enforcement: disclose material terms clearly, obtain express informed consent, and provide simple cancellation mechanisms.
Merchant takeaway: your best dispute prevention investment for BNPL plus subscriptions is not another fraud tool. It is a cancellation flow your customers can actually use.
BNPL itself is not a processor, but it can add operational strain if your acquiring setup is already brittle.
If you are dealing with higher dispute volume, higher tickets, or more complex refund flows, you typically want:
A good place to start is our guide to chargeback time limits by network:
And if you are evaluating fraud controls that help before disputes happen, see our guide to 3D Secure 2:
For pricing and checkout policy decisions, our surcharging rules guide is also relevant:
Often yes, but the path depends on how the BNPL provider funded the purchase. If it was funded via card rails, card network chargeback rules can still apply alongside the provider's own dispute process.
Yes. That is why you should keep refund IDs and timestamps, and avoid issuing refunds outside the original payment path unless you have a documented exception.
Not automatically. Start by adding targeted controls for first-time buyers, high ticket sizes, or high-risk SKUs, then measure dispute rate by cohort.
Sometimes. You may be able to negotiate pricing based on volume, average order value, and refund or dispute performance.
Letting support treat it as a normal card transaction. BNPL adds a second set of case IDs, timelines, and refund workflows, so you need a tighter ops process.
You can apply for a merchant account through Easy Pay Direct or another processor that fits your model. Other options worth a look: