Chargeback Management for D2C Brands: A Complete Guide

You shipped the order. The customer got it. Six weeks later, the money vanishes from your account.

That is a chargeback. And most D2C brands handle them backwards. They wait for the dispute to land, scramble to upload a tracking number, lose anyway, and move on. Meanwhile the real damage builds quietly in a ratio they never look at.

Here is the part that stings. Card networks changed the rules in 2025 and 2026. The number Visa now scores you on is not the chargeback rate in your Shopify dashboard. It is a different number, and it is almost always higher.

This guide fixes that.

Key takeaways

• Your dashboard rate is not the network rate. Visa counts fraud alerts and disputes together. One bad order can be counted twice.
• Your processor fires you before Visa fines you. Most D2C brands never hit Visa’s fine threshold. That is not the risk. Losing card processing is.
• Deflection beats fighting. A dispute killed before it is filed carries no fee and no ratio hit at all.
• Fighting is a math problem. Below roughly a 16% win chance, fighting an average order loses you money.
• Evidence is captured at checkout, not after. If you are not storing IP and device ID today, you cannot use Visa’s best tool.
• Software does not fix a chargeback problem. Ownership does.

Quick answer: what is chargeback management?

Chargeback management is the system you use to stop disputes before they happen, fight only the ones you can win, and keep the ratio card networks track below the line that gets you dropped by your payment processor.

It has three jobs, in this order:

1. Prevent. Fix the reasons customers dispute in the first place.
2. Deflect. Kill disputes before they are formally filed.
3. Recover. Fight the small number you can actually win.

Most brands only do the third one. That is why they lose.

---

Part 1: How chargebacks actually work

What a chargeback is

A chargeback is a forced refund. The customer calls their bank instead of calling you. The bank pulls the money out of your account first and asks questions later.

Chargeback vs refund vs inquiry

These three get mixed up constantly. The difference decides how much it costs you.

	Refund	Inquiry	Chargeback
Who starts it	You	The card issuer	The card issuer
Money leaves right away	Yes	No	Yes
Fee charged	No	No	Yes
Counts against your ratio	No	No	Yes
Can you respond	Not needed	Yes	Yes, before a deadline

One important note. Amex and Discover still use inquiries. Visa and Mastercard do not, according to Stripe’s dispute documentation.

So if you sell mostly on Visa and Mastercard, there is no warning phase. The money is just gone.

The full dispute lifecycle

Most guides stop at “submit evidence.” There are five stages, and the last two can cost you more than the order.

Stage 1: The cardholder files. They call their bank. The bank decides if the claim has merit. Customers usually get 120 days from the purchase date. For pre orders or future dated services, the clock often starts on the delivery or event date instead.

Stage 2: The chargeback lands. The money and the fee leave your account immediately. You get a reason code and a deadline.

Stage 3: Representment. This is your response. You submit evidence to the issuing bank. You usually get 7 to 21 days depending on the network. Miss it and you lose automatically, even with perfect evidence.

Stage 4: The bank decides. This takes weeks. Complex cases can take up to 90 days. You wait.

Stage 5: Pre arbitration and arbitration. If the issuer disagrees with your evidence, they can push back again. Either side can escalate to the card network for a final ruling.

Here is the trap. Arbitration is expensive and most processors will not let you do it. Stripe states plainly that it does not support the arbitration phase. And if you contest a Visa or Mastercard compliance dispute, your processor collects an extra $500 network fee up front. You get it back only if you win.

For a D2C brand with an $80 AOV, arbitration is almost never worth it. Plan to win at representment or not at all.

---

Part 2: The real cost of a chargeback

The number most brands get wrong

Most brands think a chargeback costs the order value. It does not. It costs more than the order was ever worth.

Here is the full math on a single $80 order at a typical D2C cost structure.

Line item	Amount
Cost of goods	$36.00
Shipping and pick and pack	$9.00
Payment processing fee (2.9% + $0.30, not refunded)	$2.62
Ad spend to acquire the order	$22.00
Money already spent	$69.62
Chargeback fee	$15.00
Staff time to respond (30 min at $25/hour loaded)	$12.50
Total cash loss	$97.12

That $80 order just cost you $97.12. The customer also keeps the product.

The number nobody calculates

A clean order at this cost structure leaves you $10.38 in contribution.

$97.12 divided by $10.38 means you need about 9 more clean orders just to break even on a single $80 chargeback.

Run your own numbers. Start with your contribution margin and your true cost per order, then plug them into the table above. The result usually shocks people.

Fees and timeframes at a glance

Item	Typical figure
Chargeback fee (Shopify Payments, US)	$15
Chargeback fee (Stripe, US)	$15
Is the fee refunded if you win	With Stripe, no. Assume no.
Time to respond	7 to 21 days
Time for the bank to decide	Weeks, up to 90 days
Customer window to file	120 days, sometimes longer
Visa or Mastercard compliance dispute fee	$500, refunded only if you win
Dispute resolved by pre dispute tools	No fee, no ratio hit

That last row is the whole game. We come back to it.

---

Part 3: The rule change most D2C brands missed

This is the section that separates brands that survive from brands that get shut off.

VAMP replaced everything

In 2025, Visa folded its old fraud and dispute programs into one. It is called the Visa Acquirer Monitoring Program, or VAMP.

Straight from Visa’s own VAMP fact sheet:

VAMP Ratio = Count of [Fraud (TC40) + Disputes (TC15)] divided by Count of Settled Transactions (TC05)

Read that again. Fraud reports plus disputes.

What TC40 and TC15 actually mean

• TC40 is a fraud report. Your customer’s bank files one when a cardholder says a charge looks fraudulent. It happens even if no chargeback is ever filed. You usually never see it.
• TC15 is a dispute record. That is your actual chargeback.
• TC05 is a settled transaction. That is your order count.

The double count that kills brands

Here is the trap. Stripe’s documentation on card network monitoring programs confirms it directly.

A single fraudulent transaction can appear in both the TC40 report and the TC15 report. When that happens, Visa counts it twice.

Worked example: two very different numbers

A brand does 4,000 orders in a month.

• 12 fraud disputes (these hit TC40 and TC15, so they count as 24)
• 10 non fraud disputes (TC15 only, so they count as 10)
• 6 fraud alerts that never became disputes (TC40 only, so they count as 6)

What your dashboard shows: 22 chargebacks divided by 4,000 orders = 0.55%

What Visa scores: 40 divided by 4,000 orders = 1.00%

Same month. Same store. Nearly double the number.

Brands watch the 0.55% and feel safe. Their processor is watching the 1.00%.

Where the lines actually sit in 2026

Most articles on this topic still quote rules that no longer exist. Here is the current picture.

Threshold	Number	Who it applies to
Visa acquirer “Above Standard”	0.50% ratio	Your payment processor’s whole portfolio
Visa acquirer “Excessive”	0.70% ratio	Your payment processor’s whole portfolio
Visa “Excessive Merchant” (US, from 1 April 2026)	1.50% ratio and 1,500+ disputes and fraud per month	You, directly
Stripe internal non compliant flag	0.50% ratio and 5+ VAMP count	You, directly
Mastercard Excessive Chargeback Merchant	1.50% rate and 100+ chargebacks	You, directly
Mastercard High Excessive Chargeback Merchant	3.00% rate and 300+ chargebacks	You, directly
Industry standard for “excessive”	0.75% dispute activity	Everyone

The risk is not the fine. It is the offboarding.

Look closely at that table.

Most D2C brands will never hit Visa’s 1,500 monthly dispute minimum. So Visa will probably never fine you directly.

Your processor will fire you first.

Your acquirer gets measured at 0.50% and 0.70%. Your orders sit inside their pool. If you drag their ratio up, they do not write you a warning letter. They offboard you. Stripe flags accounts at just 0.50% and five VAMP events.

Losing card processing is a business ending event for a D2C brand. Fines are not the threat. Getting cut off is.

Mastercard fines you directly, and it escalates fast

Months over Mastercard ECM thresholds	Fine
1	$0
2 to 3	$1,000
4 to 6	$5,000
7 to 11	$25,000
12 to 18	$50,000
19+	$100,000

Above 300 chargebacks, Mastercard adds a $5 per chargeback issuer recovery assessment on top.

Mastercard only releases you after three straight months below the threshold. So a bad quarter costs you a good quarter to fix.

Part 4: The DEFEND Loop

Most chargeback advice is a pile of tips. Tips do not survive contact with a busy ops team.

You need a loop that runs every week. We call it DEFEND.

Letter	Step	The job
D	Deflect	Kill the dispute before it is filed
E	Evidence	Capture the data at checkout, not after
F	Fight	Only what you can actually win
E	Eliminate	Fix the root cause, not the symptom
N	Numbers	Track what the networks score, not what your dashboard shows
D	Dedicate	Give it a named owner

D: Deflect before it becomes a dispute

This is the highest ROI move in this entire guide, and almost nobody does it properly.

Visa’s fact sheet says the VAMP ratio excludes disputes resolved through pre dispute solutions.

Read that as a gift. If you kill the dispute before it is filed, it does not count against you at all. Stripe goes further: resolved disputes do not incur a dispute fee either.

No fee. No ratio hit. No staff time.

The four pre dispute tools

Tool	Owned by	What it does
Ethoca Alerts	Mastercard	Warns you a cardholder is about to dispute. You refund fast.
Verifi (Order Insight)	Visa	Pushes your order data into the cardholder’s banking app so they recognize the charge
Consumer Clarity	Mastercard	Same idea. Shows real merchant and purchase detail in the bank app.
Rapid Dispute Resolution (RDR)	Visa	Auto refunds qualifying disputes by rule before they enter the system

The move most brands miss

Stripe’s dispute prevention documentation confirms something powerful: if the extra order data sent through Order Insight is CE 3.0 eligible, the dispute can be blocked entirely.

Not refunded. Not fought. Blocked. The cardholder cannot file it.

That means your CE 3.0 data capture (covered next) does double duty. It wins disputes and it stops them from existing.

Why deflection wins on pure math

Take our brand from earlier. VAMP count of 40, ratio 1.00%. They turn on alerts and deflect 14 of those events.

• New VAMP count: 26
• New VAMP ratio: 0.65%

They cut their network ratio by 35% without winning a single dispute.

And on cost per event:

• Refund an $80 order through an alert: you lose $69.62 in sunk cost
• Lose a chargeback on the same order: you lose $97.12
• Deflection saves $27.50 per event, and it does not count against your ratio

Your deflection setup checklist

• Enroll in Verifi and Ethoca alerts through your processor
• Turn on Order Insight so your order data reaches the bank app
• Route alerts to a shared inbox with a 24 hour response SLA
• Auto refund any alert under a value threshold you set (many brands use 2x AOV)
• Log every alert so you can find the pattern later

E: Evidence captured at checkout, not after

Here is where brands lose disputes they should win. They go looking for evidence after the dispute lands. By then the data is gone.

What Visa Compelling Evidence 3.0 does

CE 3.0 is the single best tool a D2C brand has against friendly fraud. It lets you prove the cardholder has bought from you before, without a problem, on the same card.

But it only works if you captured the right data at the time of purchase.

The exact CE 3.0 requirements

From Stripe’s Visa CE 3.0 documentation, a dispute qualifies only when all of this is true:

• The dispute is a Visa dispute with network reason code 10.4
• You have at least two prior transactions from the same payment method that were never disputed
• Those transactions happened 120 to 364 days before the disputed one
• Those transactions were paid, undisputed, and not validation charges
• You can describe the product on the disputed order and on both prior orders
• The disputed order and both prior orders match on either two main evidence elements, or one main element plus one secondary element

The evidence elements

Main evidence elements	Secondary evidence elements
Customer purchase IP address	Shipping address
Customer device fingerprint or device ID	Customer email address
	Customer account ID

One catch. Device fingerprint and device ID together is not a valid pair. You need a real second signal.

Your checkout data checklist

• Store the purchase IP address on every order
• Store a device fingerprint or device ID on every order
• Push customers toward accounts, not guest checkout, so you have a stable account ID
• Keep email address and shipping address in a clean, queryable field
• Retain all of it for at least 400 days, because CE 3.0 looks back up to 364 days

If your store is not storing IP and device ID today, that is a one week engineering fix that pays for itself the first time you use it.

The bonus nobody talks about

Visa’s fact sheet says TC40 fraud that qualifies for CE 3.0 is excluded from the VAMP ratio.

So CE 3.0 does three things at once:

1. It wins friendly fraud disputes
2. It lowers your VAMP ratio
3. Paired with Order Insight, it can block the dispute entirely

F: Fight only what you can win

Fighting every dispute is not grit. It is a bad trade.

The real win rates

Stripe publishes win rates by evidence strength in its dispute best practices guide. These are sobering.

Evidence strength	Chance of winning
Very strong (5 dots)	60%
Strong (4 dots)	40%
Medium (3 dots)	25%
Weak (2 dots)	15%
Very weak (1 dot)	5%

Stripe says it plainly: “Even in the most favorable cases, it’s very difficult to overturn a disputed payment.”

The 16% Rule

Run the expected value. On an $80 order, with 30 minutes of staff time costing $12.50:

Win chance	Expected value of fighting
5%	negative $8.50
15%	negative $0.50
25%	positive $7.50
40%	positive $19.50
60%	positive $35.50

The break even point is a 15.6% win chance.

The 16% Rule: Fight the dispute only if your honest win chance is above 16%. Below that, accept it, refund it, and spend the time fixing the root cause instead.

What to fight and what to let go

Always fight	Usually fight	Usually accept	Never fight
CE 3.0 qualified disputes	Subscription disputes with a signed terms checkbox	True fraud with a genuinely stolen card	Visa code 10.5
Product not received with signed delivery proof	Product not as described with clear PDP photos	Any dispute with no tracking
Duplicate charge with two distinct orders	Credit not processed where you have the refund receipt	Orders below your labor cost

Visa does not accept evidence for reason code 10.5 at all. Do not waste the time.

---

E: Eliminate the root cause

Every chargeback is a symptom. Treat the disease.

Sort last quarter’s disputes into buckets and count them. The winner tells you what to fix.

Dispute reason	What is actually broken	The fix
“I don’t recognize this charge”	Your statement descriptor	Change it to your brand name plus a support number
“Item never arrived”	Delivery proof or carrier choice	Signature on high value orders, proactive delay emails
“Item not as described”	PDP copy or photography	Fix the listing, not the dispute
“I was charged after cancelling”	Cancellation flow is buried	One click cancel, renewal reminders 3 days out
“Duplicate charge”	Double click on checkout	Idempotency keys and button locking
“I wanted a refund and couldn’t get one”	Support response time	Refund SLA under 24 hours

The one that matters most

That last row is the big one. Most friendly fraud is a customer who gave up on your support team.

Fast, honest support is chargeback prevention. Slow support turns a $60 refund into a $97 chargeback plus a ratio hit.

If your support queue is backed up, that is not a service problem. It is a payments risk.

This is where chargebacks and returns management become the same job. A customer who cannot get a return processed will call their bank instead. Watch your customer support KPIs as leading indicators of your dispute rate, not as separate metrics.

Same story with fulfillment. Your “item never arrived” dispute rate is a direct output of your fulfillment model and your carrier mix.

---

N: Numbers the networks actually score

Stop reporting the wrong number.

Dispute rate vs dispute activity

Stripe’s guide on measuring disputes explains two calculations that look almost identical and mean different things.

• Dispute rate: disputes counted by the date of the original charge
• Dispute activity: disputes counted by the date of the dispute

Card network monitoring programs use dispute activity. If you are reporting dispute rate, you are reporting a number the networks do not use.

The five metrics to track every month

1. VAMP ratio = (TC40 fraud + TC15 disputes) divided by settled transactions
2. Dispute activity by month, not by charge date
3. Net win rate = disputes won divided by disputes fought
4. Deflection rate = alerts resolved before a dispute divided by total alerts
5. Cost per dispute = fee + COGS + shipping + CAC + labor

Your internal alarm levels

Do not wait for the network to tell you. Set your own lines.

VAMP ratio	Status	Action
Under 0.30%	Healthy	Monthly review
0.30% to 0.50%	Watch	Weekly review, turn on alerts if you have not
0.50% to 0.75%	Alarm	Your processor is now watching you. Deflect aggressively.
Above 0.75%	Danger	Assume offboarding risk. Escalate to leadership today.

Set the alarm at 0.5%, not 1%. That is where your processor starts paying attention.

Ask your processor for your VAMP metrics directly. Stripe surfaces them in a VAMP dashboard. If you cannot see the number the network sees, you are managing blind.

---

D: Dedicate an owner

Chargebacks fail as a side task. Every deadline is short. Every deadline is different. Nobody’s job description says “dispute response,” so it gets done at 5pm on a Friday, badly.

The two roles you actually need

Role	What they do	Time needed
Chargeback analyst	Triages alerts daily, assembles evidence packs, submits responses inside SLA, tags every dispute by reason code	Roughly 1 hour per 10 disputes, plus daily alert checks
Chargeback manager	Owns the ratio, runs the weekly root cause review, reports VAMP to leadership, decides fight or accept policy	4 to 6 hours a week

At 40 disputes a month, that is not a full time hire. But it is real work, and it has hard deadlines.

The operating rhythm

• Daily: Check Verifi and Ethoca alerts. 24 hour SLA. No exceptions.
• Daily: Respond to any dispute with under 5 days remaining.
• Weekly: Root cause tally. Which reason code is growing?
• Weekly: Ratio check against your alarm levels.
• Monthly: VAMP ratio and net win rate to leadership, with a trend line.

Write it down as an SOP. If it lives in someone’s head, it dies when they take a vacation. Our guide on building ecommerce SOPs for remote teams covers the format.

Part 5: Chargeback reason codes and what to do about each

The reason code tells you what evidence the bank wants. Send the wrong evidence and you lose even when you are right.

The four categories

Every code across every network falls into one of four buckets.

Category	What the customer is claiming
Fraud	“I did not make this purchase”
Quality	“I got it, but it was wrong, broken, or not what you said”
Clerical	“You charged me twice, or the wrong amount, or never gave me my refund”
Technical	“There was a processing error”

Reason code reference by network

These codes come from Stripe’s dispute categories documentation.

Dispute type	Visa	Mastercard	Amex	Discover
Fraudulent	10.4 (card absent), 10.3, 10.5	4837, 4863, 4849	F29, F24, FR2	7010, 4866
Product not received	13.1	4855	C08	4755
Product unacceptable	13.3, 13.4, 13.5	4853	C31, C32	(none)
Subscription canceled	13.2	4841	C28	4541
Credit not processed	13.6, 13.7	4860	C02, C04, C05	8002
Duplicate	12.6.1, 12.6.2	4834	P08, C14	4534, 4865
Unrecognized	(none)	6321, 4863	127, 176	(none)

The one code to memorize: Visa 10.4. That is card absent fraud. It is the most common D2C chargeback, and it is the only code eligible for CE 3.0. If you build your evidence system around 10.4, you have covered most of your exposure.

What evidence to send, by reason

Reason	Send this
Fraudulent (10.4)	CE 3.0 pack: two prior undisputed orders, matching IP or device ID plus one more element. Add tracking with delivery confirmation.
Product not received	Tracking number, carrier, ship date, delivery confirmation, signature if you have it, the shipping address the customer gave you
Product unacceptable	Product page screenshots, product photos, your return policy with the timestamp they accepted it, any support conversation
Subscription canceled	The signup record with the terms checkbox, all billing reminder emails sent, your cancellation policy, proof no cancellation request was received
Credit not processed	The refund receipt with date and amount, or proof the return never arrived
Duplicate	Two order records showing different items, dates, or shipping addresses
Unrecognized	Your statement descriptor, the order confirmation email, delivery proof, IP address

Keep the response short

Stripe is blunt about this. Card issuers manually review thousands of dispute responses a day. They will not read a long file.

• Lead with one clear paragraph stating why the claim is wrong
• Attach only evidence that matches the reason code
• Do not send your return policy for a “never arrived” dispute
• Redact long email threads down to the relevant lines

---

Part 6: Copy and paste evidence pack templates

These are starting points. Swap in your real details. Keep them under 200 words.

Template: Fraudulent (Visa 10.4) with CE 3.0

[Customer name] purchased [product] on [date] using the same card, IP address ([IP]), and device ID ([ID]) used for two prior orders on [date 1] and [date 2]. Neither prior order was disputed. The disputed order shipped on [date] to [address], the same address used on both prior orders, and was delivered on [date] per tracking number [number]. The transaction history shows an established, non fraudulent purchasing relationship with this cardholder.

Template: Product not received

[Customer name] ordered [product] on [date]. We shipped it on [date] via [carrier] to the address the customer provided at checkout: [address]. Tracking number [number] confirms delivery on [date] at [time]. Delivery confirmation is attached. The claim that the product was not received is not supported by the carrier record.

Template: Subscription canceled

[Customer name] subscribed on [date] and accepted our billing terms at checkout, shown in the attached signup record. We sent renewal reminders on [dates]. We received no cancellation request before the [date] charge. Our cancellation policy and the customer’s account activity log are attached. The charge was authorized under the terms the customer agreed to.

Template: Product unacceptable

[Customer name] ordered [product] on [date] and received it on [date]. The product page in effect at the time of purchase is attached and accurately describes the item, including [key spec]. The customer did not contact support before filing this dispute. Our return policy, which the customer accepted at checkout, allows returns within [X] days. We remain willing to accept a return.

Part 7: Tools, software, and what they actually fix

Every chargeback vendor will tell you their software fixes your problem. Here is the honest breakdown, tool neutral.

The four categories of chargeback tooling

Category	What it does	What it fixes	What it does not fix
Fraud screening	Scores orders before you ship	Stops real fraud entering	Nothing about friendly fraud
Alert networks (Verifi, Ethoca)	Warns you before a dispute is filed	Ratio and fee, directly	Root causes
Representment automation	Auto assembles and submits evidence	Staff time on responses	Your win rate ceiling
3D Secure	Authenticates the cardholder	Shifts fraud liability to the issuer	Adds checkout friction

The honest truth about software

Representment automation is the category most brands buy first. It is also the one with the smallest effect on your ratio.

Remember the math. All disputes count against your ratio, whether you win or lose them. Automating your responses does not lower your ratio by a single basis point. It just recovers a bit more revenue from disputes you already took the hit on.

Alert networks are the opposite. They cut the ratio directly, because deflected disputes are excluded from the VAMP count entirely.

If you buy one thing, buy alerts before you buy representment software.

What software cannot do

Software will not:

• Fix your statement descriptor
• Rewrite your product page
• Answer your support tickets in under 24 hours
• Capture device IDs at checkout
• Choose a carrier that gets signatures on high value orders
• Sit in a weekly meeting and decide what to change

Every one of those is an operations job. Tools help. Ownership wins.

Part 8: In-house vs software vs embedded team

This is the real decision. Here is the comparison nobody gives you honestly.

	In-house (side task)	SaaS software	Fully managed vendor	Embedded team
Who does the work	Whoever has time	Your team, faster	The vendor, on their terms	A dedicated team inside your ops
Typical cost	“Free” (it is not)	Monthly fee plus per dispute	Percent of recovered revenue	Fixed monthly team cost
Fixes the ratio	Rarely	Only if you buy alerts	Sometimes	Yes, it is the goal
Fixes root causes	No, no time	No	No, out of scope	Yes, same team runs support and ops
Meets the 24 hour alert SLA	No	Only if staffed	Yes	Yes
Reports VAMP to leadership	No	Data only, no narrative	Their metrics, not yours	Yes
Breaks when someone quits	Yes	Yes	No	No

The honest answer

Under 20 disputes a month: handle it in house, but write the SOP and set the alarm. Turn on alerts.

20 to 150 disputes a month: this is the dangerous zone. Too many to ignore, not enough to justify a full time analyst. This is where brands drift past 0.5% without noticing.

Above 150 disputes a month: you need a dedicated function. Full stop.

Why most brands get stuck

Most brands under $30M do not have a chargeback owner. It falls between support, finance, and ops. So it falls through.

Hiring a full time dispute analyst is hard to justify at 40 disputes a month. But leaving it unowned is how brands cross 0.75% and lose their processor.

That gap is exactly why brands work with AcquireX.

Part 9: How AcquireX runs chargeback management

We do not sell you software and walk away. We are not an agency running your disputes as a side project between client calls.

We build a dedicated, embedded team that owns the ratio the same way an in house hire would.

That team runs:

• Daily alert triage on Verifi and Ethoca inside a 24 hour SLA
• Evidence pack assembly against every dispute reason code, using the templates above
• CE 3.0 eligibility screening on every Visa 10.4 dispute
• Checkout data audits so IP, device ID, and account ID are actually being captured
• Weekly root cause reviews feeding back into support, catalog, and fulfillment
• Monthly VAMP ratio reporting to your leadership, with a trend line

Here is the difference that matters. Because we also run customer service, returns, and marketplace operations for the same brands, the root cause fix does not stop at a report. It gets executed by the same team.

A vendor tells you your “item not as described” disputes are up 40%. We rewrite the product page.

That is the difference between managing chargebacks and actually reducing them.

Your 30 day chargeback control plan

If you are starting from zero, do it in this order.

Week 1: See the real number

• Ask your processor for your VAMP ratio and dispute activity
• Pull 90 days of disputes into a sheet
• Tag each one by reason code
• Calculate your true cost per dispute using the table in Part 2

Week 2: Turn on deflection

• Enroll in Verifi and Ethoca alerts
• Turn on Order Insight
• Set an auto refund threshold
• Assign an owner with a 24 hour response SLA
• Fix your statement descriptor today. It is free and it works.

Week 3: Fix the data

• Start storing purchase IP on every order
• Start storing device fingerprint or device ID
• Confirm your data retention is over 400 days
• Push account creation at checkout

Week 4: Build the machine

• Write evidence pack templates for your top 3 dispute reasons
• Apply the 16% Rule to your response queue
• Set the 0.5% internal alarm
• Book a weekly 30 minute root cause review

Thirty days. No new software required for most of it.

If your dispute ratio is creeping and nobody owns it, talk to us. We will pull your real number first, before anyone talks about scope.

Glossary

Term	What it means
Chargeback	A forced refund initiated by the cardholder’s bank
Representment	Your response to a chargeback, with evidence
Pre arbitration	The issuer pushing back a second time after your response
Arbitration	The card network making a final ruling. Expensive. Most processors do not support it.
TC40	A fraud report filed by the issuer. Counts against you even with no chargeback.
TC15	A dispute record. Your actual chargeback.
TC05	A settled transaction. Your order count.
VAMP	Visa Acquirer Monitoring Program. The single program that replaced Visa’s old fraud and dispute programs.
VAMP ratio	(TC40 + TC15) divided by TC05
CE 3.0	Visa Compelling Evidence 3.0. Lets you beat friendly fraud with prior purchase history.
EFW	Early Fraud Warning. A heads up that an order was flagged as fraud.
RDR	Rapid Dispute Resolution. Visa’s auto refund tool.
ECM	Excessive Chargeback Merchant. Mastercard’s monitoring program.
Friendly fraud	A real customer disputing a real purchase. The biggest D2C category.
Liability shift	When 3D Secure moves fraud liability from you to the issuing bank

---

Frequently asked questions