TrustLens Chargeback Speedometer: How to Read the Ratios Before Your Gateway Does

A chargeback ratio is not just a fraud metric. It is the number your payment processor and the card networks use to decide whether you are a merchant worth keeping. Cross a threshold and you enter a monitoring program. Stay in a monitoring program long enough and you face fines, rolling reserves, or account termination.

Most store owners only find out they have a ratio problem when the processor emails them. By that point the ratio has usually been elevated for at least one full calendar month, and the options are narrowing. TrustLens is designed to surface this signal before it reaches that stage — specifically through the Chargeback Ratio Speedometer on the Command Center dashboard.

This guide covers every threshold the speedometer tracks, how the ratio is actually calculated, what the three speedometer states mean in practice, and what you should do at each stage. All threshold values and state logic in this post are verified against the TrustLens plugin code (version 1.2.5).

Why chargeback ratios matter more than chargeback counts

Card networks and payment processors do not care how many chargebacks you have in absolute terms. They care what percentage of your transactions end in a dispute. A store processing 100 orders a month with 2 chargebacks has a 2.0% ratio. A store processing 10,000 orders with 50 chargebacks has a 0.5% ratio. The second store has 25 times as many chargebacks in absolute terms and is still in good standing. The first store is already over every major threshold and heading toward program enrollment.

This is the counterintuitive reality of chargeback risk: growth is partially self-protective. As your order volume rises, the same number of disputes represents a smaller ratio. But it also means that a stagnant or shrinking store is more vulnerable to ratio spikes from a small cluster of bad actors.

Card networks monitor this ratio at the calendar month level, per card brand. A Visa chargeback counts against your Visa ratio, not your Mastercard ratio. Each network has its own threshold and its own monitoring program, with its own consequences for merchants who enroll.

The five monitoring programs TrustLens tracks

TrustLens tracks five card-network monitoring programs. The threshold values below are the exact values used in the plugin code.

A few things worth noting about this table. First, Visa is shown as two programs (VDMP and VFMP) because that is the structure TrustLens uses internally — these labels correspond to the pre-2025 Visa program names. Visa consolidated these into VAMP in 2025, but TrustLens (as of v1.2.5) tracks them separately. In practice, the VFMP threshold of 0.65% is the tighter signal: a store can be below 0.90% and still be over 0.65% if its dispute pattern skews toward fraud-coded reason codes. Either way, the plugin will surface the “Approaching threshold” state if you are within 3 disputes of either line.

Second, Amex and Discover share the same threshold (1.00%) but are tracked independently. If you process meaningful volume on both brands, you need both ratios in good standing.

Third, these are the ratio thresholds. Visa VDMP also has a minimum transaction-count qualifier in its public program rules (100+ disputes per month for the standard tier). TrustLens applies the ratio threshold as the early-warning signal regardless of absolute dispute count, which is the right call for smaller stores — even if you never hit the absolute count qualifier, trending toward the ratio threshold is a warning worth heeding.

How TrustLens calculates your ratio

TrustLens calculates your chargeback ratio as disputes divided by card-transaction orders within a time window. Specifically, it counts WooCommerce orders that have been tagged as card-brand transactions (captured automatically for Stripe and WooPayments, or via the manual entry form for other gateways), then counts how many of those orders have a dispute event recorded in the same window.

The formula is simple:

Chargeback ratio = disputes in window ÷ card-transaction orders in window

Orders with status completed, processing, or refunded are counted as card orders when the card-brand metadata is present. This is the denominator. The numerator is dispute events (specifically dispute_created events) recorded in the same window.

There are two windows:

• Calendar month: from the first day of the current month through now. This is what drives the Free dashboard speedometer and what card networks actually use for monitoring programs.
• Trailing 30 days: a rolling window from 30 days ago through now. This is available in Pro alongside the calendar-month view and is useful for spotting trends that cross a month boundary.

The Free speedometer uses the calendar-month window. This is intentional — it matches how card networks compute their monitoring ratios, so the comparison is as accurate as possible.

What feeds the denominator

TrustLens tags orders with card-brand metadata at the point of payment for Stripe and WooPayments. For other gateways, you can record chargebacks manually via the order edit screen — TrustLens captures the card brand when you do this, so the per-brand breakdown in Pro stays accurate even for non-integrated gateways.

Only orders tagged as card transactions (the _trustlens_card_tx meta is set to 1) contribute to the denominator. Cash orders, BACS transfers, and other non-card payment methods do not count, which keeps the ratio meaningful. A 1% chargeback rate on card transactions is very different from a 1% rate across all orders including bank transfers.

Per-brand vs. blended

The Free speedometer shows a blended ratio: all card orders in the denominator, all disputes in the numerator, regardless of brand. The per-brand breakdown — separate ratios for Visa, Mastercard, Amex, and Discover — is a Pro feature available on the dedicated Chargeback Monitor page.

For the Free speedometer, TrustLens uses a conservative approximation: it evaluates the blended ratio against each network threshold and surfaces the one you are closest to crossing. This means the speedometer reflects your most urgent risk signal even without a Pro subscription, but it cannot tell you which brand is driving it.

Reading the three speedometer states

The TrustLens Chargeback Ratio speedometer uses three human-readable states. These are the exact labels from the plugin code.

Healthy

Your blended calendar-month ratio is comfortably below the nearest monitoring threshold. The exact distance varies — the speedometer does not show the gap in the Free tier — but Healthy means you are not within 3 disputes of crossing any network line.

Healthy is the normal operating state for most stores most of the time. It does not require action, but it does reward routine maintenance: understanding which customers account for most of your disputes, and whether any behavioral pattern is drifting upward.

Approaching threshold

Your blended ratio is close enough to a threshold that 3 or fewer additional disputes would cross it. The exact phrasing from the plugin: “Approaching threshold” fires when disputes_to_hit > 0 && disputes_to_hit <= 3 — meaning you are within 3 disputes of the nearest network monitoring line, but have not crossed it yet.

This is the state where action is most effective. The ratio has not crossed a threshold, which means no monitoring program enrollment has been triggered. You still have room to reduce your dispute exposure before the month closes.

The Pro Chargeback Monitor page shows the exact “N disputes of room” math and names the specific program you are approaching, which tells you whether it is a Visa VFMP issue, a Mastercard ECP issue, or something else. In Free, you see the state label but not the per-brand attribution.

Action needed

Your ratio has crossed at least one network monitoring threshold. The “Action needed” state in TrustLens corresponds to status === 'danger' in the underlying data — meaning your current calendar-month blended ratio is at or above one of the five threshold values.

This does not automatically mean you have been enrolled in a monitoring program. Enrollment also depends on your absolute dispute count (Visa VDMP, for example, has both a ratio and a volume qualifier). But it does mean your ratio is in the zone where enrollment can happen, and it means your processor has almost certainly already flagged the month.

What to do when the speedometer reads Healthy

Healthy is not a reason to stop paying attention. It is a reason to understand your baseline before something changes it.

The most useful thing you can do during a Healthy period is look at the customers behind your disputes. TrustLens tracks per-customer dispute counts in every trust profile. A store with a 0.3% blended ratio might have 80% of that ratio concentrated in five customers — customers who have already been scored Risk or Critical and who you could block at checkout before they file another dispute.

A second useful habit is checking whether your dispute pattern correlates with any promotional activity. Stores that run heavy discount campaigns or first-order coupons often see dispute spikes in the weeks after — customers who bought at a discount, received the goods, and then filed chargebacks anyway. If your ratio ticks up every time you run a major sale, that is a signal worth acting on before the next one. For context on how behavioral signals feed into the trust scoring that drives those early warnings, see how TrustLens scores a WooCommerce customer.

What to do when it reads Approaching threshold

Approaching threshold means you have a narrow window to prevent the month from ending over a monitoring line. The window is defined in disputes, not days: you are within 3 disputes of crossing. Whether that is two days of exposure or two weeks depends on your dispute frequency.

The first step is identifying who is filing disputes. Go to TrustLens → Customers, sort by total disputes descending, and look at the top rows. Are these customers still active? Are they in the Risk or Critical segment? If so, blocking them at checkout prevents further orders from becoming further disputes.

The second step is reviewing any open disputes in your payment processor. Disputes that are filed but not yet resolved may close in your favour — if they do, they typically do not count against your final monthly ratio depending on how your processor reports them. Responding promptly to open disputes matters here. For a detailed guide to assembling dispute evidence, see the TrustLens Dispute Evidence Report guide.

The third step is operational: if you are running a promotion or coupon campaign, consider pausing it until the month closes. The dispute exposure from a discounted purchase is not worth the ratio risk when you are already 2–3 disputes from a monitoring threshold.

1. Identify the customers behind recent disputes

   TrustLens → Customers, sort by Total Disputes descending. Focus on customers who have filed in the current calendar month. Check their segment and whether they are still placing orders.

2. Block high-risk customers at checkout

   Customers in the Risk or Critical segment with a dispute on record are worth blocking before they file another one. TrustLens checkout enforcement works on both Classic and Blocks checkout. Blocking does not remove a prior dispute, but it prevents another one from this customer this month.

3. Respond to open disputes in your processor portal

   Active disputes that you win may close before month-end. Even if the timing is uncertain, submitting evidence is the right move. Use the TrustLens Dispute Evidence Report (Pro) for a print-ready behavioral summary, or compile evidence manually for smaller gateways.

4. Pause active promotions if possible

   New orders placed this month can become this month’s disputes if the customer files within the calendar window. If you are 1–2 disputes from a threshold and mid-campaign, evaluate whether the revenue is worth the ratio risk.

5. Upgrade to Pro for the exact per-brand breakdown

   The Free speedometer shows you are approaching a threshold but does not say which brand is driving it. Pro’s Chargeback Monitor page names the specific program (Visa VFMP, Mastercard ECP, etc.) and shows exactly how many disputes separate you from it. This information changes what you do next — a VFMP issue requires a different response than a Mastercard ECP issue.

What to do when it reads Action needed

Action needed means your blended ratio has crossed at least one network threshold for the current calendar month. At this point, some of the month-end risk may already be locked in — you cannot un-file a dispute that happened on the 5th. But there are still things you can do to limit the damage and to prevent next month from following the same trajectory.

Immediate actions

Block every customer in your Risk and Critical segments who has placed an order this month. This prevents any in-flight orders from becoming in-flight disputes. TrustLens bulk actions (Customers → select segment → Bulk Block) let you do this across the entire segment in a few clicks. Understand the risk: some of these customers may be false positives, particularly newer ones who have not accumulated enough order history. Use your judgment, and remember that you can unblock anyone at any time.

Contact your payment processor proactively. Processors generally respond better to merchants who self-report and present a remediation plan than to merchants who appear unaware of their ratio until the processor raises it. Reaching out first — with evidence that you are tracking the issue and taking action — is almost always better than waiting for the outreach to come the other direction.

Review the dispute reasons. If the disputes are concentrated in a specific reason code (item not received, not as described, unauthorized), that tells you something about the root cause. Item-not-received disputes often point to shipping or delivery issues. Unauthorized disputes often point to card-testing residue — customers whose payment details were compromised in an attack that ran through your checkout. Unauthorized disputes in particular are worth cross-referencing with TrustLens Card-Testing Defense logs to check whether there was an attack in the relevant period.

Next-month planning

Even if this month ends over a threshold, next month does not have to. The ratio resets on the first of the month. Your goal is to enter the new month with a cleaner customer base, better dispute-response coverage, and a clearer view of which orders are likely to generate disputes.

TrustLens Automation Rules (Pro) can do some of this work automatically: rules that hold orders from Risk-segment customers for manual review, or that fire a webhook to your support team when a dispute is recorded, reduce the reaction time from days to minutes. For an overview of how automation rules work in practice, see how TrustLens automation rules work.

Free vs Pro: what the speedometer gives you at each tier

The Chargeback Ratio Speedometer on the Free dashboard gives you a blended calendar-month ratio, a colored status dot, and one of three human-readable state labels. This is the core signal, and it is available to every TrustLens user at no cost.

The most operationally significant Pro feature is the daily email alert. By default, TrustLens Pro sends an alert when any card brand reaches 70% of its network threshold (configurable from 50–100%). This means you get notified before you reach the “Approaching threshold” state — with enough lead time to act. The alert fires once per brand per calendar month, so there is no risk of being flooded with notifications during a bad stretch.

The second most useful Pro feature for ratio management is the per-brand breakdown. When the blended speedometer reads Approaching or Action needed, knowing whether it is your Visa ratio or your Mastercard ratio that is driving the issue changes your response entirely. Visa disputes are often friendly-fraud or item-not-received complaints that respond to proactive communication. Mastercard disputes can skew toward unauthorized and require a different set of remediation actions.

Frequently asked questions

Does a chargeback from a Visa card count against my Mastercard ratio?

No. TrustLens captures the card brand on each paid order and counts disputes only against the ratio for the matching brand. A Visa dispute increments your Visa dispute count and is compared against the Visa VDMP and VFMP thresholds. It does not affect your Mastercard ECP calculation.

Does TrustLens automatically block customers when Action needed fires?

No. The free version of TrustLens never auto-blocks. The “Action needed” state is a dashboard signal — it tells you the threshold has been crossed and that you should act, but no blocking or enforcement happens automatically without your input. TrustLens Pro can optionally auto-block after N lost disputes (configurable in settings), but this is off by default and requires explicit configuration.

My ratio is at 0.00% but the speedometer shows “No card orders yet” — why?

The speedometer requires card-brand metadata on your orders to function. If none of your recent orders have been tagged as card transactions, the denominator is zero and the ratio is undefined rather than zero. For Stripe and WooPayments stores, this metadata is captured automatically on new orders. For existing historical orders, run Historical Sync from TrustLens → Dashboard. The speedometer populates as soon as qualifying orders are present.

Can I see last month’s ratio?

On the Free dashboard, you see only the current calendar month. TrustLens Pro includes a 12-month trend chart on the Chargeback Monitor page that shows your blended ratio for each of the past twelve months. This is useful for identifying whether a current elevated ratio is a one-off event or part of a worsening trend.

What is the warn threshold in Pro and how does it interact with the speedometer states?

The warn threshold in TrustLens Pro (default 70%, adjustable from 50–100%) is the trigger for daily email alerts. When any brand’s ratio reaches 70% of its network threshold, the alert fires. This is a separate signal from the speedometer states — it is designed to give you an earlier heads-up than the “Approaching threshold” state, which fires when you are within 3 disputes of the line regardless of percentage. A store with high order volume might have a 70% ratio alert fire weeks before it enters “Approaching threshold” territory. A store with lower order volume might see the reverse. Both signals are worth watching.

Does TrustLens track Visa VDMP and Visa VFMP separately?

Yes, as of TrustLens version 1.2.5. TrustLens tracks both historical Visa monitoring programs as distinct thresholds: VDMP at 0.90% and VFMP at 0.65%. In the Free speedometer, both are evaluated against the blended ratio, and the one you are closest to is used to determine the speedometer state. In the Pro Chargeback Monitor, both appear as separate progress bars. Note that Visa consolidated VDMP and VFMP into a single program (VAMP) in 2025 — TrustLens continues to use the legacy labels and thresholds in its current version, which still serves as a meaningful early-warning signal even if the program branding has changed.

Getting the most out of the speedometer

The Chargeback Ratio Speedometer is not a fire alarm. It is a pressure gauge — one that gives you a reading before the pressure becomes a problem, if you check it regularly. The most effective use is routine: open the TrustLens dashboard at the start of each week, note the state, and spend five minutes on the customer list if it is anything other than Healthy.

Stores that manage their chargeback ratio well are not necessarily the ones with the lowest absolute dispute counts. They are the ones that understand the denominator as well as the numerator — that a busy, high-volume month full of completed orders is a ratio-protective event, and that a slow month with even a handful of disputes is the moment to pay attention.

If you are not yet tracking dispute activity by customer, the TrustLens plugin page has the full feature overview and installation instructions. The speedometer, the customer trust profiles, and the chargeback tracking module are all included in the free version.