Reducing false declines without letting in more fraud

Fraud losses are easy to see. They arrive as chargebacks with amounts attached. False declines are harder to see, because a good customer who is turned away leaves no record beyond a failed attempt. Yet in many businesses the revenue lost to false declines is several times the revenue lost to fraud.

This post covers how to estimate false declines, where they come from, and how to reduce them without raising your fraud rate.

Figures in this post are illustrative placeholders, not measured results.

Where false declines come from

A legitimate payment can be declined at three points:

1. Your own fraud rules. A rule that blocks orders over a certain amount from a new country will block real customers too.
2. The issuer. The card issuer may decline because the transaction looks unusual to its model, often because it is cross-border or lacks data.
3. Authentication. A 3-D Secure challenge that fails or times out is recorded as a failure, even when the shopper simply could not find their phone.

Each needs a different fix, so start by separating them in your data.

Estimating the size of the problem

You cannot know for certain which declines were false. You can estimate:

• Retry success. When a declined shopper retries with the same card and succeeds within an hour, the first decline was probably false.
• Later purchases. Shoppers declined once who complete a purchase later with the same card or email are likely good customers.
• Manual review outcomes. If you review a sample of blocked orders and contact the shoppers, the share that turn out genuine is a direct estimate for your own rules.

In our illustrative dataset, 2.4% of all attempts were declined by merchant rules. Review of a sample suggested roughly 70% of those were genuine, a loss well above the merchant's 0.3% fraud chargeback rate.

Fixing your own rules

Rules accumulate. Each one was added for a reason, and few are removed. Go through them with three questions:

• What does this rule catch? Look at the chargebacks it would have prevented in the last 90 days.
• What does it cost? Look at the orders it blocked and estimate how many were genuine.
• Is there a softer action? Many rules can send an order to 3-D Secure or manual review instead of declining it.

Replacing hard blocks with a step-up to authentication often recovers good orders while keeping fraud flat, because fraudsters fail the step-up at a much higher rate than genuine customers. Fraud Shield supports scored outcomes, so you can approve, challenge or decline by risk band rather than by single rule.

Helping the issuer say yes

Issuers approve more when they see more context. Things within your control:

• Send full data. Billing address, shopper email, device data for 3-D Secure, and line items where the scheme supports them.
• Use network tokens. Tokenised card credentials tend to approve at a higher rate and stay current when cards are reissued. See Network Tokens.
• Acquire locally. A domestic transaction looks less risky to the issuer than a cross-border one. Our post on local acquiring explains why.
• Use a clear descriptor. A statement line the shopper recognises reduces "I don't know this charge" disputes, which in turn affects how issuers score you over time.

Getting authentication right

3-D Secure moves fraud liability to the issuer, but every challenge is a point where a shopper can drop off.

• Request exemptions where eligible. Low-value and low-risk transactions in regions such as the EEA and UK can often skip the challenge.
• Use frictionless flows. Sending richer data increases the share of authentications that complete without a challenge.
• Retry declined exemptions with authentication. If an issuer declines an exempt transaction with a soft decline asking for authentication, retry with 3-D Secure rather than failing the order.

Authentication handles exemption requests and soft-decline retries automatically.

Retrying soft declines

Some decline codes mean "try again later" or "try differently". Retrying these once, with adjusted data or routing, recovers a share of payments. Smart Routing can retry eligible declines through a second acquiring path.

Do not retry hard declines such as stolen card or closed account. Repeated retries on these can attract scheme fees and damage your standing with issuers.

Measuring the result

Track three numbers together, every week:

• Approval rate, split by reason for decline.
• Fraud chargeback rate, by count and by value.
• Share of orders that went through a challenge.

If approvals rise and fraud stays flat, the change worked. If both rise, look at which segment drove it. Acceptance Insights shows these metrics side by side, and the glossary defines the decline categories used in this post.