How does a false decline happen?
Every fraud control trades missed fraud against blocked good customers. A risk model gives a payment a score, a rule compares it with a threshold, and anything above it is declined or sent to review. Stripe’s documentation, for example, blocks payments its models rate as high risk by default and lets merchants add a payment they know is legitimate to an allow list. Simple checks have the same problem: Stripe notes that address verification can fail for legitimate payments, for example when a customer has moved without telling the issuer.
Why do false declines matter?
The loss is the whole order and often the customer, not only the margin. Baymard Institute’s survey of shoppers who abandoned an order found that 10% left because their card was declined. As an illustrative example: a store blocks 1.5% of 40,000 monthly payments for risk. If two thirds of those 600 blocks were genuine customers with an average order of 50 euros, false declines cost 20,000 euros a month in sales, likely more than the fraud the rule stopped.
How do merchants reduce them?
By measuring them, then loosening the controls that cost more than they save. Practical steps include a 3-D Secure challenge instead of an outright block for borderline payments, routing cross-border cards to a local acquirer, rules that treat known returning customers differently from new ones, and a second route or method after a soft decline.
Where does Omno use it?
Omno’s cascading moves a rejected payment to the next PSP in the routing rule and the hosted checkout lets a customer choose another method after a decline. Customer groups let returning customers follow different routes from first purchases, and the routing-decision log records the response code for every attempt, so declines can be analysed per provider, card country and group.