Related Questions
.png)
A merchant reports stable refund rates. Dispute volume rises anyway. For risk leaders, the instinct is to investigate fraud. The correct instinct is to investigate friction.
Refunds are a merchant-controlled metric. Merchants set the policy, control the processing speed, and decide when (or whether) to issue them. Disputes are a customer-controlled metric. They reflect what happens when customers run out of patience or options. When the two diverge, it almost always means the merchant is creating obstacles between customers and resolution.
Stable refunds with rising disputes is not a fraud signal. It is a friction signal.
Merchant monitoring programs routinely track refund rates as a proxy for customer satisfaction. This creates a structural blind spot. A merchant can issue refunds consistently while systematically delaying them, requiring excessive effort to obtain them, and using dispute filings as the operational trigger for processing them.
By the time dispute rates breach scheme thresholds (typically 1% for Visa and Mastercard), the friction has already been operating for weeks or months. The financial exposure (dispute fees, potential scheme fines, reputational risk with card networks) is already in the portfolio.
Early detection requires measuring friction before it converts into disputes. That means moving beyond refund rates and into the operational mechanics of how merchants actually resolve customer issues.
Access the full detection framework →
The complete guide provides a five-part assessment framework built from operational review of merchant dispute patterns:
The most diagnostic metric is not the refund rate. It is the dispute-to-refund ratio: what percentage of refunds are issued within 7 days of a dispute being filed?
If that number exceeds 10%, the merchant is using dispute filings as the refund processing trigger. Customers who ask for refunds and wait do not get them. Customers who escalate to disputes receive them immediately. This creates a self-reinforcing cycle where disputes become the most efficient resolution path, regardless of whether the underlying issue is legitimate.
Key insight: A 15-day refund processing window looks reasonable in a policy document. Against a 10-day dispute filing timeline, it means customers will systematically dispute before the refund arrives. Processing speed must be evaluated against dispute filing behavior, not just stated policy.
Customers file disputes when they cannot resolve issues through merchant channels. Support responsiveness is therefore a direct upstream variable for dispute volume.
The failure modes we see most often in merchant underwriting are not outright non-functional support teams. They are support teams that are functional for some issues but cannot process refunds, that respond within 48 hours when the issue is time-sensitive, or that direct customers through multiple handoffs without resolution authority.
Key insight: Email-only support in time-sensitive merchant categories (travel, events, subscriptions) creates structural dispute risk. If a customer needs to cancel an event ticket and cannot reach anyone in time, a dispute is not fraud. It is the only available action.
Delivery failures and shipping delays are among the most preventable dispute categories. They are also the ones where merchant behavior (notification practices, tracking provision, delivery failure resolution) determines whether a shipping problem becomes a dispute.
The pattern we see repeatedly in high-dispute-rate merchants is not unusually bad carrier performance. It is the absence of proactive delay notification. When merchants do not communicate delays, customers lose confidence that the order exists. By the time the product ships, the dispute has already been filed.
Key insight: Dispute rates for delayed orders without proactive notification are significantly higher than for delayed orders where customers receive a communication and revised timeline. The delay itself is less damaging than the silence.
Subscription and service merchants with complex cancellation processes face a specific dispute pattern: customers who tried to cancel, could not complete the process, were charged again, and disputed the charge.
This is not friendly fraud. It is the predictable outcome of a cancellation process that is harder to complete than a dispute filing. The FTC's negative option rule requires cancellation to be as simple as sign-up. Merchants who do not meet this standard face both regulatory exposure and dispute volume, and the two often arrive simultaneously.
Key insight: If the cancellation process requires a phone call during business hours, customers in different time zones are effectively locked in. Risk teams should test the cancellation process directly as part of merchant onboarding review, not rely on policy documentation alone.
The guide introduces three customer effort metrics that provide earlier warning than dispute rates:
These metrics can be derived from data that merchants already hold (support ticket logs, refund timestamps, dispute records) and do not require new instrumentation. They provide a structured view of friction that dispute rates and refund rates, analyzed separately, cannot produce.
Access the full detection framework →
The guide details the operational characteristics that distinguish low-friction from high-friction merchants:
The guide includes a detailed low-friction merchant profile with specific metrics: dispute rate 0.42%, average refund processing 3.2 business days, dispute-to-refund ratio 2.1%, and support interactions per resolution 1.4.
Access the full detection framework →
The guide identifies the highest-frequency errors in friction assessment:
Measuring refunds without measuring timing. A 2% refund rate with a 14-day average processing time is not the same risk profile as a 2% refund rate with a 3-day average. The rate is identical. The friction exposure is not.
Treating all disputes as fraud. A significant portion of dispute volume in most portfolios reflects friction rather than fraud. Risk teams that route all disputes to fraud investigation miss the operational signal entirely. Transaction monitoring that separates friction-driven disputes from fraud-driven disputes enables more accurate portfolio risk assessment.
Not testing the merchant experience. Document review does not surface friction. Testing the refund request process, contacting support with a time-sensitive issue, and attempting to cancel a subscription reveals what policies cannot. Mystery shopping as a standard component of the review process catches friction that documentation misses.
Accepting category-average performance. Some merchant categories have poor average performance across refund processing, support responsiveness, and cancellation ease. A merchant performing at category average in a high-friction category is still a high-friction merchant. Risk teams should set absolute thresholds, not relative ones.
This framework enables risk teams to:
The full guide includes step-by-step assessment protocols, data requests for each friction dimension, testing procedures (mystery shopping, support testing, cancellation process walkthroughs), merchant assessment checklists with quantified risk thresholds, and a customer effort metric calculation guide with worked examples.
The complete guide provides operational checklists, data request templates, testing scripts, and verification protocols for each of the five friction dimensions. It is designed for immediate implementation by underwriting and risk teams assessing e-commerce, subscription, and service merchants.
For acquirers, PayFacs, and marketplaces managing merchant portfolios, this resource provides the structured framework needed to distinguish merchants with genuine customer resolution capability from those whose metrics look acceptable while friction accumulates.
Read the full guide: How to Detect Customer Friction Before It Becomes a Dispute Spike →
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.png)
