Skip to content
Open banking routing and electronic invoicing — live across 30 countries. Routing · invoicing · 30 countries See coverage
Get started
← All industries
Online Gaming

Player deposits that clear —
without card decline roulette.

Gaming operators fight card blocks, issuer declines, and punitive MCC pricing. StixBNK initiates account-to-account deposits through PSD2 open banking and ACH/SEPA where licensed — players authenticate at their bank, you get real-time status events per player reference, and settlements reconcile on T+5 in fiat or USDC.

Talk to sales Get API keys
↑ approval Bank-first flows for players who prefer A2A
SCA Strong authentication performed by the ASPSP
Per player Deposit reference mapped to wallet ID
T+5 Operator settlement · fiat or USDC

The problem

Why online gaming merchants leave card rails.

01

Issuer blocks on gaming MCCs

Major card issuers decline or flag gambling transactions outright. Players with funds in their account still fail at checkout — support tickets spike on Friday nights.

02

Card deposit limits frustrate high rollers

Daily card caps of €500–€2,000 push VIP players toward slow wire transfers. Manual crediting delays seat them at competitors with faster funding.

03

Opaque payouts slow compliance reviews

Batch card refunds and lump-sum wires lack per-player references. AML teams spend days matching withdrawal queues to ledger entries.

Payment flow

How StixBNK handles online gaming checkout

  1. 01

    Licensed-market KYB

    Submit gaming licence, entity structure, and target markets during onboarding. StixBNK maps coverage to live provider availability — not a static marketing PDF.

  2. 02

    Player opens cashier

    Cashier UI calls your backend; you POST a collection with player ID, amount, currency, and redirect URL. Reference format is enforced at initiation.

  3. 03

    Bank selection and SCA

    Hosted checkout lists ASPSPs for the player's country. They authorise in-app; instant rails confirm in seconds on supported banks.

  4. 04

    Wallet credit on webhook

    Authorised status triggers your ledger credit. Player ID, amount, and bank metadata arrive in one normalised event — no PAN data in your stack.

  5. 05

    Operator settlement T+5

    Treasury receives aggregated payout in fiat or USDC on T+5. Per-deposit references remain in your reconciliation export for AML and finance.

Licensed sportsbook

Friday-night deposit surge — €250 player top-ups

A UK-licensed operator sees 35% card decline rates on deposits during peak match hours. They add Pay by bank for players with supported UK banks.

  1. Player selects €250 deposit; backend creates collection ref PLR-9918234.
  2. Hosted checkout shows Barclays, HSBC, NatWest; player picks NatWest and completes app-based SCA.
  3. Webhook authorised in 8 seconds; wallet credited; player places bet before half-time.
  4. No card MCC block — funds confirmed via open banking, not card authorisation.

Outcome: Deposit completion rate on bank-first cohort rises above card path. Support tickets for "payment failed" drop during peak windows.

Casino VIP

High-value deposit — €5,000 without card velocity limits

A tier-1 player hits the €2,000 daily card cap. VIP desk offers a Pay by bank link with pre-filled amount and player reference.

  1. VIP agent generates payment link tied to player ID VIP-4421 and €5,000.
  2. Player opens link on mobile, selects German bank, authorises via PSD2 SCA.
  3. Compliance sees payer bank, timestamp, and player ref in one audit log entry.
  4. Settlement to operator account on T+5 in EUR fiat; player wallet credited on authorisation.

Outcome: VIP funds same session instead of waiting 24–48h for wire confirmation. Compliance audit trail is per-transaction, not batch.

Stack

Products online gaming teams run on

01

Open banking routing

Player deposit initiation with market-aware routing, fallbacks, and one webhook contract across EU, UK, and ACH corridors.
02

AML transaction monitoring

Enrich deposit events with payer bank metadata for faster AML review — per-player references, not opaque batches.
03

Open banking compliance

Licensed-market routing with PSD2-aligned initiation flows — operational coverage map, not a brochure.

FAQ

Common questions from online gaming operators

Which gaming markets do you support for deposits?

Coverage depends on your licence and our live provider map. During KYB we align your target jurisdictions to enabled banks — you see availability before go-live, not after integration.

Can we map every deposit to a player ID?

Yes. References are set at collection creation and flow through webhooks and settlement exports. Your ledger, AML, and finance teams see the same player ID on every event.

Do bank deposits avoid card chargebacks entirely?

On A2A rails there is no card chargeback mechanism. Player disputes follow banking rules — a different regime than Visa/Mastercard reason codes on CNP deposits.

Discuss gaming deposit routing for your licensed markets.

Request a demo