Derived dataset · ICP #1

iGaming payment providers (PSPs)

Which payment methods and rails an operator accepts, and how many operators accept each one. Crypto, cards, e-wallets and alternative methods, for payment vendors selling into iGaming.

20 distinct payment methods across 6 rail categories, on 2,464 of the 20,774 indexed operator domains, seen 2026-05-01 to 2026-08-28. A method counts once per operator. An operator listed with none had none on its deposit page at that time.

API reference → Request access →

What each PSP record surfaces

Operator coverage

Operators accepting this method, sliced by license issuer and geography.

Rail mix

Crypto / fiat / e-wallet / open-banking breakdown across the operator footprint.

Geographic overlap

Markets and currencies where this method appears most often.

Dated shifts

Each operator-method observation carries first seen, last seen and last confirmed, so an added rail reads differently from a standing one.

Questions you can answer

Which MGA-licensed operators accept crypto?: Combine the MGA jurisdiction with the crypto payment category. The answer lists the operators that match both.
Which operators that target Brazil accept local payment methods such as Pix?: Combine the Brazil market with the local payment methods category.
Which operators accept Skrill?: Search by the name of one payment method to list the operators that accept it.
Which payment methods does one operator accept?: Look up the operator's domain to see the payment methods on its site.
Where do I ask these questions?: In the API, the CLI or Claude. Start with the number of matching operators, then open the operators you need.

Payment categories

Cards

Visa, Mastercard and other card schemes.

Crypto

Bitcoin, Ethereum, USDT and other coins.

E-wallets

Skrill, Neteller, ecoPayz and similar wallets.

Bank transfer

Wire transfers.

Open banking

Trustly and other instant bank payments.

Local methods

Methods of one region, such as Pix in Brazil.

API surface

GET  /v1/companies/search   discovery faceted by payment_category; returns company_ref
GET  /v1/companies/resolve  authoritative profile by company_ref or signal

Method canonicalization (e.g. "USDT TRC20" → "crypto · USDT") via the supplier-aliases table — see API docs.

Where does your rail land?

Request a sample PSP profile or kickoff API access for your prospecting workflow.

Request access →