Growing Approved Payment Volume for an iGaming Operator

Gaurav Choudhary Gaurav Choudhary
Last Updated November 17, 2026
15 mins read
Growing Approved Payment Volume for an iGaming Operator

Approved payment volume is the value of deposits your stack accepted divided by the value of deposits players attempted over the same period. Measure it in currency, split it by decline code, and it becomes a number you can diagnose, improve and write into a contract. This article treats it as an operating metric you own, not a figure your processor reports to you.

On this page

What Approved Payment Volume iGaming Operators Actually Measure

The definition is short. Approved payment volume equals accepted deposit value divided by attempted deposit value, over one fixed period. A deposit counts as attempted the moment the player submits it from the cashier, whatever happens next. A deposit counts as accepted only when funds are confirmed and the wallet is credited.

The denominator matters more than the numerator. Many dashboards divide approved transactions by total transactions. That is a count-based approval rate, and it misleads whenever small deposits dominate your traffic. Consider a hypothetical day with 100 attempts: 90 deposits of $20 and 10 of $500. Attempted value is $6,800. If every small deposit clears and five of the large ones are declined, the count-based rate reads 95%. The value-based figure is $4,300 over $6,800, or about 63%. Same day, same data, a thirty-point gap. The players you lose are the ones who deposit the most.

Counting raw transactions has a second flaw. A player who fails twice and succeeds on the third try generates three attempts and one approval. Your count-based rate looks poor even though the player was served. Your value-based rate looks fine for the same reason, and that is correct, because the revenue arrived. Decide up front how you treat retries. The cleanest rule is to group attempts by player, amount and a short time window into one deposit intent, then report both the first-attempt rate and the final-outcome rate. The gap between them tells you how much your retry and fallback logic is recovering.

Fix One Denominator

Pick one definition and use it in every report: finance, payments, product, and any target you set with a provider. Write it down in a single sentence and attach it to the dashboard. The common failure is a quarterly review where the processor quotes a rate on its own denominator, often net of fraud blocks applied before the request reaches the issuer, while your team quotes another. Neither is wrong. They just cannot be compared.

The same rule applies to the headline target. If leadership sets a goal for approved payment volume, state the denominator, the period, the currency basis and which methods are in scope. Exclude nothing silently. If you exclude test traffic or internal accounts, say so in the definition.

The Decline Code Is the Unit of Diagnosis

A rate tells you that something is wrong. A decline code tells you what. Every refused deposit carries a response from the issuer, the acquirer or your own risk layer, and that response is the only reliable starting point for a fix. Treat each code as a row in your analysis, weighted by the deposit value it cost you. A code that appears rarely but attaches to large deposits can outrank a frequent code on small ones.

Raw codes differ between acquirers and methods, so map them into your own categories and keep the original alongside. A workable set is insufficient funds, issuer do-not-honor, authentication failed, data mismatch, suspected fraud, technical error and method not permitted. Keep that map under version control. When the categories shift between months, your period-over-period comparison stops meaning anything.

Why Deposits Get Declined Before the Player Reaches the Game

Most declines trace back to one of three causes: the issuing bank’s risk rules, an authentication challenge the player did not complete, or player data that does not match the card or account. Each leaves a different signature in your logs, and each calls for a different owner on your team.

The Three Common Causes

Issuer risk rules: Issuing banks score gambling transactions on their own terms. Merchant category, deposit size, a first-time merchant, cross-border routing and velocity can each push a score over the line. These usually surface as generic do-not-honor responses, which tell you little on their own. Patterns across issuers, amounts and times of day tell you more.

Failed authentication: A 3-D Secure challenge can fail because the player abandons it, mistypes a code, never receives an SMS, or the issuer’s access control server times out. Some of these are player behavior and some are issuer infrastructure. The EMVCo specifications for 3-D Secure authentication define how frictionless and challenge flows are meant to work, and reading them clarifies which data elements you can send to raise the share of frictionless approvals.

Data mismatch: Address verification failures, a name on the account that differs from the name on the card, an expired card, or a wrong CVV. These are often your fault in the sense that the cashier form invited the error. Poor field validation, no card-number formatting and unclear error messages all inflate this category.

Split Before You Conclude Anything

Take the value-weighted decline data and cut it four ways: by route, by method, by region and by decline code. Route means the acquirer or provider path the request took. Looking at any single cut hides the cause. A low overall rate might be one acquirer failing for one issuer country on one card scheme. Only the combined view shows it.

Build the cut as a standing report, not an ad hoc query. Include attempted value, accepted value, rate and the top three decline codes per segment. Add a minimum-volume threshold so a segment with twelve attempts does not trigger an alarm.

Platform Faults Versus Player-Specific Declines

The distinction that saves the most time is between faults that hit many players on one route and declines that hit one player. A platform fault looks like a sudden drop on a single route or method, usually with a cluster of technical-error codes or timeouts, across many unrelated accounts. The response is configuration, escalation to the provider, or a reroute. A player-specific decline looks scattered: one account, one card, repeated attempts, a mismatch or insufficient-funds code. Changing routing for it accomplishes nothing. It needs a clear message in the cashier and a support path that can help the player try another method.

Mixing the two up wastes effort in both directions. Teams adjust routing rules for a problem that is one player’s expired card, or tell support to wait out a fault that is actually an acquirer outage. If your payment layer exposes route-level response data cleanly, this diagnosis takes minutes. If it does not, a well-specified payment gateway API integration that returns normalized decline codes, route identifiers and latency per request is the foundation for everything that follows.

Routing Deposits Across Methods and Acquirers to Lift Approval

A second acquirer or payment method raises approval when it reaches players your first route cannot serve, or when it handles a decline category the first route handles badly. It does nothing when the declines come from the issuer or the player, because the same issuer will refuse the same transaction on any route.

When a Second Route Helps and When It Duplicates

Check your decline mix first. A second acquirer is worth testing when you see technical errors, acquirer-side risk blocks, poor local acquiring in a specific region, or weak authentication performance on one route. Local acquiring in a player’s own country often lifts issuer trust, because the transaction looks domestic. A different method adds value when it reaches players who do not hold or do not want to use a card.

It will mostly duplicate when the dominant codes are insufficient funds, expired card, wrong CVV or issuer do-not-honor on cards that are simply not approved for gambling. Those players will fail again on route two. If you are operating in a category that acquirers treat cautiously, the account structure behind each route matters too, and our piece on high-risk payment processing covers what to ask for there.

Run a Controlled Test

Do not switch traffic wholesale. Split a small, random share of deposit attempts to the new route or method while the rest stays on the current one. Randomize at the deposit-intent level, not by country or time of day, or you will be comparing different populations. Hold the test long enough to collect a meaningful number of declines in each code category, and compare value-weighted approval by decline code, not just the headline rate.

The code-level comparison is the point. A new route might win overall because it handles technical errors better while losing on issuer declines for one region. That is a routing rule, not a wholesale migration. If the test route wins in specific segments, scale it there first and keep watching the same report. Set a rollback condition before the test starts.

Fallback Logic: Retry Soft Declines Only

Automatic fallback recovers revenue when it is selective. A soft decline is temporary or route-related, and a retry on a different route or after a short delay can succeed. A hard decline is permanent for that card or account, and a retry only adds noise, costs fees and can push issuers toward blocking you.

Decline class Typical examples Action
Soft Issuer unavailable, system malfunction, timeout, some do-not-honor responses Retry once on an alternate route, or prompt the player to retry
Authentication Challenge failed or abandoned Offer a fresh challenge, or suggest another method
Hard Invalid card number, expired card, lost or stolen, restricted card Do not retry, ask for a different card or method
Fraud or policy Suspected fraud, transaction not permitted Do not retry, route to risk or support

Treat that table as a starting point. Code semantics vary by acquirer, so confirm each mapping with your provider before encoding it. Cap retries per deposit intent and log every attempt so the first-attempt and final-outcome rates stay separable.

Alternative Rails

Some declines are really a card problem, and no routing rule fixes them. Bank-based methods bypass the card network entirely. If you are weighing that option, pay-by-bank in the cashier sets out what to ask a provider before you add it. Measure it on the same denominator as everything else, so its contribution to approved payment volume is visible rather than assumed.

Tuning KYC and Authentication so Checks Do Not Block Good Deposits

Stronger verification lowers fraud and compliance risk, and it also lowers approval when applied indiscriminately. Every extra step is a place where a legitimate player abandons or fails. The aim is not minimum friction. It is friction proportional to risk, applied where risk actually sits.

The Trade-Off, Stated Plainly

Authentication friction costs you in two ways. Players who face a challenge fail or drop out, and issuers that see weak authentication data may decline more often. Loosening checks lifts approval in the short term, but a higher fraud and chargeback rate can bring tighter acquirer terms, reserve requirements or a lost account. Neither extreme is a strategy. Treat tighter KYC as a lever with a measurable cost in approved payment volume, and measure the cost, because it can be small when the checks are well placed and large when they hit everyone.

Risk-Tiered Checks

A tiered model sorts players by what you know about them and applies checks accordingly. A sensible shape looks like this:

  • Low tier: Fully verified players with clean history, depositing small amounts on a previously used method, skip optional extra steps and use frictionless authentication where the issuer allows it.
  • Standard tier: Verified players with a new method, a larger-than-usual deposit or a changed device get a standard authentication challenge.
  • High tier: Accounts with risk flags, such as mismatched identity data, rapid method changes, known bad patterns or unusual velocity, face full authentication and, where needed, manual review before funds are accepted.

Set the thresholds from your own data, not from a template. Review them against the decline and chargeback figures by tier. If the low tier shows chargebacks creeping up, tighten it. If the high tier shows many good players failing, widen the criteria or improve the data you pass to the issuer.

Document Every Tier

A regulator will want to follow your logic, and so will your acquirer. For each tier, record the entry criteria, the checks applied, the data used, who approved the rule and when it last changed. Keep the change history. Rules that live only in a risk engineer’s head, or in an undocumented config file, fail an audit even when they work well. The FATF guidance on a risk-based approach is the common reference point for proportional controls, and aligning your tier documentation with that language makes the case easier to present. Check your own licence conditions as well, since local rules can set a floor you cannot tier below.

Look at Both Ends of the Funnel

Deposit-time checks are only half of the friction story. Players who struggle through identity verification at signup arrive at the cashier already frustrated, and some never attempt a deposit. The signup-side view is in our piece on KYC friction at signup. Read the two together, since a check moved from signup to first deposit still costs you something, just in a different report.

Setting an SLA and a Monthly Approval Review for Your Payment Provider

Write the SLA terms that bear on approval into the contract, then hold a monthly review that checks the provider against them with your own data. The contract sets the floor. The review tells you whether you are above it and what to do next.

SLA Terms Worth Writing Down

What a typical provider offers varies widely, and the headline uptime figure is rarely the whole story, so negotiate the terms below rather than accepting a template.

Term What to specify
Monthly availability A percentage measured per route and method, with the measurement method stated
Scheduled maintenance Notice period, maximum window length, and whether maintenance counts toward downtime
Authorization response time A target and a percentile, for example the share of requests answered within a set number of seconds
Incident handling Time to acknowledge, time to update, and a post-incident report
Service credits A defined credit when availability or response targets are missed, and the claim process
Reporting Access to decline-code data by route, issuer country and method

Two points deserve extra attention. First, maintenance exclusions can swallow the availability figure. A generous exclusion window makes a high percentage meaningless, so cap it. Second, availability is not approval. A route can be fully up and still decline heavily. If you can, add an approval-related term, even a reporting and remediation obligation when approval on a segment falls below an agreed level. Providers resist hard approval guarantees because issuers control the outcome, but a duty to investigate and report is usually negotiable.

The Monthly Review

Run it on a fixed date with the same participants: payments, risk, finance and a provider representative for at least part of it. Use one pack each month, built on the single denominator from the start of this article. It should show approved payment volume and the payment approval rate by method, by region and by decline code, each compared with the previous period and with the same month a year earlier if you have it. Add attempted value so a rate change can be read against a volume change, plus first-attempt versus final-outcome rates, and the top decline codes ranked by value lost.

Review decline codes at least monthly, and watch the largest ones weekly. A new code appearing, or an existing code doubling its share, is worth a same-week look. Do not wait for the review.

Turning the Review into a Decision

Each month should end with one of three outcomes, and the data should point to it.

  • Renegotiate: Use this when the provider missed SLA targets, or when its route consistently underperforms alternatives in your controlled tests. Bring the evidence, claim the credits, and ask for specific changes.
  • Add a route: Use this when declines concentrate in a segment a second acquirer or method could serve, such as technical errors in one region. Start with the controlled test described earlier.
  • Fix an integration: Use this when the cause sits on your side, such as data mismatches from the cashier form, missing authentication data, or retries firing on hard declines. No contract change helps here.

Start with the codes that cost the most value and sit within your control: data mismatches, retries on the wrong class, and authentication data you are not sending. Those pay back fastest. Issuer-side declines come last, because you can influence them but not decide them.

Record each decision and its expected effect, then check it at the next review. Over a few months you will have a log showing which interventions moved approved payment volume and which did not, and that log is more useful in a provider negotiation than any benchmark.

Approved Payment Volume iGaming FAQs Buyers Ask Most

What SLA does a typical iGaming payment solution offer?

Payment gateway contracts usually quote availability as a monthly uptime percentage, and 99.9% is a common target. That figure only means something once you know what counts as downtime, so ask whether scheduled maintenance is excluded and how partial outages affect acceptance. Get the authorization response-time target in writing as well, because slow responses lose deposits even when the service is technically up.

Does adding a second payment provider always raise approved payment volume iGaming operators see?

No. A second provider helps only when declines are specific to the first route. If both routes hit the same issuer rules or the same player-data mismatch, the second route declines the same deposits. Compare decline codes by route for several weeks before moving significant volume. Keep the contract flexible enough to shift traffic back if the new route underperforms.

How often should an operator review decline codes?

Weekly is practical for most operators, with a deeper monthly review by method and region. A weekly check catches a sudden spike in one issuer’s declines before it costs a full day of deposits. The monthly review shows whether a fix held over a longer period.

Will tighter KYC lower approved payment volume?

It can, if the same checks run on every deposit regardless of risk. Tiering checks so that verified, low-value players skip extra steps usually protects approvals without weakening controls on higher-risk accounts. Record the tiers in your compliance documentation so the logic can be shown to a regulator.

Which decline codes should an operator fix first?

Start with codes that hit many distinct players on one route, because they usually point to a configuration or integration fault that the operator controls. Codes that repeat for a single player usually reflect that player’s bank or account, so they need a support response rather than a platform change.

Gaurav Choudhary

Gaurav Choudhary

| COO

Gaurav Choudhary, COO at Source Code Lab, drives iGaming strategy and growth as a leading iGaming platform provider. With 10+ years of experience in iGaming Industry, he crafts user-centric iGaming software platforms for sportsbook, casino, fantasy, RMG, and B2B solutions. He excels in GTM execution, affiliates, emerging markets, and digital transformation, optimizing products from roadmap to launch.

Location Map

Let's Build Success

From concept to launch, we help build winning gaming platforms. Let's discuss your project.

Blog Form