Notifications
Clear all
Topic starter
11/07/2026 8:35 pm
TL;DR: Transaction authorization and merchant approval are separate decisions at checkout, and banks often decline good customers because they lack richer context while sophisticated fraud still gets through, according to Signifyd. The governance problem is not just fraud scoring but decision quality at each control point, where thin data creates revenue loss, chargebacks, and avoidable customer friction.
NHIMG editorial — based on content published by Signifyd: approval vs. authorization transactions and their impact on fraud and revenue
By the numbers:
- In fact, according to Signifyd data, 15% of orders are falsely declined for authorization by banks.
- A healthy approval rate is highly variable, depending on vertical, product mix and risk appetite, but if your approval rate falls out of the mid-to-upper 90% range, it may signal overly strict fraud filters.
- In card-not-present transactions, authorization rates for online transactions are roughly 10 percentage points lower than for in-store transactions.
Questions worth separating out
Q: What breaks when payment authorization data is too thin?
A: When issuers only see basic transaction fields, they are more likely to decline good customers and miss sophisticated fraud patterns.
Q: Why do merchants need to care about issuer authorization decisions?
A: Because issuer decisions directly affect conversion and revenue before the merchant ever makes an approval call.
Q: How do you know if approval controls are too strict?
A: Look for approval rates that drift below expected ranges for your vertical, rising manual-review queues, and a growing share of legitimate customers being blocked.
Practitioner guidance
- Define separate issuer and merchant control objectives Document which decisions belong to the bank and which belong to the merchant, then assign explicit success metrics for each stage.
- Enrich pre-authorization signals before sending transactions upstream Pass device, order-history, and behavioural context into the pre-authorization path so issuers can distinguish legitimate customers from risky traffic with more confidence.
- Tune fraud filters against false-decline thresholds Review manual-review queues and fraud rules when approval rates fall below expected ranges, and compare decline reasons against customer value segments to find avoidable friction.
What's in the full article
Signifyd's full article covers the operational detail this post intentionally leaves for the source:
- Detailed walkthroughs of authorization and approval decision flow, including who acts first and what signals each party can see.
- The article's full breakdown of authorization rate, approval rate, and chargeback rate calculations for ecommerce teams.
- Examples of how pre-authorization changes issuer decision quality and reduces fees on doomed transactions.
- Further explanation of why card-not-present commerce creates lower authorization rates than in-store transactions.
👉 Read Signifyd's analysis of approval vs. authorization transactions →
False declines in transaction authorization: what should merchants do?
Explore further
11/07/2026 9:03 pm
Transaction authorization is a decision-quality problem, not just a fraud-score problem. Banks decide with limited context, so false declines and missed fraud are both predictable outcomes of thin data. That makes the governance question less about any single model and more about where richer signals should enter the control chain. Practitioners should evaluate authorization as a layered decision workflow, not a single pass or fail event.
A question worth separating out:
Q: Who is accountable when false declines and chargebacks rise?
A: Accountability is shared, but it is not ambiguous. The issuer owns the authorization decision, the merchant owns the approval decision, and both should be measured against the quality of the data they use. A governance model that assigns ownership for each stage makes root-cause analysis and remediation far more effective.
👉 Read our full editorial: Transaction authorization gaps are driving false declines and fraud loss
