// Blog · Payments
Why your casino deposit approval rate is low, and what actually fixes it
Every point of card approval is deposits you already earned the marketing cost for. Most casino brands are leaving five to ten of them on the table, and the reasons are diagnosable.
Operators obsess over acquisition cost and bonus cost, and then route every deposit through one acquirer and never look at the decline log. For a brand taking €1.2M a month in deposits, each point of approval is roughly €13,000 a month. The gap between a typical single-acquirer setup and a well-routed one is usually five to ten points.
Here is how to find out where your points are going, and what actually brings them back.
Why cards decline in gambling specifically
Gambling transactions carry merchant category code 7995. Issuing banks treat it differently from a grocery purchase, and some treat it very differently.
| Reason | Typical share of declines | What is really happening |
|---|---|---|
| Issuer decline, "do not honour" | 35 to 45% | The cardholder's bank blocks MCC 7995 by policy, or its risk model dislikes the merchant, the amount, the hour or the acquirer country. |
| Insufficient funds | 15 to 25% | Genuine. Nothing to fix on your side except offering a smaller suggested amount on retry. |
| 3-D Secure abandoned or failed | 10 to 18% | The player is sent to a bank challenge, it takes too long or fails, and they give up. |
| Acquirer risk rules | 8 to 14% | Velocity limits, country mismatches and BIN rules on the acquiring side, often set conservatively and never revisited. |
| Wrong details, expired card | 5 to 10% | Form design and stored cards fix most of this. |
The first row is the one that matters. It is also the one most platforms show you as a single opaque number.
Step 1: get the breakdown, not the rate
An approval rate on its own is not actionable. You need the same number cut four ways:
- By decline reason code, mapped to plain language, not raw ISO codes.
- By BIN country. A German card declining through a Maltese acquirer and a Brazilian card declining through the same acquirer are two different problems.
- By acquirer and PSP. If you only have one, this is already your finding.
- By first deposit versus repeat. New-card declines and known-card declines have different fixes.
If your platform cannot give you this in a report you can run yourself, that is a platform problem before it is a payments problem.
Fix 1: cascade declines to a second acquirer
Cascading means that when acquirer A returns a soft decline, the same transaction is retried through acquirer B automatically, inside the same checkout, without the player doing anything. Soft declines are the issuer saying "not this time, not this way", and a different acquirer in a different country with a different descriptor often gets a yes.
Done properly this is worth 1.5 to 3 points on its own. Done badly it doubles your fees on the declines that stay declined, so the rules matter: cascade on soft decline codes only, never on insufficient funds or stolen-card codes, and cap the chain at two retries.
Fix 2: local acquiring and local methods
Issuers approve domestic transactions at a higher rate than cross-border ones, full stop. If Brazil, Canada, Poland or Germany is a top-three market for you and you are acquiring all of it through one European entity, you are paying for that convenience in approvals.
Local payment methods go further. Pix in Brazil, Interac in Canada, Blik in Poland and open banking in the UK and Europe typically approve in the mid to high nineties, carry no MCC 7995 stigma and settle faster. In a market where they are popular, putting the local method first in the cashier moves overall approval by three to eight points.
Fix 3: make 3-D Secure frictionless where you can
Under PSD2 in Europe, strong customer authentication is required, but the rules allow exemptions for low-risk and low-value transactions, and a properly set up 3DS 2 flow lets the issuer approve without a challenge when the risk data is good. Sending rich data (device, history, address match) and requesting exemptions where they apply turns a chunk of the "abandoned at 3DS" bucket into frictionless approvals. Worth one to two points, and it also shortens the deposit flow for everyone else.
Fix 4: tokenize cards so repeat deposits are one tap
A returning player should never type a card number. Store the card as a token at the first deposit and the second deposit becomes a single tap with a known-good card, a known device and a clean history for the issuer to see. Approval on tokenized repeat deposits runs several points above first deposits.
The constraint is that storing card data properly means card data never sits in your platform in the clear. Tokenization and vaulting engineered to PCI-DSS standards solves the security problem and the approval problem at the same time.
Fix 5: recover the deposits that still fail
Whatever you do, some deposits will fail. A player who just had a card declined is at the peak of intent and, fifteen minutes later, is gone. A WhatsApp or SMS message in that window, with a one-tap retry link and an alternative method pre-selected, recovers a quarter of failed deposits for the brands we see. That is covered in detail in WhatsApp and SMS for casino retention.
What the full picture looks like
| Fix | Typical uplift | Effort |
|---|---|---|
| Cascading to a second acquirer | +1.5 to 3 pts | Low, if the platform supports it |
| Local acquiring in top markets | +2 to 5 pts | Medium, new contracts |
| Local payment methods | +3 to 8 pts | Low to medium |
| 3DS exemptions and frictionless flow | +1 to 2 pts | Low |
| Tokenized one-tap re-deposit | +1 pt, plus conversion | Low |
| Failed-deposit recovery messaging | 25% of failures recovered | Low |
None of these require heroics. They require a platform that exposes the decline data, supports multi-acquirer routing with rules you control, has local methods already integrated, and keeps card data out of your systems.
How we handle it
BetCode ships with 24 payment methods across cards, wallets, open banking, local methods and crypto, smart routing and cascading with rules you can read, multi-currency wallets, and card tokenization built to PCI-DSS standards. Decline reasons are reported in plain language by BIN country, acquirer and deposit type, and failed-deposit recovery journeys on WhatsApp and SMS are part of the CRM. If you want a second opinion on your own numbers, send us a month of decline data and we will tell you where the points are.
Questions we get asked
What is a good deposit approval rate for an online casino?
For cards it depends heavily on market mix. Low eighties is common for a single-acquirer setup, low to mid nineties is achievable with cascading, local acquiring and tokenized repeat deposits. Local methods such as Pix, Blik and open banking typically approve in the mid to high nineties.
Does cascading increase fees?
Only on transactions that are retried and still decline, which is why the rules matter. Cascade only on soft decline codes, exclude insufficient funds and fraud codes, and cap the chain at two attempts. Done that way the extra fees are small next to the recovered deposits.
Is storing cards safe for a casino?
Storing raw card numbers in your platform is not something you want to do. Tokenization replaces the card number with a token that is useless outside the vault, so your systems hold no sensitive card data. BetCode's payment technology is engineered to PCI-DSS standards for exactly this reason.
Why do my first deposits decline more than repeat deposits?
A first deposit is a new card, often a new device, and no history with the merchant. Issuers score that as riskier. Repeat deposits on a tokenized card with a clean history approve several points higher, which is one reason to make the second deposit as easy as possible.