Could the fraud controls protecting your merchants be costing them more revenue than the fraud itself?
Every software provider (ISV) with embedded payments recognizes the tension between risk and revenue: tighten risk controls and introduce more friction or loosen them and accept more exposure to allow transactions through. That tension is sometimes framed as payment fraud versus conversion, a dial to turn in one direction or the other depending on how much risk the merchant can absorb.
But in practice, the dial metaphor is the problem. The costs on the over-cautious end rarely appear where anyone is looking for them.
Chargebacks are visible: they appear on statements, trigger processor notifications, require merchant action, and generate measurable fees. But false declines are invisible: a declined legitimate customer simply leaves, and the merchant never knows the sale existed. The result is that fraud budgets tend to concentrate heavily on chargeback mitigation, even though chargebacks are only one part of the total cost — false declines, manual review labor, and overly conservative transaction rules can create substantial additional operating costs that don’t show up in the same line item.
The revenue loss that never shows up in the fraud report
A false decline happens when a legitimate customer’s payment is incorrectly rejected because it looks risky, even though the transaction is valid.
The immediate cost of a false decline in payments is a lost sale. The compounding cost is a lost customer: 41% of falsely declined shoppers never return to that store. A single miscalibrated control does not generate a chargeback or a fraud alert; it just sends customers on their way. Repeated across a merchant’s transaction volume, that pattern becomes a retention problem, and eventually a platform problem.
Merchants absorbing consistent false declines will often look for the source, even if they cannot see the full payment decision path. If they start connecting lost customers or failed recurring charges to the platform experience, that risk can become an ISV retention issue before it ever appears in a churn report.
For example, a professional services firm may use the platform to bill a $12,000 monthly retainer. If that legitimate recurring charge is declined, the merchant does not see a fraud prevention success. They see delayed cash flow, an uncomfortable client conversation, and a reason to wonder whether the payment experience is standing in the way of revenue.
The structural problem with out-of-the-box defaults
Risk controls calibrated to average transaction behavior across a broad merchant base perform well in the middle of the distribution. At the edges, they produce predictable and avoidable failures, and 47% of merchants estimate that up to 5% of their legitimate orders are incorrectly declined as fraudulent as a result.
The miscalibration is structural. A merchant processing large, infrequent transactions looks nothing like one processing hundreds of small daily transactions, but default and broad-based controls often treat them identically. The profiles that tend to absorb the most false declines from generic defaults include:
- High average order value merchants, where infrequent large transactions trigger conservative thresholds calibrated for lower-value volume
- Professional services firms billing monthly retainers, where recurring large charges read as anomalous against a broad-base baseline
- Specialty retailers with irregular transaction cadence, where purchasing patterns fall outside the frequency assumptions baked into default rules
One layer of this problem sits outside the ISV’s direct visibility. Many default decisions are made upstream at the gateway, processor, or network level, and the signals driving them are opaque to both the merchant and the ISV. This is where the ISV’s leverage starts: knowing which controls can be tuned inside the platform, which decisions happen upstream, and where a payment partner can help prevent a legitimate transaction from being blocked unnecessarily.
The checkout experience starts at the infrastructure layer
The frictionless checkout experience merchants want to offer depends on having an infrastructure reliable enough to apply controls consistently without slowing authorization. Each layer in the authorization sequence represents a point where merchant-aware configuration produces a different result than a generic default:
- Gateway-level controls determine which transactions are flagged before they reach the processor. Generic thresholds applied here can produce a high volume of false declines because they don’t have a lot of context about the merchant’s actual transaction profile.
- Risk signals passed during authorization shape the issuer’s decision. Hosted payment pages and tokenized credentials produce cleaner signals than unstructured checkout flows, reducing the likelihood of a conservative issuer response.
- Network-level decisions are the least visible layer for both merchants and ISVs, and the hardest to influence without a payment partner who understands how those signals interact with merchant-specific transaction patterns.
ISVs that understand those layers, and can align their payment partnership to the actual transaction profiles their merchants carry, are solving for something 85% of merchants identify as their top fraud challenge: preventing fraud without degrading the customer experience
The right infrastructure protects the revenue
Payment experience optimization starts with the right framing, and security versus conversion is the wrong one. The real opportunity lies in understanding where fraud decisions are made across the payment stack, and which of those decisions can be tuned to better reflect a merchant’s transaction profile.
For ISVs, that means configuring fraud controls within their own platform while working with their payment provider to better understand where gateway, processor, or network-level decisions may be contributing to unnecessary false declines. This will ultimately ensure legitimate transactions aren’t being blocked by one-size-fits-all defaults.
A platform that generates fewer false declines without reducing fraud controls is performing better across both dimensions simultaneously. That is an infrastructure outcome, and ISVs are well-positioned to surface it before merchants start looking for the answer elsewhere.
"*" indicates required fields