Definition
Payment Approval Rate (AR%, also acceptance rate) is the share of payment transaction attempts that complete successfully. It is the core KPI of an iGaming cashier: every point of approval rate lost is acquisition money spent on players who tried to pay and couldn't.
Formula
AR % = Successful transactions ÷ All transaction attempts
Two complementary views: AR (transactions) — successful deposit transactions ÷ all deposit attempts — and AR (users) — players with at least one successful deposit ÷ players who attempted a deposit.
AR (users) can be higher than AR (transactions) when players retry after failures. The gap is diagnostic, but it does not reveal the cause by itself: inspect retries, abandonment, method switches and decline codes.
How operators use it
| Cut | Question answered | Required evidence |
|---|---|---|
| Method × provider | Is one route depressing the blend? | Attempts, approvals and decline-code distribution |
| First vs repeat deposit | Is acquisition or repeat monetisation affected? | Like-for-like cohorts by deposit number and risk state |
| User vs transaction | Are retries masking transaction friction? | Unique users, attempts, retries, switches and abandonment |
| Withdrawal outcome | Are valid withdrawals completing? | Success, rejection reason, p50/p95 time and manual-review rate |
A single failing method can sink the blended average, so AR is monitored per payment method and provider, never only in aggregate. A low rate can reflect issuer declines, authentication, limits, fraud controls, technical failure or traffic mix; the metric alone cannot decide which.
The most valuable cut is AR by deposit number. First-deposit failure affects acquisition economics, while repeat-deposit failure affects already activated cohorts. Compare the same market, method, issuer mix and risk state before calling a change abnormal.
The payment-method roadmap should come from eligible-user coverage, approval, abandonment, withdrawal success, cost, fraud and reconciliation evidence. Do not assume a bank rail always outperforms cards, or that another provider will fix an issuer- or policy-driven decline.
Common misinterpretations
Showing only user-level AR can hide transaction retries, while a blended transaction rate can hide a method- or provider-specific issue. Publish both where useful, decompose by method and terminal outcome, and inspect issuer, authentication, risk, input, outage and abandonment evidence before assigning a cause. A low rate alone is not a traffic-quality or infrastructure verdict.
Related metrics: Registration-to-Deposit Conversion · First-Time Deposit (FTD) · Second Deposit Conversion · Hold Percentage
Common questions
What is a good payment approval rate for an online casino?
There is no defensible universal approval-rate threshold. Card, bank-transfer, wallet, first-deposit and repeat-deposit attempts have different risk and issuer mixes. Establish a baseline per method, provider, market tier, device and deposit number, then investigate statistically meaningful deterioration and processor decline reasons.
Why is user-level AR higher than transaction-level AR?
Because players retry after failed attempts. If transaction AR is low but user AR is much higher, players are eventually getting money in — but through a frustrating flow that some share of them abandons. Report both numbers; each tells a different part of the story.
Why does approval rate change after the first deposit?
Do not assume a normal direction. Changes can come from payment-method mix, issuer response, authentication, limits, fraud controls or player selection. Compare like-for-like cohorts and decline codes by deposit number before attributing the change to one cause.