Stripe Dispute Prevention: A Refund, Not a Chargeback

On Visa and Mastercard there is no warning shot. Those two networks retired the inquiry stage, so the first thing you hear about a cardholder's complaint is the chargeback itself: the money already pulled, the fee already charged, and a sales receipt in QuickBooks that is about to be unwound in a month you may have closed.

Except that is only true if you have not enrolled in dispute prevention. If you have, something else can happen first, and it produces a completely different record.

That is the part nobody writes about. Dispute prevention is sold as a fraud tool and discussed as a fraud tool, and every article about it counts disputes. But the three things it can do to a disputed charge produce three different outcomes in your books: one leaves your original sale untouched, one adds a refund, and the one you get without it removes the sale entirely. Same lost revenue in two of those cases, and an entirely different set of records.

If you want Stripe refunds, disputes and payouts landing in QuickBooks against the records they belong to, start a free trial.

What Stripe actually turned on

Dispute prevention is not a Stripe product in the sense that Radar is. It is Stripe's integration with two card-network programs, and Stripe names them plainly:

Stripe has integrations with dispute prevention products offered by Verifi (a Visa solution) and Ethoca (a Mastercard solution).

The split matters more than it first appears, because it is a split by network, not by feature. Verifi covers your Visa volume. Ethoca covers your Mastercard volume. There is no equivalent for Amex or Discover here, which is exactly where the inquiry stage still lives. The networks that give you a free warning do not offer this, and the networks that offer this give you no warning. The two mechanisms fill each other's gaps almost perfectly, and most businesses have neither.

Stripe lists what sits inside each one:

The Verifi solution includes Order Insights (OI) and Rapid Dispute Resolution (RDR), and Ethoca includes Ethoca Alerts.

So three named mechanisms, and they do genuinely different things. Reading them as one feature is the mistake that makes the accounting incomprehensible.

Order Insight is a data lookup. A cardholder does not recognise a charge, opens their banking app or calls the issuer, and the issuer's agent queries Stripe in real time. Stripe describes the effect: the agent "can send an API request to Stripe (a lookup) to provide detailed descriptions of the purchased items (such as product descriptions, quantity, shipping address, or IP address)". If the cardholder recognises the charge, they stop. No dispute is ever filed.

Stripe is careful to say this requires nothing from you: "Stripe automatically pulls any available data on a charge on your behalf and sends it to the issuer. Stripe uses the data that you provide at the time of the charge, and doesn't require you to build any integrations or maintain a real-time service."

Compelling Evidence 3.0 is a block. Riding on the same lookup, CE 3.0 answers with your history with that cardholder rather than the details of this one order. Stripe sets out the test precisely:

If at least two prior transactions exist with complete product descriptions that have matching IP addresses and at least one matching email address or customer delivery address, the issuer must block the dispute. As a result, the dispute is never filed and you don't incur any dispute fees or increases to your dispute rate.

"Must block" is the operative phrase. This is not persuasion. Where the data qualifies, Visa's rules take the decision away from the issuer.

RDR and Ethoca Alerts are rulesets that refund. This is the mechanism with an accounting consequence, and Stripe's own parenthesis is the whole story. On the dispute prevention overview, Stripe describes what you are configuring as rules "to automatically resolve (refund) specific disputes", and in the requirements section it says the onboarding "requires you to set up resolution rules through Radar to access dispute resolution, and define which transactions to refund".

Resolve means refund. Not "waive", not "absorb", not "close". Stripe hands the money back to the cardholder on your behalf, according to rules you wrote in advance, and the chargeback that was coming never opens.

The prices, and one of them is not what you would guess

Every one of these carries a fee, and the fees are on Stripe's pricing page rather than buried in the docs. Read this run:

Line	Fee
Dispute deflection lookups	Included
Visa resolution (RDR)	15.00 USD per dispute
Visa Compelling Evidence 3.0 block	15.00 USD per block
Mastercard resolution (Ethoca Alerts)	29.00 USD per dispute
Dispute received fee, for comparison	15.00 USD per dispute received

Three things fall out of that table, and only the first is obvious.

Deflection is free. Order Insight lookups cost nothing. A cardholder who recognises the charge and does not file is pure upside with no line item.

On Visa, resolution is a wash on fees. You pay 15.00 USD to resolve, and you avoid the 15.00 USD dispute received fee you would otherwise have paid. Stripe confirms both halves: resolved disputes "don't count towards your overall dispute rates" and "you don't pay a separate dispute received fee on these resolved disputes". The fee arithmetic nets to zero, and what you buy is the dispute rate and the record shape.

On Mastercard, resolution costs more than the fee it avoids. 29.00 USD to prevent a chargeback whose received fee is 15.00 USD. You are 14.00 USD worse off per resolution on fees alone, before counting the sale you refunded. Anyone modelling this as fee avoidance will conclude Ethoca Alerts is irrational, and they will be right about the fees and wrong about the reason. What 29.00 USD buys is the dispute rate. Stripe puts that benefit first for exactly this reason, saying resolved disputes help merchants "exit Mastercard's chargeback monitoring programs such as ECM, HECM and EFM by reducing dispute rates, and lowering fines". If you are near a monitoring threshold, 29.00 USD is cheap. If you are not, it is 29.00 USD.

The part that changes your books

Now the accounting, which is where these three mechanisms stop resembling each other.

A chargeback does not arrive in your Stripe balance as a chargeback. It arrives as an adjustment balance transaction, and an adjustment is not a record. It is a correction to one. That single fact is why a chargeback and a prevented dispute leave your books looking nothing alike, even when the same money is gone. The full journal-entry treatment of a chargeback is its own subject; what matters here is the shape.

Here is what each outcome writes.

Deflection: nothing. The cardholder recognised the charge and never filed. Your sales receipt stands. There is no fee line, because the lookup was free. This outcome is completely invisible in QuickBooks, which is worth saying out loud, because it means the mechanism with the best economics is the one you can never point at and count.

CE 3.0 block: nothing, plus a fee. The dispute was blocked before it existed. The sale stands, exactly as recorded. The only trace is 15.00 USD of Stripe fee on the day the block happened.

Resolution: a refund. The charge is refunded in full, and a refund is an ordinary, documented event that produces a Refund Receipt. Your original sale stays in place and the refund offsets it. Both events remain visible, on their own dates, with the customer attached to each.

Chargeback: a deletion. The adjustment reverses the original. In real-time sync the sales receipt is voided or removed. On a synced Stripe invoice, the linked payment is deleted and the invoice reopens as unpaid. In daily summary mode the deduction is folded into that day's summary and reduces that day's net deposit. The sale you booked stops existing in the form you booked it.

Side by side:

	Deflection	CE 3.0 block	Resolution (RDR / Ethoca)	Chargeback
Stripe fee	None	15.00 USD	15.00 or 29.00 USD	15.00 USD, non-refundable
The money	Kept	Kept	Refunded in full	Pulled by the network
Original sale record	Untouched	Untouched	Untouched	Reversed, removed, or netted
New record created	None	None	A refund	None
Counts toward dispute rate	No	No	No	Yes
Visible in QuickBooks	No	Fee only	Yes, as a refund	Yes, as an absence

Look at the last two rows together. The two columns that cost you the sale are Resolution and Chargeback, and they are opposites in your books. One adds a row. The other subtracts one.

Why the refund is the better record, and it is not close

Given that both outcomes cost you the same revenue, preferring one on bookkeeping grounds sounds like fussiness. It is not, for three reasons.

The date is right. An Ethoca alert or an RDR rule fires when the cardholder disputes, which is close to the original sale. A chargeback arrives whenever the network gets around to it, which can be months. A reversal that lands in September against a sale booked in June reaches back into a period you have closed, reviewed and possibly reported. A refund taken near the sale does not.

The audit trail survives. After a resolution you have two records: what you sold and what you gave back. After a chargeback you have an absence where a sale used to be, and an absence does not explain itself. Twelve months later, "why is this invoice open?" has a good answer in the first case and requires archaeology in the second.

The reopened invoice stops happening. The single most common support question about chargebacks is an invoice that reopens as unpaid after a customer's payment is disputed. That is correct behaviour, because your books now say the customer has not paid, and it still surprises people every time. A resolution never produces it. The invoice stays paid and a refund sits alongside it.

There is a fourth reason that only shows up later. If you contest a chargeback and win, the money comes back as a positive adjustment, and nothing re-posts the sale you lost. Someone has to notice the win and record the money by hand. A resolution has no won state, no return trip and no manual step, because you decided the outcome in advance.

Writing the ruleset is a bookkeeping decision

Stripe leaves the rules entirely to you, and gives one worked example of what a rule looks like: "resolve all potential fraud disputes under 10 USD". That threshold is doing more work than it appears.

The trap is that a resolution refunds disputes you might have won. Run the three cases on a 200.00 USD charge:

• You contest and win. You keep the 200.00 USD. You paid the 15.00 USD dispute received fee, which never comes back, and you got the 15.00 USD countered fee back on the win. Net cost: 15.00 USD.
• You contest and lose. You lose the 200.00 USD and the 15.00 USD received fee.
• RDR resolves it. You lose the 200.00 USD and pay 15.00 USD to resolve.

A resolution costs exactly what losing costs. So every dispute your ruleset catches that you would have won costs you the full sale, and every dispute it catches that you would have lost saves you nothing on fees and buys you a clean dispute rate and a better record.

That makes the threshold an estimate of your own win rate by charge size, which is not a fraud question at all. It is the same shape as the calculation behind early fraud warnings, where Stripe's published guidance is to refund at roughly the value of your dispute fee and stop well above it. Small charges are where contesting is not worth anyone's time, which is precisely why Stripe's own example rule sits at 10 USD.

Two constraints from Stripe belong in the rule design.

The first is a hard limit on what RDR can even see. Stripe states it directly:

Verifi doesn't currently support partial dispute resolution or disputes on refunded transactions. This means RDR only resolves disputes when the cardholder disputes the full amount of the original transaction and the transaction has not been refunded.

So an RDR resolution is always a full refund of the original charge. There is no partial case to model, and a charge you already partially refunded is outside the program entirely. That is convenient for the books and worth knowing before you assume otherwise.

The second is about timing. On Ethoca Alerts, Stripe warns: "The rules you set only apply to chargebacks initiated after enrollment. After you enroll, you might continue to receive notice of chargebacks initiated by cardholders before your enrollment." Expect a tail of old-style chargebacks for a while after you turn it on, and do not read them as the program failing.

If a dispute does get through, the mechanism after this one is Smart Disputes, which automates the evidence packet and charges 30 percent of the disputed amount only when you win. Stripe frames the two as complements: prevention reduces how many disputes you receive, Smart Disputes handles the ones that arrive.

What lands in QuickBooks

The honest boundary first, because it decides how much of this you should trust from anyone.

Nothing in Acodei's product documentation names dispute prevention, Verifi, Ethoca, Order Insight, Rapid Dispute Resolution or Compelling Evidence 3.0. There is no dispute-prevention-specific treatment, and any article telling you there is has invented it. What is documented is the general handling of the two events these mechanisms produce, and since a resolution is a refund and a block is nothing, that turns out to be enough to answer the question completely.

The refund path. Acodei detects whether a refund is full or partial by comparing the refund amount to the original charge amount, then creates a Refund Receipt against the customer, drawing from the holding account, with line items mirroring what was refunded. Because RDR resolves only full-amount disputes, a resolution takes the full-refund branch every time. On a resync of an already-booked refund the existing record is updated rather than duplicated, so re-running a date does not double the entry.

Two caveats travel with that. Refunds of invoice payments take their own branch, and partial refunds against an invoice carrying post-payment credit notes take another, so a resolution on a charge that paid a synced Stripe invoice is not identical to one on a standalone sale.

The chargeback path, for contrast. A dispute reaches your balance as an adjustment. Acodei imports adjustments but does not post a standalone QuickBooks transaction for them. It reverses or adjusts the original entry instead: voiding or removing the sales receipt or payment in real-time sync, folding the deduction into the day's summary in daily summary mode, and deleting the linked payment on a synced invoice so the invoice reopens as unpaid. If you later win, Acodei does not automatically re-post the won dispute as a new payment, so the returned money needs an entry from you.

The prevention fees. These are Stripe product fees rather than per-charge processing fees. Acodei's documentation covers that category directly: stripe_fee includes all Stripe product fees, not just processing, and non-transactional fees that are not tied to a specific charge are captured when they occur and posted through the Daily Balance Summary even on accounts that sync charges in real time. All of it posts against the "Stripe Fees - Acodei" product mapped during onboarding. So the practical instruction is the same one that applies to Radar and Billing fees, and it follows the same routing as every other non-transactional Stripe fee: open the daily balance summary for the date, not the individual sale, and expect the resolution and block fees to sit there with the rest.

One consequence worth planning for. If prevention works, your refund volume goes up and your chargeback volume goes down, and those two events move your monthly record count in opposite directions. A month with more refunds and fewer reversals is prevention working, not a sync problem. Reconcile against the Stripe balance rather than against last month's counts.

The short version

Dispute prevention is three mechanisms wearing one name, and only one of them touches your ledger. Deflection and CE 3.0 blocks leave your sale exactly as booked. Resolution refunds the charge, which produces a refund record next to the original sale instead of the deletion a chargeback would have caused. On Visa the fees are a wash; on Mastercard you pay 29.00 USD to avoid a 15.00 USD fee, and the dispute rate is the thing you are actually buying. Write the ruleset for the disputes you would not have contested, because a resolution costs the same as losing.

Ready to stop hand-keying the refunds and reversals? Start a free trial.

Frequently asked questions

What is Stripe dispute prevention?

It is Stripe's integration with two card-network programs: Verifi on Visa and Ethoca on Mastercard. Stripe describes the Verifi solution as including Order Insights and Rapid Dispute Resolution, and Ethoca as including Ethoca Alerts. Together they let you supply transaction data that helps a cardholder recognise a charge, block an eligible dispute before it is filed, or automatically refund disputes matching rules you set. You enrol from the Dispute settings in the Stripe Dashboard.

Does a prevented dispute show up in QuickBooks?

It depends which mechanism prevented it. A deflected dispute writes nothing at all, because no dispute and no refund happened. A Compelling Evidence 3.0 block also writes nothing beyond the Stripe fee for the block. A resolution under RDR or Ethoca Alerts refunds the charge, so it produces an ordinary refund record alongside the original sale.

How is a resolved dispute different from a chargeback in my books?

They cost the same revenue and produce opposite records. A resolution is a refund, so your original sale stays in place and a Refund Receipt offsets it, on a date near the sale. A chargeback arrives as an adjustment balance transaction, and Acodei's documented handling of adjustments reverses or removes the original record rather than posting a new one, often months later and sometimes inside a closed period.

What does Stripe charge for dispute prevention?

On Stripe's pricing page, dispute deflection lookups are listed as included, a Visa resolution is 15.00 USD per dispute, a Visa Compelling Evidence 3.0 block is 15.00 USD, and a Mastercard resolution is 29.00 USD. For comparison the dispute received fee is 15.00 USD. So a Visa resolution nets out against the fee it avoids and a Mastercard resolution does not.

Does a resolved dispute still count toward my dispute rate?

No. Stripe states that disputes resolved through the rules you set "don't count towards your overall dispute rates" and that "you don't pay a separate dispute received fee on these resolved disputes". For CE 3.0 blocks Stripe goes further: the dispute is never filed, so you incur no dispute fees and no increase to your dispute rate.

Can RDR partially refund a dispute?

No. Stripe states that "Verifi doesn't currently support partial dispute resolution or disputes on refunded transactions", which means RDR resolves a dispute only when the cardholder disputes the full amount of the original transaction and that transaction has not already been refunded. Every RDR resolution is therefore a full refund.

Where do the dispute prevention fees post?

They are Stripe product fees rather than fees attached to a specific charge. Acodei's documentation puts all Stripe product fees under the mapped "Stripe Fees - Acodei" product, and captures non-transactional fees through the Daily Balance Summary even on accounts syncing charges in real time. Look for them on the daily balance summary for the date Stripe charged them rather than on an individual sale.

Should I turn on dispute prevention if my dispute rate is low?

The fee arithmetic alone does not justify it, especially on Mastercard where a resolution costs 29.00 USD to avoid a 15.00 USD fee. The case is strongest if you are near a network monitoring threshold, since Stripe positions resolved disputes as a route out of programs like VAMP on Visa and ECM, HECM and EFM on Mastercard. Deflection through Order Insight is a separate question, because Stripe lists those lookups as included, so the enrolment costs you nothing on that mechanism.

Does dispute prevention replace responding to disputes?

No. It reduces how many disputes reach you, and anything that still arrives goes through the normal dispute process. Stripe frames Smart Disputes as the complement, automating evidence collection for eligible disputes that do come through, and charging its fee only on the ones you win.