Chargeback Ratio: How It Is Calculated and Why Two Merchants Get Two Numbers

A chargeback ratio is the disputes a merchant account received in a month divided by its sales, by count or by amount, against the same month's sales or the previous month's depending on who measures. Once a dispute posts, refunds and won representments do not remove it. Disputes lag sales by weeks, so a fall in volume raises the ratio while the count stays flat. Track it weekly per MID and confirm the formula and thresholds with your acquirer.

A chargeback ratio is the number of disputes a merchant account received in a month divided by the number of sales it settled, as a percentage or in basis points. It still gives different numbers for the same business, because whoever measures it chooses what counts as a dispute, whether to count transactions or dollars, and whether the sales in the denominator come from the same month or the month before. A refund issued after a dispute posts does not lower it, a dispute you win stays in it, and a fall in volume raises it while the dispute count stays flat. Thresholds are revised by the networks and quoted by your acquirer; none is stated here as a current rule.

The formula: disputes posted in a month over sales settled in a month

Every version of the ratio has three parts. The numerator is the disputes counted in the period: the chargebacks that posted to the acquirer during the calendar month, whatever the date of the sale they concern. The denominator is a month of sales, as a count of settled transactions or as their amount. The period decides which month supplies each side. Twelve disputes posted in September against 1,000 sales settled in September is 1.2%, or 120 basis points, a basis point being one hundredth of a percent.

• Posted date, not sale date. A dispute is counted in the month the issuer's chargeback reaches the acquirer; a July sale can put a dispute into September's numerator.
• Settled sales, not attempts. Declined authorizations are not sales. Refunds are credits and add nothing to the denominator.
• Per card brand. Visa disputes are measured against Visa sales, Mastercard chargebacks against Mastercard sales.

Count-based and amount-based: two readings of the same disputes

A count-based ratio divides disputes by sales; an amount-based ratio divides the dollars disputed by the dollars sold. The network dispute programs run on counts. Fraud programs measure the fraud that issuers report, which can exist without a chargeback, by amount in some programs and by count in others. The two readings diverge whenever ticket sizes are uneven. A store selling a $30 accessory and a $900 device takes one dispute on the device: a small count ratio, a large amount ratio. The acquirer's letter says which reading it acts on; the monitoring programs guide on this blog covers the count and ratio tests each program applies.

Same month or previous month: the denominator moves the number

The second source of disagreement is which month's sales divide the disputes. One convention divides the disputes posted in a month by the sales settled in the same month. The other divides them by the previous month's sales. Both are used, and they disagree whenever volume moves. A merchant settles 1,000 sales in August and 1,500 in September, and receives 15 disputes in September. Same-month: 15 over 1,500, or 1.0%. Previous-month: 15 over 1,000, or 1.5%. Same disputes, same sales, two numbers; shrink instead of grow and the readings swap. Two merchants comparing ratios are rarely comparing the same thing.

Why refunds and won disputes do not lower the ratio

A refund lowers the ratio only when it prevents the dispute. Once the issuer has filed the chargeback, it sits in that month's numerator and nothing removes it: a refund issued afterwards is a second credit to the cardholder, and a representment you win returns the sale amount but leaves the count where it was, because the programs count disputes received, not disputes lost. Refunds do not help the denominator either: they are credits, and some amount-based views subtract them from sales, which pushes the ratio up. The refunds that work come before the dispute exists: on the first complaint or cancellation request, and through pre-dispute alert services, paid per alert. Whether a case closed through an alert is recorded as a refund or still counted as a dispute depends on the program and on the acquirer's own ratio; ask before you pay for alerts.

How a fall in volume inflates a stable dispute count

Disputes arrive weeks after the sales they concern. So when volume falls, the denominator shrinks at once while the numerator keeps arriving from earlier months. A merchant receiving 20 disputes a month on 2,000 sales runs at 1.0%. It pauses its ads; the next month settles 800 sales while 20 disputes from earlier sales still land, and the ratio reads 2.5%. Under a previous-month denominator the same jump arrives a month later. The count test in the network programs protects a small MID that stays below the minimum number of disputes; a MID that shrinks but still exceeds the count has no such cover.

• A traffic pause. An ad account suspended, a seasonal dip, a stock-out: the disputes on the last strong month land in the weak one.
• A cap reduction or a hold. Sales fall after a review while disputes from before it continue. The monthly volume cap guide on this blog covers the cap itself.
• Sales migrated to a new MID. The disputes on the old sales stay on the old MID, whose denominator is now near zero. Keep a closing MID open and answering disputes; its ratio keeps rising after the last sale for as long as the dispute window on those sales runs.
• A billing model change. Ending a subscription plan stops renewals at once; cancellation disputes on the last cycles keep coming.

A weekly tracking routine, per MID

1. Each week, per MID and per card brand, export the sales count and amount settled month to date, and the disputes posted month to date with posting date, reason and original sale date.
2. Keep last month's sales count and amount in the same sheet, per brand, so both denominators are at hand.
3. Compute the month-to-date ratio both ways, over this month's sales and over last month's. Write the dispute count next to each ratio; the count test is half of every program rule.
4. Project the month: disputes so far divided by days elapsed, times the days in the month, and the same for sales.
5. Group the disputes by the month of the original sale. That shows your lag and how many disputes are still due from past sales before you cut traffic.
6. Write two dated lines on the sheet: the acquirer's internal threshold for this MID and the network line it quotes as current. Put your own action line well below both, and act when the month-to-date ratio has risen two weeks in a row, not when it reaches the line.
7. Keep the sheet per entity and archive it when a MID closes; the next underwriter asks for processing history.

The ratio on a fresh entity, and where IBOCore fits

The ratio belongs to a merchant account, so a new MID on a new entity starts at zero on both sides of the fraction. It is not a reset for the business: the traffic, the offer and the refund path that produced the disputes produce the same ratio on the new MID, and the monitoring programs guide on this blog explains what follows. Fix the disputes first, then add the file. IBOCore's part is the file. Each package is a US LLC or C-Corp incorporated in the director's home state, with its EIN; a nominee director who is a real, KYC-verified US resident, the IBO (Independent Business Operator), qualified in-house with a zero criminal record and a credit score of 650 or more, exclusive to one merchant and never used before; a business bank account at Bluebanc or Relay in the company's name with full operational access; and the complete director and business documentation. The director takes the acquirer's verification calls and compliance queries for the life of the package, and the documents show the director on the state filing and on the EIN letter. IBOCore does not sell chargeback management and does not give legal or tax advice; the ratio, the plan and the disputes behind it remain yours.

• One price: $999 setup, then $2,999 per month, for standard high-risk e-commerce, dropshipping, info-products, coaching, compliant health and wellness, SaaS, subscription and continuity, nutra and supplements, streaming, crypto-adjacent education, paid media and fitness memberships alike.
• The IBO package costs $999 setup, then $2,999 per month from 30 days after delivery, whatever the vertical or the billing model.
• Timing and terms: payment in USDT or USDC on ERC20 or TRC20, delivery the same day it confirms, then the acquirer's own 3 to 10 business days of onboarding, its timeline and not a promise of approval. Billing starts 30 days after delivery; a package idle for 30 days can be reclaimed, setup fee not refunded. No clawbacks if an acquirer terminates the MID, and no KYC, notary or travel on the merchant.

Questions merchants ask

Is the ratio measured per MID or across my whole business?

Per merchant account and per card brand, which is what the networks measure and the acquirer reports. An acquirer may also read a blended figure across the MIDs it holds for one entity. What does not happen is netting: a clean second MID does not dilute the first one's ratio, and disputes on a closed MID keep counting against it until the dispute window has run out.

Why does my processor dashboard show a different ratio from the acquirer's letter?

Because it is cut differently. Many dashboards group disputes by the date of the sale and net refunds out of volume; the programs count disputes by the date they posted, against gross settled sales, per brand, sometimes against the previous month. Add alerts or retrievals that one side counts and the other does not, and two honest figures diverge. Re-cut your export to the acquirer's formula and the numbers meet.

What counts in the numerator: chargebacks only, or retrievals and alerts too?

In the network programs, a dispute is generally counted once, in the month the first chargeback posts; later stages of the same case do not add a second count. Retrieval requests and inquiries are not disputes. Whether a case closed through a pre-dispute alert is treated as a refund or counted as a dispute varies by program. Fraud programs count issuer fraud reports or fraud-coded chargebacks, depending on the network. An acquirer's internal ratio may add any of these; the answer for your MID is in its letter or agreement.

Compliance touchpoints that survive audit

Clean setups disclose beneficial ownership, file BOI, use genuine IDs, and keep the IBO informed of website and descriptor changes. Processors re-scan for prohibited products, undisclosed aggregation, and transaction laundering. Violations land on MATCH and kill future MID applications.

• AML / CDD: customer due diligence on the merchant entity.
• PEP screening: politically exposed persons get enhanced review.
• OFAC / SDN: sanctions lists checked on owners and signers.
• Website compliance: refund policy, terms, pricing visible before checkout.

Compliance shortcuts that trigger MATCH

Fake guarantors, borrowed SSNs, cloaked websites, and third-party processing through your MID are the fastest paths to MATCH listings. Recovery requires legal work and years of delay. Disclose, document, and keep the IBO in the loop.

FAQ: quick answers

How fast can I get an IBO package on IBOCore?

Available inventory ships the same day after payment. You receive Articles, EIN letter, registered agent details, bank onboarding pack and signer contact through your merchant dashboard. Processor onboarding typically follows over the next one to two weeks.

Where can I look up payment-processing jargon?

Use the Resources glossary on IBOCore (/resources) for 580+ definitions: MID, chargeback ratio, MATCH, rolling reserve, MCC, RDR, KYB and high-risk vertical vocabulary.