In-Short
Core Idea
Approval rate is useful, but it is not neutral. The number changes when the reporting logic changes.
Why It Matters
Teams use approval ratio to judge providers, migrations, and payment health. If the denominator is incomplete, the business can back the wrong system with too much confidence.
How It Works
Different reports count different transaction states. Once cancelled attempts, incomplete flows, or vague failure labels are handled differently, the same provider can look stronger or weaker without the user experience actually changing.
Simple Way to Imagine It
It is like judging a checkout line only by the customers who reached the cashier, while ignoring the people who abandoned the queue before paying.
Where the issue first showed up
Long Read
Payment approval ratio is one of the most common metrics used to evaluate deposit performance. On paper it should show how reliable a payment provider is. In practice the number can change depending on how declined, cancelled, and incomplete transactions are classified.
During a payment provider migration, I ran into a case where approval ratios looked significantly different depending on the reporting source. That immediately raised a more useful question than "which number is better?" The real question was "what exactly is each report counting?"
The business was using two separate payment providers. One handled casino deposits, while another handled sports betting deposits. Casino deposits historically showed higher approval ratios, so consolidating deposits under the stronger provider looked logical from both a commercial and operational perspective.
At first sight, the migration seemed to work. Deposits looked healthy and the headline ratio appeared strong.