Chargeback Risk Scorecard for eCommerce Stores
eCommerce stores sell almost entirely card-not-present, so every 'I didn't authorize this' and 'item never arrived' claim lands on you. Enter a few numbers from your store and payment dashboards to see your dispute ratio, your headroom under the 1.00% line, and which fixes matter most for an online checkout.
Your scorecard
Note: Visa's VAMP ratio counts fraud reports plus disputes, so your Visa ratio may be higher than the dispute-only ratio shown here.
Score breakdown by factor
Your full chargeback report
Worst-case estimate: assumes you lose the full average ticket on every dispute. It excludes the cost of goods shipped, shipping, and any card brand program fines.
Your prioritized fix list
Reduction rates are planning assumptions set by TouchSuite for prioritization, not measured industry statistics. Actual results vary.
Your controls already cover the basics. Focus on fast responses to disputes and tracking reason codes.
If you complete every fix above
Step-by-step setup notes
A specialist can walk through your dispute reports and the chargeback and fraud tools available for your setup. This scorecard is not a quote or an underwriting decision.
Why eCommerce stores carry more chargeback exposure
When a customer taps a card in a store, the chip read gives the merchant strong evidence. Online, there is no chip and no signature. Unless a transaction is authenticated through something like 3-D Secure, fraud disputes on online orders usually fall on the merchant. That is why the scorecard weighs your fraud tools so heavily.
Many eCommerce disputes are not criminal fraud. They are friendly fraud: a customer who doesn't recognize the charge, a package marked delivered that the buyer says never came, or a return the customer believes was refunded. A statement descriptor that shows your LLC's legal name instead of your store brand is one of the most common and easiest-to-fix causes.
Chargebacks also cost more than the order. You lose the sale, and often the product and shipping too. Many processors charge a per-chargeback fee, and some add retrieval, dispute-review, or 'high-risk' surcharges once your ratio climbs. Read your statement for these line items. They are where a rising ratio starts costing you money before any card brand program applies.
Getting accurate inputs from your eCommerce store
Pull chargebacks for the last 90 days from every place you accept cards: your Shopify, WooCommerce, BigCommerce, or Magento payment dashboard, any standalone gateway, and wallet payments like Apple Pay and Google Pay. Disputes split across two dashboards are easy to undercount.
Chargebacks lag the purchase. Cardholders often dispute weeks or months after the order, so December holiday orders can show up as January and February chargebacks. Use your average monthly transactions over the same 90 days as your chargebacks. If you enter a peak November or December month as the denominator, your ratio will look better than it is. In a slow month after the holidays, the ratio can spike even if nothing changed operationally.
For billing model, choose based on what most of your volume looks like. A subscription box or replenishment program with automatic rebills should not be entered as one-time, even if you also sell single orders. If you offer a free or discounted trial that converts to paid, choose that option. Trial conversions are a frequent source of 'I never agreed to this' disputes.
Worked example: a hypothetical eCommerce store
These numbers are hypothetical. Picture a Shopify apparel store doing $60,000 a month across 800 orders, so the average ticket is $75. It had 18 chargebacks in the last 90 days, which is 6 per month. That gives a ratio of 0.75%, in the caution zone. It is above the tool's 0.65% buffer but under the 1.00% Mastercard monitoring ratio. Headroom is 8 minus 6, so the store can absorb about 2 more chargebacks a month before reaching 1.00%.
The store shows its refund policy only in the footer, uses AVS/CVV but not 3-D Secure, has a descriptor with the brand name but no phone number, and sells one-time orders. The score works out to 43: - 25 ratio points - 6 for the refund policy - 5 for fraud tools - 4 for the descriptor - 0 for billing - 3 for the eCommerce baseline That lands in the Moderate band.
The gated report would put the cost at $115 per chargeback: $75 lost sale, $25 fee, and $15 handling. That totals about $8,280 a year, before product and shipping costs. It would then rank four fixes: 1. Pre-dispute alerts (15% assumed reduction) 2. 3-D Secure (10%) 3. A clearer descriptor (5%) 4. Refund policy at checkout (5%) Combined, that is about a 31% assumed reduction. The projected ratio is roughly 0.52%, the projected score is about 20 (Low), and projected savings are roughly $2,563 a year. The thresholds and reduction rates are planning assumptions, not card brand rules or measured results.
Estimates are based on published industry averages and are not a quote. Actual rates depend on card mix, ticket size, industry, and underwriting.
What a good result looks like for eCommerce stores
A healthy result for most online stores is a ratio below the 0.65% caution line, with enough headroom to absorb a bad shipping week or a holiday surge in disputes. A Low or Moderate band with your descriptor and refund-policy answers already at the lowest-risk option means your remaining exposure is mostly fraud and fulfillment.
Smaller stores should read the ratio carefully. At 150 orders a month, just 3 chargebacks in 90 days, or 1 per month, puts you at about 0.67%, already in the caution zone. Low volume makes the ratio jumpy. The fixes that prevent single disputes, like a clear descriptor, shipping-status emails, and refunding before a dispute is filed, matter more than for a large store.
Drop shippers and stores with long delivery windows should expect 'item not received' claims to drive the ratio. The scorecard can't see delivery times directly, but they show up in your chargeback count. If your result surprises you, unlock the full breakdown or talk to a payments specialist about alert programs and gateway settings for your platform.
Frequently asked questions
Most of my disputes say 'item not received' even though I have tracking. Which fix in the report helps with that?
Tracking helps you fight a dispute, but the cheaper win is preventing it. Send shipping and delivery emails that show your store name the way it appears on the statement. List your support contact in those emails. Pre-dispute alerts, when available on the card, let you refund an order before it becomes a chargeback. When you do respond to a dispute, include carrier delivery confirmation and the shipping address match.
Will turning on 3-D Secure hurt my checkout conversion?
It can add a step for some customers, though many authentications happen in the background. The tradeoff is that authenticated transactions can shift liability for certain fraud disputes away from you, depending on card brand rules. Ask your gateway or cart platform whether you can apply it selectively, such as only on high-ticket orders, and compare conversion before and after.
My chargebacks always jump in January. Should I wait until spring to use the scorecard?
No, but match your inputs. Enter chargebacks from the last 90 days and your average monthly orders over that same 90-day window. Don't use a single peak or slow month. January chargebacks often come from holiday orders, so a jump then is common. Watch whether the ratio settles back down by spring.
I sell a subscription box alongside one-time products. How should I answer the billing question?
Answer for the model that drives most of your recurring disputes. In most cases that means one of the subscription options, or free trial to paid if you use trials. Rebills are where 'I forgot I signed up' disputes come from. The report's reminder and easy-cancellation fix is built for that pattern.
My statement shows my LLC name, not my store name. Is that really worth changing?
For online stores it is often the cheapest fix on the list. A customer who sees an unfamiliar company name may dispute the charge instead of contacting you. Ask your processor to set a descriptor with your store brand and a support phone number or URL. The scorecard treats a legal or processor name as the highest-risk descriptor answer.
How this works: every assumption behind your score
These are the exact values the scorecard uses. Threshold values, cost figures, and fix reduction rates are assumptions, not card brand guarantees or measured statistics. Confirm current card brand rules and your actual fees with your processor.
| Assumption | Value used | Source / basis |
|---|