Why do so many player deposits get declined even though my merchant account is approved?

Because approval happens twice: your acquirer approved you, but each player's issuing bank decides whether to approve a 7995 transaction, and many US issuers decline gambling codes by default or apply extra scrutiny. Operators improve approval rates with multiple MIDs across acquirers, smart cascading retries, and clean transaction data, but some level of issuer decline is structural to the MCC.

Can I code my skill-game or sweepstakes platform as regular digital goods to avoid gambling declines?

No. If the card networks determine your product is wagering, running it under a non-gambling MCC is miscoding, which triggers brand fines against your acquirer, immediate termination, and likely MATCH listing. The recent wave of state sweepstakes bans has put these models under active network scrutiny. Get a legal opinion, present it to your acquirer, and run under the code they register you for.

How do I fight chargebacks from players who lost money and disputed their deposits?

With account-level evidence. Link every deposit to KYC identity verification, device fingerprint, IP and geolocation logs, session history, and withdrawal records, then submit that package in representment against unauthorized-use claims. Operators with this evidence pipeline win a large share of friendly-fraud disputes, and pairing it with Verifi and Ethoca alerts lets you freeze balances before disputed funds are cashed out.

High-risk vertical

Online Gaming & Skill Games: payment processing without the fragility

Real-money gaming lives or dies on a state-by-state legality map that changes every legislative session, and the card networks enforce that map through merchant coding and registration. Anything that touches wagering must run under MCC 7995, a code many issuing banks decline by default, while the skill-game and sweepstakes models that try to live outside 7995 are being banned state by state. Payment acceptance here is as much a licensing and coding problem as a processing one.

Why processors flag this vertical

Legality is fragmented by state and by game model: chance-based gambling, skill-based contests with entry fees, and sweepstakes casinos each have different legal maps, and the sweepstakes model was banned by statute in states including California, New York, New Jersey, Connecticut, Montana, and Nevada during 2025 and 2026.
UIGEA obligates the US payments system to block unlawful internet gambling transactions, so processors carry direct regulatory exposure for a merchant's geolocation failures.
Visa and Mastercard treat gambling as a restricted, registration-required category, and acquirers must register 7995 merchants and vouch for their licensing before a single transaction runs.
Instant-redeposit behavior by losing players and the emotional character of wagering losses produce friendly-fraud rates well above ecommerce norms.
The vertical is a money-laundering and bonus-abuse target, which drags AML and KYC obligations into merchant underwriting.
Operators tempted to miscode wagering volume under benign MCCs like 7994 or digital goods commit transaction laundering, and the card brands fine acquirers heavily for it, which makes banks skittish about the whole category.

What drives chargebacks here

Losing players disputing deposits as unauthorized after gambling losses, the classic friendly-fraud pattern of the vertical.
Family-member card use, especially minors depositing on a parent's card, followed by unauthorized-transaction claims.
Disputes triggered by slow or restricted withdrawals, where a player who cannot cash out promptly charges back deposits instead.
Bonus and promotion misunderstandings, such as wagering requirements locking funds a player believed were withdrawable.
True fraud from stolen cards used to launder funds through deposit-and-withdraw cycles.

Processing challenges to expect

Mainstream PSPs decline real-money gaming, and even gaming-tolerant acquirers require gaming licenses, state-by-state legal opinions, and card-brand registration before boarding.
MCC 7995 transactions are declined at elevated rates by US issuers, some of which block the code categorically, so even a fully approved merchant sees materially lower authorization rates than normal ecommerce.
Skill-game and sweepstakes operators occupy a coding gray zone: run as 7995 and inherit gambling declines, or code as games and risk brand fines and termination if the networks judge the product to be wagering.
Acquirers demand robust geolocation, age verification, and self-exclusion controls, and a documented failure in any of them is grounds for immediate termination.
Reserves and settlement delays are standard because player-balance liabilities and bonus abuse leave the acquirer exposed if the operator fails.

The infrastructure playbook

Get the coding question settled in writing before building anything: a legal opinion on whether your model is wagering under the states you serve, and acquirer confirmation of the MCC you will run under, because retroactive recoding is how operators end up on MATCH.
Run cascading MIDs across multiple acquirers with intelligent retry, since issuer-side 7995 declines make single-MID setups leave real approval percentage on the table.
Enforce geolocation blocking at deposit, not just signup, and keep the blocklist synced to the moving legal map, including the recent sweepstakes bans, because UIGEA exposure lands on your processor and they audit for it.
Deploy Ethoca and Verifi alerts with automated player-account correlation, so a deposit dispute freezes the player balance before funds are withdrawn and the loss compounds.
Tie chargeback defense to your KYC stack: device fingerprints, login history, and gameplay records are winning evidence against 'unauthorized transaction' claims from players who used the account for weeks.
Keep player payment credentials in a processor-neutral vault, since gaming operators change acquirers more often than almost any vertical and re-onboarding depositors is a direct revenue hit.

Frequently asked questions

Why do so many player deposits get declined even though my merchant account is approved?: Because approval happens twice: your acquirer approved you, but each player's issuing bank decides whether to approve a 7995 transaction, and many US issuers decline gambling codes by default or apply extra scrutiny. Operators improve approval rates with multiple MIDs across acquirers, smart cascading retries, and clean transaction data, but some level of issuer decline is structural to the MCC.
Can I code my skill-game or sweepstakes platform as regular digital goods to avoid gambling declines?: No. If the card networks determine your product is wagering, running it under a non-gambling MCC is miscoding, which triggers brand fines against your acquirer, immediate termination, and likely MATCH listing. The recent wave of state sweepstakes bans has put these models under active network scrutiny. Get a legal opinion, present it to your acquirer, and run under the code they register you for.
How do I fight chargebacks from players who lost money and disputed their deposits?: With account-level evidence. Link every deposit to KYC identity verification, device fingerprint, IP and geolocation logs, session history, and withdrawal records, then submit that package in representment against unauthorized-use claims. Operators with this evidence pipeline win a large share of friendly-fraud disputes, and pairing it with Verifi and Ethoca alerts lets you freeze balances before disputed funds are cashed out.

Related verticals