TouchSuite helps both traditional and high-risk merchants manage chargeback exposure through NoFraud-powered screening, analyst review of ambiguous orders, purchaser authentication options, and chargeback-management assistance. Your chargeback ratio is the count of chargebacks you receive in a calendar month divided by the count of transactions you processed that month, but Visa and Mastercard measure it differently, set different thresholds, and impose different consequences. Understanding which program applies to you, and why your disputes are happening in the first place, is the work that actually moves the number. No service eliminates chargebacks entirely; the goal is keeping your ratio below network thresholds while reducing the volume of avoidable disputes.
A chargeback is a forced reversal of a payment. A cardholder contacts their bank, disputes a charge, and the card network pulls the funds back from your account while the case is reviewed. Your chargeback ratio is the percentage of your transactions that result in those reversals over a given period, almost always a calendar month.
The basic formula looks like this:
Chargeback ratio = chargebacks received in the month ÷ transactions processed in the month × 100
So if you processed 1,000 transactions in March and received 10 chargebacks in March, your ratio is 1.0%.
That sounds simple. The complications come from two directions: the networks define the numerator and denominator differently from each other, and they use different thresholds to decide when your account is at risk.
Count matters as much as dollar value. A merchant doing low-volume, high-ticket sales can cross a threshold on count alone even when the dollar exposure is small. Conversely, a high-volume merchant with many small transactions can absorb more chargebacks in absolute terms before the ratio becomes a problem.
Visa replaced its older Visa Dispute Monitoring Program with the Visa Acquirer Monitoring Program (VAMP), which consolidates fraud and dispute monitoring into a single ratio. The VAMP ratio counts qualifying fraud plus disputes, divided by settled card-not-present transactions. Visa publishes current regional thresholds and effective dates on its fact sheet; review that document directly because thresholds and program rules change over time.
VAMP applies to card-not-present volume, which means e-commerce merchants carry proportionally more exposure. Card-present fraud is excluded from certain VAMP calculations, so a merchant running both in-person and online channels can have meaningfully different risk profiles across those two environments.
Mastercard's Excessive Chargeback Program (ECP) uses a count-based ratio: chargebacks received in a month divided by transactions processed in the prior month. That one-month lag in the denominator is different from Visa's approach and can produce a different ratio from the same underlying data. Mastercard also separates merchants into standard and excessive categories with distinct fee structures and consequences. Because Mastercard explicitly warns that standards change over time, always verify current thresholds in the published rules rather than relying on secondary sources.
A merchant at 0.85% on their own internal calculation might be fine under one program and flagged under another, depending on which card type generated the disputes, whether it was card-present or card-not-present, and which month's transaction count is used as the base. If your processor only shows you one ratio, ask which methodology it uses.
Most chargebacks trace back to a small number of failure patterns. Before reaching for a technology solution, diagnose which of these is driving your disputes.
1. True fraud (unauthorized transactions) Someone used stolen card credentials to buy from you. This is most common in card-not-present environments and is the target of fraud-screening tools. High rates usually signal weak authentication at checkout.
2. Friendly fraud (cardholder disputes a legitimate transaction) The transaction was authorized by the actual cardholder, who later disputes it, sometimes because they forgot the purchase, sometimes because the business descriptor was unrecognizable, and sometimes deliberately. Visa recommends clear and recognizable billing descriptors as one of the most direct ways to reduce these disputes.
3. Fulfillment failure Product never arrived, arrived damaged, or was materially different from the description. The dispute is legitimate and preventable. Tracking numbers, delivery confirmation, and clear product descriptions are your first line of defense.
4. Cancellation and refund friction A subscriber or customer couldn't easily cancel or get a refund, so they went to their bank instead. Visa specifically cites clear refund and cancellation policies as a prevention measure. If your cancellation process requires a phone call or a long wait, some customers will dispute rather than persist.
5. Unclear or confusing billing descriptors If your legal business name appears on the statement instead of your trading name, customers dispute charges they don't recognize. Descriptor management is a quick fix with measurable impact.
6. Merchant error Duplicate charges, wrong amounts, and processing failures generate disputes that are entirely within your control. A weekly reconciliation review catches these before they age into chargebacks.
Technology can surface the data, but a human review cadence is what converts that data into fewer disputes. Here is a practical weekly structure:
Monday: Pull the dispute queue. Review every new chargeback by reason code. Group them by category: fraud, friendly fraud, fulfillment, cancellation, or error. The distribution tells you where to direct effort.
Tuesday: Audit the previous week's fraud-screening flags. Review any orders that triggered holds or review queues. Look for patterns in declined-but-attempted orders, those are attempted fraudulent purchases that didn't become chargebacks, and they reveal attacker patterns.
Wednesday: Check your descriptor and contact information. Run a test purchase on your own checkout. Confirm the billing descriptor on your bank statement matches what customers expect. Confirm your customer-service phone number and email are visible on the statement and on your website.
Thursday: Review fulfillment and return data. Cross-reference orders with delivery confirmations. Flag any undelivered orders approaching your carrier's trace window. Process pending refunds before they age into disputes.
Friday: Compile your ratio estimate. Take chargebacks received this week divided by transactions processed this week (not the most precise monthly calculation, but a useful trend signal). If the weekly rate is trending up, investigate before month-end.
Visa identifies transaction monitoring and fulfillment records as core prevention practices. The routine above operationalizes those practices at the merchant level.
Screening happens before a transaction settles and is the most cost-effective point of intervention. A screening tool scores orders against signals like device fingerprint, IP geolocation, velocity patterns, email reputation, and billing-shipping address match. High-risk orders are flagged for review or declined before the card is charged, which means no chargeback is possible on a blocked order.
TouchSuite's fraud-prevention and chargeback-management solutions are powered by NoFraud and include analyst review of ambiguous orders and optional purchaser authentication. Analyst review is meaningful for merchants whose order mix includes a high proportion of borderline cases, situations where an automated system alone might block legitimate customers or pass through risky ones.
Several third-party networks allow processors and merchants to receive early notification when a cardholder initiates a dispute before the chargeback is formally filed. That window, sometimes 24 to 72 hours, gives you the opportunity to issue a refund and prevent the chargeback from being counted in your ratio. This is most useful for merchants who are already near a threshold and need to reduce count quickly.
When a chargeback is filed, you have a limited window to respond with compelling evidence. What constitutes compelling evidence depends on the reason code. For a fraud dispute, evidence of 3DS authentication, delivery confirmation to the billing address, and prior purchase history with the same credentials strengthens your case. For a "not as described" dispute, photographs, product specifications, and your return policy response documentation are more relevant.
Weak responses lose regardless of the underlying facts. If your team doesn't have a documented evidence template for each major reason code, that is a gap worth closing before your ratio becomes a problem.
Self-serve flat-rate processors like Square and Stripe are efficient for low-dispute businesses with predictable transaction patterns. They are less suited to merchants who operate in verticals with inherently higher dispute rates, subscription billing, digital goods, telemedicine, nutraceuticals, CBD and hemp, vape products, firearms and ammunition, or credit repair, among others.
TouchSuite states that it serves both traditional and high-risk merchants and names many of these verticals explicitly. High-risk merchant accounts typically involve specialized underwriting, closer monitoring, and sometimes rolling reserves, but they also come with processors who understand that a 0.5% chargeback rate in a subscription business is a different risk profile from the same rate at a retail shop.
If you are a high-risk merchant currently processing on a general-purpose platform, your greater risk is account termination without warning rather than a higher rate. A processor experienced in your vertical can structure the account, monitoring, and evidence workflows around the specific dispute patterns your business actually sees.
TouchSuite also connects merchants with working-capital options alongside payment processing, relevant context if chargeback reserves are constraining your cash flow while you work through a ratio remediation period.
That said, TouchSuite is not the right fit for every merchant. If your dispute volume is very low, your vertical is standard, and you want a completely self-serve setup with published flat-rate pricing, a simpler processor may serve you better. The question to answer first is whether your chargeback exposure is a routine operational matter or a structural risk that requires a processor built for it.
If your chargeback ratio is rising, your merchant account is in a network monitoring program, or you process in a high-risk vertical and want to understand your options, speak with a TouchSuite payment specialist or start a merchant-account application. Come prepared with your current ratio, the card types involved, and the reason codes you see most often, that information will make the conversation immediately actionable.
Contact our team today to discuss your payment processing needs — no pressure, just answers.
Talk to Us →