Why Partnering With a Chargeback Prevention Provider Matters
A chargeback prevention provider matters to a partner because an accountable provider absorbs chargeback losses and commits to an approval-rate floor. A non-accountable vendor sells tools and leaves every dollar of risk with the merchant.
I've worked with merchants on cutting their chargeback rate, and the fastest fix was usually the billing descriptor. It beat whatever software the vendor pushed hardest.
By the end of this you'll have a three-question test for any provider, plus one question to ask per merchant.
Key takeaways
Vetting a provider for your merchant base? See our partner terms before you run the test on us.
What does a chargeback prevention provider do for a partner?
For a partner, a chargeback prevention provider keeps your merchants clear of monitoring programs by catching their disputes before they become chargebacks. A merchant who stays under the thresholds keeps processing, and you keep the account.
It works because the card networks will tell you a dispute is coming before it lands. Ethoca alerts carry that warning on Mastercard's side.
On Visa's side it comes through Verifi.
A provider's job is to do something useful with the warning before the window closes.
Where providers split is what happens when one of those calls goes wrong. An accountable provider puts its own money behind the outcome, and a tool vendor hands your merchant the bill.
That's the difference you're actually shopping for. Two providers can pull identical alerts from the same networks and still leave your merchant in a very different spot when a dispute slips through.
Why chargebacks are a partner problem, not a merchant one
When a merchant's chargeback rate climbs, the partner who onboarded them pays for it too. Whether you're a payment service provider, a payment facilitator, a gateway, or an agency, three things follow the merchant back to you:
- Your processor starts asking questions about the account.
- The card network puts that merchant in a monitoring program.
- The merchant churns, or gets shut off, and stops paying you.
Visa writes this into a program. Its Visa Acquirer Monitoring Program scores an acquirer on its whole portfolio. Above Standard starts at a 0.5% ratio, and Excessive at 0.7%.
Those numbers are far tighter than the per-merchant limit. So an acquirer under pressure sets a stricter cap of its own and pushes it onto the merchants in your book.
Your acquirer counts your whole book, and once it decides the problem is you, that's very hard to reverse.
How hard this hits depends on what you signed. A payment facilitator that underwrites merchant risk carries real liability, up to and including the losses on a merchant who disappears. A referral-only agency with no processing exposure mostly carries the churn.
So read your own exposure before you read the vendor list. If you underwrite, a provider's coverage gaps land on your balance sheet. If you refer, they land on your renewal rate.
The cost of reactive handling vs. proactive prevention
Fighting chargebacks after they file costs more per case than stopping them before they post, because the dispute fee is charged the moment the chargeback exists. Winning the case doesn't get that fee back.
Then there's the labor. A dispute response means pulling transaction records, matching evidence to the reason code, and writing the packet.
That's staff hours on every case.
An alert that auto-refunds under a set threshold closes the case with nobody touching it. Set that threshold where a refund costs less than a dispute response. Route everything above it to a person.
Merchants who try the refund half on its own find out that refunds don't replace alerts as a prevention plan.
In Chargeback.io's Dropship.io case study, switching to alerts cut the following costs over about 18 months:
Those figures belong to one merchant's Stripe volume. Read them as one result, and price your own case separately with our chargeback ROI calculator.
What a chargeback prevention provider actually does
Strip away the marketing and the daily work is matching, tying each alert to a real order fast enough to refund it. Get that wrong and nothing else in the product matters.
An alert arrives with four fields to match on:
- The transaction amount.
- The date of the charge.
- The billing descriptor.
- The bank identification number.
Tie those to an order correctly and the charge either auto-refunds under the merchant's threshold or routes to a person. Miss it and the alert expires unused.
This is where the billing descriptor earns its keep twice. A descriptor that reads as the store name plus a support number is easier for a provider to match.
It also lets the cardholder recognize the charge on their statement, which stops some disputes before any alert is needed. That second reason is why merchants who want to prevent chargebacks start there.
Descriptor hygiene is the cheapest piece of this work and the most skipped.
The accountability test: how to tell a partner from a vendor
A provider with skin in the outcome will put a chargeback guarantee, an approval-rate floor, and a named payer in writing. Three questions get you all three, and each answer changes what the next one is worth:
- Chargeback guarantee. Does the provider reimburse the merchant for approved orders that dispute anyway?
- Approval-rate SLA. Does it commit to a floor on the share of orders it will approve?
- Who eats the loss. When an approved transaction still disputes, whose money covers it?
Three yeses means a fully accountable partner, and three noes means a tool vendor. In between is a prevention-only provider that stops disputes well and still leaves the loss with the merchant.
That middle tier is the right buy when your merchants mainly need fewer chargebacks.
The sections below take the questions one at a time.
1. The chargeback guarantee check
A chargeback guarantee is a written promise to reimburse the merchant for approved card-not-present orders that turn out to be fraudulent. Riskified defines it as a provider paying for its own approval calls.
In a contract the word is binding. On a marketing page it means nothing.
So ask for three things in writing:
- The reimbursement window, in days.
- The evidence the merchant has to supply to claim it.
- The list of reason codes it covers.
2. The approval-rate SLA check
An approval-rate service-level agreement sets a floor on the share of orders the provider will approve. Without one, a provider can hit its guarantee by declining every order it isn't sure about.
A guarantee with no approval floor turns chargeback losses into lost sales. Declined good orders never show up in a chargeback rate, so the provider's numbers improve while the merchant loses revenue nobody is measuring.
3. The who-eats-the-loss check
On a fully accountable model the provider's own money covers the loss, and only on the chargebacks filed under the reason codes its contract names. Everywhere else the merchant pays, so ask them to point at the clause and name the entity whose money covers it.
The third answer also tells you what the first two were worth. A named payer means little when the guarantee's reason-code list is three items long.
Our own model is worth running the test on. According to Chargeback.io's own published rates, it bills per alert, $29 for Ethoca and $15 for Visa's programs. There's no monthly minimum and no reimbursement commitment attached.
That puts us in the middle tier. We prevent the dispute, and the merchant keeps the loss on anything we don't reach.
Put all three questions in front of every provider you shortlist and require a written answer to each.
Our partner terms are published, so compare them against whoever else is on your list.
Where an accountable partner model breaks down
A guarantee only covers the disputes the alert networks actually report. Anything the networks miss stays with the merchant, whatever the contract says.
Chargeback.io's own Dropship.io engagement documented three gaps where that happens:
- Tokenized wallets. Payments through Stripe Link, Google Pay, and Apple Pay were harder to tie back to a transaction.
- Issuers that skip the alert. Some banks filed a chargeback directly, with no alert first.
- Partial refunds. RDR doesn't apply to a charge that was already partly refunded.
Every dispute in one of those gaps still needed handling by hand.
So add a fourth question when you vet a provider for one merchant. Ask what share of that merchant's volume runs through tokenized wallets, because no guarantee and no approval floor will reach it.
A merchant selling mostly through Apple Pay and a merchant selling mostly on stored cards get very different value from the same contract. The second one has far more transactions a provider can actually match.
Price the guarantee against the share of volume it can actually reach, then plan for the rest.
Merchants comparing whole categories can start with our guide to evaluating chargeback protection tools.
How we sourced our data
The Dropship.io figures in this article come from one named, published customer case study. Every number belongs to that single merchant's Stripe volume over its own window. Read them as one merchant's result. The coverage gaps above come from the same engagement's notes.
FAQ
Is a chargeback guarantee the same as chargeback insurance?
A guarantee is the provider paying for card-not-present orders it approved itself. Insurance is a third party paying for losses it never approved.
Can a partner be liable for recommending a bad provider?
Contractual liability sits with the merchant who signed. Your real exposure is commercial, in churned accounts and an acquirer conversation about your portfolio.
Does an accountable provider ever decline a dispute?
Yes, routinely. Most guarantees pay out only on chargebacks filed under a fraud reason code, which leaves every non-fraud dispute with the merchant.
How is Ethoca different from Verifi, RDR, and CDRN?
Ethoca and Verifi are alert companies, one owned by Mastercard and one by Visa, so those two differ by card network. RDR and CDRN sit a level below as two programs Verifi runs.
