Approval Rate

Overview

Approval Rate is often calculated as approved attempts divided by total eligible authorization attempts. The denominator should exclude requests that never reached a decision, such as malformed API calls, while business reporting can separately track checkout conversion.

Approval rate is related to but not always the exact complement of Decline Rate . Pending, canceled, timed-out, abandoned authentication, and technical-failure states can exist between approval and decline.

Segmenting the metric identifies where performance changes. A stable global rate can hide a sharp decline for one issuer, country, payment method, currency, device, or off-session use case. Both transaction count and approved value should be monitored.

Duplicate retries should be controlled through Duplicate Detection so one unsuccessful customer payment does not appear as several independent declines. Conversely, combining genuinely separate attempts can hide poor customer experience.

Optimization must balance valid approval against fraud, disputes, and operating cost. Relaxing controls can increase approvals while increasing losses. A complete performance view compares approval, fraud, dispute, retry, abandonment, and customer-conversion outcomes together.

A robust metric also distinguishes merchant-controlled and external causes. Invalid integration data, unsupported payment methods, or unnecessary authentication failures can be corrected by the merchant, while issuer risk policy may be less directly controllable. Prioritizing by recoverable revenue, customer segment, and root cause helps teams improve approval without encouraging unsafe retries or weakening fraud prevention.

Reporting should state whether approvals are measured at authorization, completed payment, or another stage. Mixing these definitions across teams creates false comparisons and misdirected optimization work.

The calculation rule should be documented beside every dashboard and executive report.