High-Risk LicensingHigh-Risk Licensing
Home / Payments and banking / PSP

Payment Systems for Online Casinos: Choosing a PSP and Getting Connected

Introduction

A gambling licence does not by itself guarantee access to a payment service providerPSP means Payment Service Provider. A PSP helps an operator accept deposits, process payments, settle funds, manage refund logic, chargebacks and reserves and, in some models, handle payout flows., acquiring, or a settlementSettlement is the transfer of funds from a PSP, acquirer, EMI or payment processor to the operator’s settlement account. account. For the payment chain, what matters is not only whether a licence exists, but also which company accepts players’ funds, which entity is the contracting party with the player, which countries the project serves, whether the licence matches the actual product, and how deposits, refunds, payouts, and settlements are structured.

For the founder of an online casino, the practical route starts not with searching for a “PSP for gambling,” but with defining the project’s own model. Before approaching a provider, the operator should identify the licensee, the Merchant of Record, target and excluded markets, domains, expected payment methods, participants in the payment chain, and the company to which settlement funds should be paid. These details should then be brought into one consistent version across the licence, website, Terms and Conditions, corporate documents, and due diligenceDue diligence is the comprehensive review of a company, licence, domains, UBOs, payments, agreements, liabilities, suppliers, complaints, operating history and reputation before a transaction. materials.

Analytical conclusion Successful onboarding depends on a combination of four factors: whether the business itself is acceptable to the specific payment chain, the transparency of the corporate structure, the legality of operating in the target marketsTarget GEO means the countries that the operator genuinely targets through advertising, website language, affiliates, payment methods, SEO, support or bonus campaigns., and the operator’s ability to demonstrate that the declared model matches the actual flow of funds. One strong element, such as a licence, does not compensate for inconsistencies in the others.

What payment solutions does an online casino need?

The phrase “payment system for an online casino” is often used to mean everything at once: the payment form on the website, the PSP, acquiring, the bank account, and player payouts. To build a workable structure, these functions need to be separated.

A payment service provider (PSP) may provide the operator with one or more services: technical integration of payment methods, transmission of payment data, transaction routing, interaction with an acquirerAn acquirer is the bank or payment institution that enables a merchant to accept card payments., settlements, or additional payment-management tools. However, the commercial label “PSP” does not by itself determine the company’s legal or regulatory status.

Some providers are licensed payment institutions or electronic money institutions. Others perform primarily a technical function and operate through banks, acquirers, or other regulated participants. Therefore, when selecting a provider, the operator should establish not only its trading name, but also the exact legal entity, its contractual role, and its actual position in the payment chain.

Rule / condition The presence of terms such as PSP, payment gateway, payment platform, or processing on a company’s website does not by itself confirm that the company is authorised to accept or hold the operator’s funds. Regulatory status must be assessed by reference to the service actually provided and the applicable law.

For an online casino, it is useful to distinguish at least the following roles.

Participant Primary function What the operator should establish
Contracting party with the player Provides the gambling service to the player and assumes the contractual obligations towards the player Which company is named in the Terms and Conditions, who accepts the wager, and who is responsible for the gaming balance and payout
Merchant of Record Acts as the merchant in the payment transaction and assumes the corresponding obligations within the payment chain Which company is registered as the merchant, in whose name the merchant identifier is opened, and who is responsible for refunds and disputes
Payment gateway Technically transmits payment data and requests between the website and subsequent participants Whether it only transmits data or also participates in routing, processing, or settlement
Payment service provider (PSP) Organises one or more parts of payment processing Which legal entity provides the service, what exactly it does, and through whom acquiring and the movement of funds are arranged
Acquirer Connects the merchant to the card payment chain and assumes acquiring responsibilities Who the actual acquirer is, for which merchant the acquiring relationship is established, and whether its model accepts the specific product and markets
Bank or other settlement institution Services the account and settlements within the scope of its permitted activities In whose name the account is opened, where the funds come from, who is authorised to control them, and how the settlement company is connected to the operator
Alternative payment method provider Services a specific local or international payment method Whether the rules of that payment method allow gambling and the declared countries
Payout provider Technically or financially facilitates withdrawals to players On whose behalf the payout is made, where the funds come from, and whether this model is aligned with the rest of the payment chain

One company may perform several roles. Conversely, a single PSP brand may offer the operator a solution in which separate functions are in fact performed by several legal entities.

The onboarding structure should therefore show two different things.

The first is payment processing: who receives the request from the website, passes it on, receives the authorisation decision, and returns the result to the operator.

The second is the flow of funds: where the funds actually come from, through which participants they pass, where settlement with the operator takes place, and where refunds and payouts are made from.

These two flows are connected, but they are not the same. A technical gateway may participate in transmitting a payment message without becoming the holder of the funds. Conversely, a settlement participant may receive or transfer funds without providing the operator with the customer-facing payment form.

Practical conclusionA strong licence cannot rescue a weak structure. Before negotiating pricing, the operator should prepare two one-page diagrams: the payment-data flow and the flow of funds. For each link in the chain, the diagram should identify the legal entity, its function, and the contract under which it participates. This makes it possible to identify inconsistencies before they are discovered during PSP or acquirer due diligence.

The Merchant of Record requires particular attention. It cannot be identified solely by looking at which company is described as the “payment agent” or named in a single agreement. The operator should compare the contracting party with the player, the information shown on the payment page, merchant registration, the settlement account, how the transaction appears on the bank statement, responsibility for refunds and disputes, and the actual economic role of the companies involved.

Red flag The Terms and Conditions identify one company as the operator, the payment application identifies another company as the merchant, while settlement funds are paid to a third company without a clear contractual basis. Such a structure requires explanation before an application is submitted, not after the due diligence team asks about it.

A separate settlement or payment company within the group does not by itself indicate a violation. The relevant questions are why it participates in the chain, whether its role is consistent with the contracts and applicable regulation, and whether that role has been fully disclosed to the bank, PSP, and acquirer.

PSP requirements for the licence, company, and target markets

The first substantive question in the review of an online casino is not simply “is there a licence?”, but what exactly the licence permits, which company it covers, which product it covers, and in relation to which markets.

Card-scheme rules confirm that the legal status of remote gambling activity is independently relevant. For example, current Mastercard rules require the acquirer, before acquiring remote gambling transactions, to register the relevant merchant and obtain gambling-licensing documentation for the applicable jurisdictions.[1] This does not mean that a single licence automatically makes the operator acceptable in every country or obliges a particular acquirer to onboard the project.

Verified fact Mastercard Security Rules and Procedures — Merchant Edition, in the version dated 4 August 2026, section 9.4.2, provides for the registration of a merchant for remote gambling transactions and for the acquirer to obtain documentation of a gambling licence for each applicable jurisdiction.[1]

For the operator, this leads to a broader practical question: does the declared payment model match the legal structure of the project?

A PSP or acquirer may compare the licensee with the company identified on the website; review the domains and the actual product; identify ultimate beneficial owners and controlling persons; analyse target markets and restrictions; and establish which company accepts funds and where payouts will be made from. The scope of the review depends on the particular provider, its role, the acquirer, the banking chain, and the applicable law.

A licence from one jurisdiction is also not a universal authorisation to operate with players worldwide. For payment due diligence, what matters is not only the jurisdiction that issued the licence, but also the legal status of offering the product in the player’s country.

Accordingly, saying “we operate under an offshore licence” is not enough. The provider needs a more precise answer: who the licensee is, which product the authorisation covers, which domains belong to the project, where players are acquired from, and which markets are excluded.

Analytical conclusion For a PSP, the geography of the business forms part of the overall risk profile. The licensing jurisdiction, the company’s jurisdiction, and the player’s jurisdiction answer different questions. The permissibility of accepting players in a particular market cannot be inferred solely from the fact that the operator holds a valid foreign licence.

It is particularly important that information about the company, licence, domains, and markets does not conflict across different sources.

Element What must be established What it should be compared against
Operating company Full legal name, registration details, and role in the project Corporate register, licence, Terms and Conditions, PSP application
Licence Licensee, type of authorisation, covered product, and current status Official register or regulator document, actual product, application
Domain Which websites are used to offer the product and relate to the licensed activity Licensing perimeter, website, PSP application, technical integration
Target markets Where the operator accepts players and where it actively markets the product Country legal matrix, website, advertising, payment methods, restriction settings
Contract with the player Which company provides the service and assumes obligations towards the player Terms and Conditions, refund and payout policy, licence
Recipient of funds Which company is the merchant and where settlement funds are actually paid PSP/acquirer agreement, merchant registration, settlement account, flow-of-funds structure

This table does not require the same legal entity to appear in every row. A group structure may be more complex. However, every difference should have a clear legal and operational rationale.

For example, the licensee may use an external technical provider, a separate acquirer, and a bank account in another jurisdiction. That does not by itself indicate a problem. A problem arises when the roles cannot be reconstructed from the documents or when the actual flow of funds conflicts with the disclosed model.

Red flag A company is used to accept players’ funds solely because the principal operator cannot pass due diligence, while the actual gambling activity, the role of the licensee, or the origin of the transactions is not disclosed to the payment partner. This is not a way to “improve the payment architecture”; it creates a risk of misrepresenting the merchant and the nature of the transactions.

Geography must also be reviewed separately. It is not enough for the operator to maintain an internal list of prohibited countries. The declared model must match the actual product: registration availability, advertising, affiliate trafficAffiliate traffic is traffic originating from affiliates, partner websites, review portals, Telegram channels, streamers, influencers or other partner sources., language versions, payment methods, and technical restrictions.

At the same time, one technical signal does not provide the full picture. IP address, document country, residential address, country of issuance of the payment instrument, and other data may not match. The specific set of checks depends on the law, the licence, the payment partner, and the operator’s risk model.

Practical conclusion Before approaching a PSP, target markets should be divided into at least three groups: markets the project intends to actively serve; markets where additional legal analysis or conditions are required; and excluded markets. For the first group, the operator should be able to explain not only why it considers the activity permissible, but also how that position is implemented on the website, in advertising, and in the payment architecture.

Merchant profile and documents for onboarding

PSP due diligence begins well before the operator submits a full archive of corporate documents. The provider first needs to understand what kind of business this is and whether it falls within the provider’s risk appetite in principle.

For this purpose, it is useful to prepare a concise merchant profileA merchant profile is a structured description of the business for a PSP, covering the company, licence, product, target markets, UBOs, traffic sources, AML/KYC, refund logic, chargebacks, volumes, payment methods, suppliers and risk controls.: a structured description of the project that allows the PSP or acquirer to understand the legal and commercial model without reviewing dozens of disconnected files.

Such a profile does not replace due diligence on the company and its ultimate beneficial owners. Its purpose is to give the reviewing party one consistent starting version of the project.

Project Passport for the PSP

For an online casino, the profile should normally explain:

Company
which company is the operator and where it is registered;
Licence and product
which licence is used and which product it covers;
Target markets
which markets are targeted and which are excluded;
Domains and brands
which domains and brands belong to the project;
Payment methods
which payment methods are required;
Deposits and payouts
how deposits and payouts are structured;
Volumes and currencies
which volumes and currencies are expected;
Crypto-assets
whether crypto-assets or other additional payment rails are used;
Provider task
what service the operator is seeking from the provider.

This should not become a marketing presentation. For due diligence purposes, an accurate description of the actual model, including its limitations, is more useful than a claim that the business is a “fully compliant international casino.”

Practical conclusion The concise profile should be prepared before collecting documents at scale. If two or three pages do not make it clear who the operator is, who receives the funds, where the players are located, and what exactly is required from the PSP, a full document package will most likely only increase the number of inconsistencies.

Following the preliminary assessment, the provider may request documents to review the company and the business. The exact list depends on the provider’s role and internal procedure, but the logic of the review usually comes down to several questions.

Five Questions in Project Review

Who controls the project
Who controls the project. Corporate documents and information about ultimate beneficial owners, directors, and authorised persons are used for this purpose.
Legal basis
Does the project have the stated legal basis for its activities. This involves reviewing the licence, the licensed entity, domains, product, and business geography.
Website and application
Does the actual website match the application. The reviewing party may compare the Terms and Conditions, Privacy Policy, payout and refund rules, responsible gamblingResponsible gambling is the set of rules and processes intended to protect players, including limits, self-exclusion, monitoring of harmful behaviour, age verification, complaint handling, transparent bonus terms and harm prevention. information, age restrictions, and other user-facing documents against the application data.
Flow of funds
Is the flow of funds clear. The provider needs to understand who accepts the deposit, where settlement is made, where payouts are made from, and what function each intermediary company performs.
Risk management
Can the operator manage risk after onboarding. Policies alone are therefore not enough: depending on the model, evidence may be required showing how customer verification, sanctions screening, fraud prevention, dispute handling, and change management work in practice.

Analytical conclusion The purpose of due diligence is not to collect the largest possible number of documents. The purpose is to determine whether the corporate documents, licence, website, agreements, payment application, and actual operating model describe the same business.

This is why the quality of the package is determined primarily by consistency.

If the application identifies company A as the licensee, the licence is issued to company B, the Terms and Conditions establish a contract with company C, and the funds are expected to be received by company D, the project does not become transparent merely because registration documents have been provided for all four companies.

The differences may be lawful and explainable. For example, separate companies may own intellectual property, provide technology, or perform permissible settlement functions. However, the role of each company should be defined in advance and should not conflict with disclosures made to players and payment partners.

Rule / condition Every company that appears between the player and the final settlement with the operator should have an identifiable function. If that function affects the acceptance, holding, transfer, or payout of funds, its contractual and, where applicable, regulatory basis should be established separately.

Before the first full application, the operator should conduct a consistency review: take the information about the company, licence, domains, markets, contracting party with the player, and recipient of funds, and check it simultaneously against the website, corporate documents, licensing materials, payment application, and the intended flow-of-funds structure.

This approach allows the operator to correct the structure and documents before due diligence begins, rather than provide different explanations after each new PSP question.

Red flag The business description should not be adapted to the assumed preferences of a particular bank or PSP if doing so conceals the gambling activity, the actual product, the target market, the Merchant of Record, or a participant in the flow of funds. Sustainable onboarding requires one verifiable version of the project that matches the actual activity, not a “convenient version” of it.

Operator review and PSP onboarding

Once the operator has identified the licensee, Merchant of Record, target markets, and flow-of-funds structure, the actual onboarding process begins. This is not a single decision that “the PSP approved the project,” but a sequence of reviews that may involve the payment service provider itself, the acquirer, the settlement bank or electronic money institution and, for card payments, participants in the relevant payment scheme.

The process usually begins with a preliminary discussion. At this stage, the provider needs to understand the product, licence, player countries, currencies, expected turnover, average transaction value, payment methods, and required payout model. For an operating business, its payment-processing history is also relevant: volumes, refunds, disputed transactions, fraud, and the reasons why relationships with previous providers ended, if there were any.

Initial interest from the provider does not yet mean approval. The next stage is a review of the operator itself and an assessment of payment risk. The merchant profile prepared earlier becomes an evidence base: corporate and licensing documents are compared against the website, product, payment model, financial forecast, and actual controls.

Practical conclusion It is useful to separate two questions. First: is the provider willing in principle to work with this type of business, licence, and geography? Second: is it willing to accept this particular operator, with its expected volumes, payout structure, history, and financial risk? A positive answer to the first question does not replace the second.

During due diligence, the operator will usually need to explain not only its legal structure but also the commercial payment model. The provider needs to understand expected monthly turnover, the number and average size of deposits, main currencies, the proportion of new and returning customers, forecast refunds and disputes, player payout volumes, peak loads, and available liquidity. For a new project, some metrics will necessarily be forecasts, but the assumptions should be internally consistent: the operator cannot simultaneously declare a modest initial turnover while providing a settlement model designed for a payment flowPayment flow is the map of how funds move: who accepts the deposit, where funds are held, who performs settlement, and how withdrawals, refunds, chargebacks, crypto conversion and reconciliation are handled. many times larger.

After the risk review, the parties agree the commercial and operational terms: which payment methods will be available, in which countries and currencies, which company will be registered as the merchant, how transactions will be identified, where settlement funds will be paid, what fees and reserves will apply, what transaction limits will be set, and how refunds and payouts will be handled.

For card onboarding, some requirements come not only from the particular PSP.

Verified fact Mastercard Rules dated 2 June 2026, § 5.1.1, require an acquirer, before entering into, extending, or renewing an agreement with a merchant, to verify that the merchant conducts bona fide business activity, has adequate account-data protection measures, and complies with applicable law.[2] This rule applies to the acquirer within the Mastercard system and is not a universal list of documents that every commercial PSP is required to request.

Mastercard imposes additional requirements for remote gambling.

Verified fact The current public version of Mastercard Security Rules and Procedures — Merchant Edition dated 4 August 2026 provides in § 9.4.2 that, before acquiring remote gambling transactions, the acquirer must register the relevant merchant with Mastercard and obtain and retain a copy of the gambling licence for each applicable jurisdiction. As a general rule, such remote gambling transactions are identified with MCCMCC means Merchant Category Code: the code used to classify a business for card-payment purposes. 7995; the document provides separate rules for certain registered categories.[1]

The expanded set of requirements that § 9.4.2 goes on to list for certain merchants in the United States and U.S. Territories cannot automatically be applied to an international offshore casino. For example, the specific requirements concerning evidence of legality, attestations, and independent certification in that part of the text have the territorial scope stated in the rules.

Visa also sets specific rules for online gambling.

Verified fact Visa Core Rules and Visa Product and Service Rules dated 18 April 2026, § 5.8.18.1, require an online gambling merchant to hold a valid licence or other appropriate authorisation to operate the relevant website or application and to identify an online gambling transaction as MCC 7995. The additional Quasi-Cash/Online Gambling Transaction indicator in that provision is expressly specified for the AP, Canada, CEMEA, LAC, and US Regions, so it should not be described without qualification as an identical global requirement for all Visa regions.[3]

These rules do not turn a card scheme into an authority that grants the operator permission to operate in a particular country. They set the requirements of the relevant payment scheme. Whether gambling may lawfully be offered to a player must be assessed separately under the applicable law, licence, and contractual model.

What happens after the review

If the legal and risk review is passed, the project proceeds to contracting and technical integration. At this stage, the contractual parameters and technical setup should describe the same model: the merchant legal entity, currencies, countries, transaction identification, permitted payment methods, settlement account, refunds, and payouts should not differ from what was approved during due diligence.

Before a full launch, the entire transaction lifecycle should be tested. A successful response from a test payment gateway is not enough. The team should see how the transaction is authorised and recorded internally, how it appears in the provider’s report, how settlement is generated, how a permitted refund is processed, and how the approved payout model operates.

The review does not end after launch. The commercial agreement will typically impose obligations to notify the provider of certain changes and allow the provider to reassess the terms if the risk changes. Card schemes also use their own monitoring mechanisms.

For example, current Visa Rules in § 10.4.3.1 provide for the Visa Acquirer Monitoring Program (VAMP): Visa may identify acquirers under the program criteria, require remediation of unusual activity, and assess risk, including at merchant or sponsored merchant level.[3] This is a Visa scheme rule, not a promise that every PSP will use identical thresholds or the same response process.

Analytical conclusion Onboarding is better understood as the beginning of an ongoing compliance regime rather than the completion of a one-off review. If the product, markets, merchant company, domains, payment page, or nature of the transactions changes after approval, the provider’s earlier decision should not automatically be treated as applicable to the new model.

PCI DSS and SAQ A: redirect and embedded payment form

Outsourcing card-data processing to an external provider can materially reduce the scope of the operator’s own obligations, but it does not mean that the casino website falls entirely outside PCI DSS.

It is particularly important to distinguish two common models correctly: redirecting the user to an external payment page and embedding an external processor’s form on the operator’s page.

Verified fact In FAQ 1588, the PCI Security Standards Council explains a specific SAQ A eligibility criterion relating to protection against script-based attacks on the webpage. This criterion applies to merchants that embed a third-party processor’s payment page or form, for example through an iframe. That particular criterion does not apply to a merchant that redirects the user from its website to the processor’s page.[4]

For an embedded form, FAQ 1588 provides two main ways to demonstrate compliance: the operator either uses measures to protect the page from script-based attacks, for example techniques related to PCI DSS requirements 6.4.3 and 11.6.1, or obtains the relevant confirmation from a PCI DSS-compliant third-party processor that provides the embedded form.[4]

However, this does not mean that a website using a redirect is exempt from external scanning.

Verified fact FAQ 1604, published by PCI SSC in June 2026, expressly confirms that the external scanning by an Approved Scanning Vendor (ASV) required under SAQ A applies to the relevant merchant webpages both where the user is redirected to a third-party processor and where an embedded iframe is used. The FAQ links this requirement to requirements 11.3.2 and 11.3.2.1 of SAQ A for PCI DSS v4.x.[5]

In other words, for SAQ A these two requirements should not be conflated:

  • the specific criterion concerning protection against script-based attacks in FAQ 1588 applies to an embedded form;
  • the ASV scanning of merchant webpages described in FAQ 1604 applies both to the redirect model and to the embedded iframe model.

The operator should confirm the correct SAQ and the final scope of the assessment with the organisation accepting the compliance validation, typically the acquirer or the relevant payment scheme. FAQ 1588 separately points to the need for such confirmation.[4]

Practical conclusion At the technical onboarding stage, the question should not be “we do not see card data, so PCI does not apply to us,” but rather “which payment acceptance method are we using, which SAQ applies to that architecture, and which elements of our website still remain within the scope of the applicable requirements?”

Fees, reserves, and settlement timelines

For a CEO, the cost of processing is not the same as a single percentage rate in a commercial offer. The economics of a payment channel consist of several types of cost and, just as importantly, liquidity constraints.

A processing fee reduces revenue. A reserve works differently: it may not be a final expense, but it temporarily removes part of the funds from available working capital. A settlement delay is also not a fee, but it increases the amount of money the operator has to finance itself.

It is therefore incorrect to compare two PSPs only by their processing percentage.

Parameter What it affects What to ask before signing
Processing fee Direct variable cost of accepted transactions What amount the fee is calculated on, and whether it differs by payment method, country, currency, or card type
Fixed transaction fee Particularly significant where the average deposit is small Whether it is charged only for successful transactions or also for certain declined attempts
Currency conversion Can materially change the actual cost of international processing Who performs the conversion, at what rate, and what additional fees apply
Payout fee Increases the cost of servicing players How the payout fee is calculated and whether it differs by method and currency
Refund May create a separate operational cost Whether the original fee is refunded and whether a separate refund fee is charged
Transaction dispute Creates administrative costs and may have additional consequences What fee applies to a dispute, when it is charged, and whether it is returned if the outcome is successful
Monthly minimum volume or fee Creates fixed costs at low turnover What exactly counts towards the minimum and how any shortfall is calculated
Rolling reserveA rolling reserve is a percentage of turnover temporarily retained by a PSP as protection against chargebacks, refunds, fraud and regulatory risk. Reduces current liquidity What percentage is withheld, for how long, on what release schedule, and for which obligations it may be used
Fixed reserve or security balance Freezes a predetermined amount How the amount is set, when it must be replenished, and when the funds are returned
Settlement frequency Determines how quickly funds reach the operator What the stated settlement period means, which event starts the period, and which days are excluded
Settlement delay or additional hold Increases working-capital requirements In what circumstances the provider may suspend or extend settlement
Negative balance and set-off Determines which funds are used to cover obligations Whether the provider may withhold amounts from future settlements or the reserve
Hold after termination Affects liquidity after the channel is closed How long the reserve may be retained, which claims may be covered from it, and how the final reconciliation is carried out

The exact amounts and timelines are determined by the agreement and commercial offer for the specific payment chain. There is no universal “normal fee” or “standard reserve for casinos.”

Why a reserve should be calculated separately from the fee

If the agreement provides for a rolling reserve, part of each settlement is temporarily withheld to secure future obligations. Economically, this differs from a fee: the fee is normally an expense, whereas the reserve, subject to the contractual conditions, should be released according to the agreed schedule after permitted deductions.

For the operator, however, the main issue is liquidity. Money that may be returned several months later cannot at the same time be used for current player payouts, marketing, or operating expenses.

Rule / condition In the financial model, the reserve should be reflected in two places: as a reduction in current cash flow and as a future receivable if the agreement actually provides for its subsequent release. Treating the reserve as an ordinary fee is just as incorrect as treating it as immediately available cash.

A hypothetical example illustrates the difference.

Assume, solely for illustration, that 100,000 monetary units were successfully processed during a settlement period. The agreement provides for a 3% processing fee and an 8% rolling reserve. If currency conversion, refunds, disputes, payouts, and other fees are temporarily excluded, 3,000 becomes a processing expense, another 8,000 is temporarily withheld in reserve, and the settlement amount before other adjustments is 89,000.

This is not a benchmark for market rates. The figures of 3% and 8% are used only to demonstrate the arithmetic. In a real project, only the contractual figures should be used.

The settlement period is not the same as the fund-release period

A commercial designation such as T+N usually describes one element of the settlement cycle. It does not automatically answer questions about the reserve, weekends and banking days, currency conversion, disputed amounts, negative balances, or additional holds.

The agreement should therefore establish separately:

  • when a transaction is considered accepted for settlement;
  • how the settlement batch is formed;
  • when the PSP or acquirer transfers the net amount;
  • when the bank actually credits it to the operator;
  • when each portion of the reserve is released.

Analytical conclusion Two offers with the same percentage fee may have entirely different economics. A longer settlement cycle, a high reserve, expensive payouts, or unfavourable currency conversion may have a greater financial effect than the difference in the base processing rate.

What happens to the reserve after the agreement is terminated

Closing a payment channel does not necessarily mean the immediate return of all withheld funds. If the agreement allows the reserve or another security balance to be retained to cover future refunds, disputes, a negative balance, or other specified obligations, part of the funds may remain withheld after new transactions stop.

The duration and grounds for such a hold are contractual parameters. They should not be replaced with a universal number of months.

Before signing the agreement, the operator needs to understand when the hold period starts, how individual portions of the reserve are released, which obligations may be set off, whether the provider may change the amount of security, and how final reconciliation is carried out.

Practical conclusion When comparing offers, it is useful to calculate not only the cost of one successfully accepted deposit, but also the maximum amount of the operator’s own money that the business must have to operate normally under the applicable reserve and ordinary settlement delay.

Deposits, payouts, and the banking chain

An online casino’s payment model should distinguish at least four types of movement of funds: a player deposit, a refund, a payout of winnings or an available balance, and settlement by the payment chain with the operator.

They have different economic meanings and should not be recorded in the system as interchangeable transactions.

Flow What happens Where the funds move What the operator should be able to evidence
Deposit The player fundsPlayer funds are money and other amounts owed by the operator to players, including account balances, confirmed winnings and payments that must be made under the applicable rules. the gaming balance using an approved method From the player’s payment instrument into the agreed payment chain The player, transaction, amount, currency, payment method, and its connection to the gaming records
Refund A previously accepted amount is returned in relation to the corresponding transaction Back through the permitted refund mechanism The original transaction, the basis for the refund, and the corresponding amount
Player payout The player receives winnings or another available balance that is due for payment From the approved source of payout to the player through an authorised channel The player’s entitlement to the payout, completion of the required checks, and the link between the payout and the account
Settlement to the operator The acquirer, PSP, or another agreed participant transfers net settlement funds to the operator From the payment chain to the disclosed settlement account The composition of the settlement batch, fees, reserve, refunds, disputes, conversion, and the final amount

A deposit is not a settlement to the operator

When a player makes a successful deposit, this does not mean that the corresponding amount is already in the operator’s bank account.

The transaction first passes through the agreed authorisation and processing chain. It may then be included in a settlement batch. Fees, the reserve, refunds, disputed amounts, and other contractual adjustments may be deducted from the total. Only after that is the agreed net amount transferred to the operator.

This is why the volume of processed deposits and the actual receipt of funds in the bank account cannot be treated as interchangeable metrics.

Analytical conclusion The operator may have several different figures at the same time: the volume of successfully processed deposits, the amount awaiting settlement, the amount held in reserve, the amount of disputed transactions, and the amount already available in the bank account. For liquidity management, what matters is not the largest of these figures, but the portion of the funds the operator can actually use.

A refund and a payout of winnings are not the same thing

A refund corrects or reverses a previously processed payment transaction. A payout of winnings fulfils the operator’s obligation to the player. It is incorrect to use one process in place of the other merely because, technically, funds are being sent back to the customer in both cases.

This distinction is expressly reflected in card-scheme rules.

Verified fact Mastercard Rules dated 2 June 2026, § 5.1.2.1, expressly prohibit the use of a refund transaction to credit winnings or value usable for gambling to a Mastercard or Maestro Account. The same provision separately explains that the return of unused funds from the original transaction, or a refund made in connection with a cardholder fraud claim subject to the specified conditions, is not a payout of winnings.[2]

The public Mastercard Rules refer the procedure for card-based payouts of winnings to the Gaming Payment Transaction rules and the separate Mastercard Gaming and Gambling Payments Program Standards. A universal technical route for every Mastercard payout therefore cannot be inferred from the general public rule without checking the applicable programme and agreement.[2]

Visa uses a different formulation in its public rules.

Verified fact Visa Rules, § 5.8.18.3, require gambling winnings to be paid to a Visa cardholder by means of an Original Credit Transaction (OCT). For the Europe Region, there is an additional requirement that the OCT for winnings be sent to the same payment credential used for the winning wager.[3] This is an additional regional Visa rule, not a universal requirement for every payout method or every payment scheme.

This leads to an important practical principle: the operator needs separate logic for deposits, refunds, and payouts. Even where the user sees all three actions in one payment section of the account interface, they may represent different types of transactions with different rules on the PSP and acquirer side.

Player funds are not the same as the available PSP balance

One of the most dangerous mistakes in a financial model is to treat the balance shown in a payment provider’s dashboard as equivalent to freely available cash.

The interface may simultaneously show processed transactions, unsettled amounts, funds held in reserve, amounts subject to delayed settlement, and the balance available for transfer. The names of these figures depend on the particular system, so their meaning should be checked against the agreement and settlement documentation.

At the same time, liabilities to players exist independently of the bank balance. If a player has a balance due for payout, that obligation does not disappear because the acquirer has delayed settlement or part of the incoming funds is held in reserve.

Practical conclusion The treasury model should answer a simple question: can the operator meet player obligations that are due for payment if settlement inflows from the main channel temporarily slow down? The answer cannot be based solely on the current balance shown in the PSP dashboard.

How to reconcile the banking chain

Every settlement received in the operator’s account should be reconcilable with the reporting from the payment channel.

At management-accounting level, the operator should be able to trace backwards from a bank receipt to the settlement batch and from the batch to individual transactions. The difference between the gross volume of processed payments and the bank receipt should be broken down into understandable components: fees, reserve, refunds, disputed transactions, conversion, and other contractual adjustments.

This is particularly important where the technical provider, acquirer, and settlement institution are different legal entities. A bank receipt may come from a legal entity other than the brand the operator sees in the dashboard, but the actual chain and the basis for that settlement should be disclosed and consistent with the contractual structure.

Red flag If the operator cannot explain why players’ funds are accepted on behalf of one entity, settlements arrive from another, and payouts are made through a third, and those roles do not follow from the disclosed contractual model, it is risky to continue scaling that channel without clarifying the structure.

This does not mean that a lawful payment chain must always involve only one legal entity. The requirement is different: every participant in the movement of funds should have a clear, disclosed, and agreed role.

Opaque payment structures: risks for the operator

A complex payment structure is not in itself a violation. An online casino may use a payment service provider, an acquirer, a payment facilitator, an electronic money institution, a separate payout provider, or a crypto provider. Models in which several merchants are serviced through a payment facilitator or aggregatorAn aggregator is a B2B supplier that combines games, payments, data feeds, KYC tools or other services from multiple providers into a single integration. may also be permissible.

The risk arises not from the number of participants, but from discrepancies between the business that is actually being serviced, who the merchant is, how the transaction is identified, and what has been disclosed to the acquirer and other participants in the chain.

An opaque structure therefore cannot be identified by a single external feature. Person-to-person (P2P) transfers, an aggregator, a crypto payment, or a separate settlement company do not become unlawful merely because of the name of the model. The specific function of each participant, the contractual basis, the applicable regulation, and whether the actual structure has been agreed with the provider must be established.

Incorrect transaction category

For card payments, the merchant category is not an arbitrary technical field.

Verified fact Visa Rules dated 18 April 2026 require online gambling to be identified as MCC 7995 even where gambling services are not the merchant’s primary activity. Mastercard, in the current version of Security Rules and Procedures — Merchant Edition dated 4 August 2026, also provides for MCC 7995 as the general code for remote gambling transactions, while certain registered models are subject to other specific categories.[1][3]

If actual casino activity is processed under the category of another product or service without an appropriate basis, the issue is not merely a “technical setup.” The acquirer receives an inaccurate representation of the nature of the transactions on which its due diligence, monitoring, and risk-acceptance decision are based.

For a CEO, the practical question is simple: does the merchant category correspond to the product the player actually purchases or uses?

Hidden Merchant of Record

Earlier, we distinguished the contracting party with the player, the Merchant of Record, and the technical participants in processing. In practice, risk arises when these roles diverge without a disclosed basis.

For example, the website and user agreement may identify one operator, while the acquiring relationship is set up for another entity that is presented as an independent merchant even though it does not in fact provide the declared service. The mere involvement of a second company proves nothing by itself. Its actual function and whether the payment chain is aware of it must be established.

Mastercard uses the specific concept of Merchant Transaction Laundering within MATCH Pro. In the current version of Security Rules and Procedures — Merchant Edition, § 11.14.1, reason 03 relates to a situation in which a MATCH Merchant submits transactions arising from card acceptance outside a valid Merchant Agreement between the acquirer and the merchant.[1]

Rule / condition Not every multi-layered payment structure should be called transaction laundering. This term has a specific context in Mastercard rules. However, the operator should treat it as a critical risk if transactions passing through its merchant connection do not correspond to the agreed merchant, product, or contractual model.

Undisclosed company receiving settlements

The company identified to the player and the company into whose account settlement funds are paid do not necessarily have to be the same in every permissible structure. For example, the contractual model may provide for a payment facilitator or another settlement participant.

But the difference must be explainable.

Before launch, the operator needs to understand:

who is legally entitled to receive the relevant funds; under which agreement; whether the acquirer is aware of the model; whether the bank account corresponds to the declared settlement chain; how the funds are reconciled to specific transactions; and how obligations to the operator and players are performed after settlement.

Red flag The PSP presents the operator with one brand and one agreement but does not explain why settlements will be received from or through another legal entity, while the origin of that company and its role cannot be reconstructed from the documents.

This does not automatically mean that the settlement is unlawful. It means that the operator does not yet understand its own payment chain well enough to accept the corresponding risk.

Shared MID, aggregator, and Sponsored Merchant

Another area where it is easy to reach the wrong conclusion is the use of shared infrastructure.

The involvement of an aggregator does not automatically mean that the merchant is being concealed. Mastercard Rules expressly provide for a Payment Facilitator and Sponsored Merchant model. Under this model, the Payment Facilitator enters into the agreement prescribed by the rules with the Sponsored Merchant on behalf of and as agent for the acquirer, maintains information about such merchants, and conducts ongoing monitoring of them. Mastercard Rules also expressly allow the contractual withholding of funds for chargebackA chargeback is a card transaction disputed by the player through the player’s bank or card issuer. reserves and similar purposes.[2]

Accordingly, the question is not whether the MID is “shared,” but what the model actually is.

The operator should establish whether it is registered as an independent merchant or as a Sponsored Merchant, which entity acts as the Payment Facilitator, who its acquirer is, which identifier is assigned to the operator’s transactions, and whether the upstream participant sees the actual product.

Analytical conclusion A shared technical routing arrangement may be a legitimate part of an aggregator model. Opacity arises where the casino believes it is operating within an agreed aggregator structure, while in reality transactions are mixed with other businesses without clear registration, identification, and contractual basis.

The same principle applies to crypto, alternative payment methods, and P2P mechanisms: the actual function and legal regime should be identified first, and only then should the permissibility of the specific structure be assessed.

Reasons for refusal by a PSP

A PSP refusal does not always mean that the project is legally or technically structured incorrectly. The provider may simply not accept the relevant type of licence, the company’s country of registration, certain target markets, or gambling as a risk category.

The first task after a refusal is therefore to distinguish between the policy of the particular provider and a defect in the project itself.

In the first case, restructuring the corporate setup will not necessarily solve the problem: the operator approached a partner whose risk profile was not suitable for the project from the outset. In the second case, resubmitting the same model to another provider merely moves the problem further down the chain.

In practice, the reasons can be grouped around several questions.

The provider does not accept the model itself

A PSP, acquirer, or its banking partner may not service certain licences, products, merchant countries, or player markets.

This is a commercial or internal risk policy unless the restriction follows directly from law or the rules of the relevant payment scheme. A single refusal therefore does not justify the conclusion that “this licence is accepted nowhere.”

The disclosed information does not match

Inconsistencies between the licence, company, website, contract with the player, payment application, and actual recipient of funds are particularly serious.

Even if every legal entity exists and can provide corporate documents, an unexplained difference between them increases the number of questions around the structure.

The target markets are unclear

A project may provide a licence but still lack a consistent answer as to which countries it intends to accept players from and on what basis.

The problem is not only the absence of legal analysis. The provider may find that countries declared as excluded are in fact present in advertising, affiliate traffic, payment methods, or the user journey.

The controls are not evidenced

For an operating business, what matters is not only the policy on paper but also the history of its implementation. A new operator may not yet have historical metrics, but working processes should exist for customer verification, sanctions screening, fraud prevention, refund handling, and payouts.

The security of the card environment and the correctly defined PCI DSS scope are assessed separately. The SAQ A requirements for redirect and embedded-form models are addressed in the PSP onboarding section and should not be replaced with a general statement that “the PSP stores the card data.”

The financial model cannot absorb the onboarding terms

The provider may consider the projected turnover, average transaction value, geography, level of disputes, or expected payouts incompatible with its risk model.

For the operator, insufficient liquidity is a separate obstacle. Even a commercially acceptable offer becomes unsuitable if the reserve and settlement timelines leave the company without enough funds to meet its obligations on time.

The history of the merchant or related persons requires additional review

Acquiring due diligence is not limited to the new company.

Mastercard requires new merchants to be screened and subsequently monitored. The current version of Security Rules and Procedures — Merchant Edition also provides for re-screening, including where there is a change in the ownership, country, or nature of the business of the merchant or Payment Facilitator.[1]

A new company therefore does not necessarily create a “clean history” if its owners, activities, or related payment relationships point to an earlier risk profile.

Practical conclusion After a refusal, it is useful to classify it at one of three levels: incompatible provider policy; insufficient evidence; or a structural defect in the project. Only then should the operator decide whether to find another partner, supplement the application package, or restructure the model.

The same unprepared application should not be sent to dozens of providers in the hope that one of them will not ask the questions already raised by the previous acquirer.

How to assess a payment provider’s offer

The operator should verify not only whether a PSP is willing to accept the casino, but also who exactly is offering the payment service and whether that entity is capable of delivering the promised model.

A trading name does not answer this question.

A single brand may simultaneously offer a technical gateway, payment routing, acquiring through a partner, settlement services, and services provided by several regulated companies.

Rule / condition Regulatory status cannot be determined solely from the label PSP or “payment gateway.” A technical gateway that provides a software connection does not automatically become a payment institution. If a company actually provides a regulated payment service, its status and permissions should be checked under the applicable law of the relevant jurisdiction.

In the EU and EEA, the EBA maintains a central register of payment institutions and electronic money institutions based on data from national competent authorities.[6] In the United Kingdom, the FCA Financial Services Register shows authorised or registered firms and their relevant permissions.[7] These registers are useful only within their respective jurisdictional scope and are not a global catalogue of all technical PSPs.

What should be established before signing the agreement

Question Document or basis for verification Red flag
Which legal entity is entering into the agreement? Full legal name, registration number, address, corporate register, agreement The offer names only a brand; the legal entity appears only when an invoice is issued
What exactly does this entity do? Service description and agreement: gateway, processing, payment service, acquiring, settlement, payout All functions are described simply as “processing,” with no allocation of responsibility
Does it require regulated status, and does it have it? Official register and list of permitted services where the function is regulated A regulator’s logo without a register entry, or a permission held by another group company
Who is the actual acquirer? Agreement, appendix, written disclosure of the chain The PSP refuses to identify the acquirer even after due diligence has started
Who settles with the operator? Settlement schedule, bank details, contractual structure Funds are to arrive from an unknown third company with no explanation of its role
Who is the merchant and how is the MID structured? Merchant agreement or sponsored merchant agreement, MID information, and Payment Facilitator details The operator is promised a “ready MID,” but no one explains in whose name it is registered
Are the specific product and countries accepted? Written confirmation after disclosure of the licence, product, domains, and GEOGEO refers to the countries or markets targeted by the operator: where it accepts players, buys traffic, runs affiliate campaigns, accepts payments or advertises. A verbal statement that “we accept all gambling and all countries” without qualifications
Who controls the reserve? Agreement: amount, formula, place of accounting, permitted uses, release procedure The reserve is described as “insurance,” but the conditions for use and return are absent
Where are settlement funds held before payment? Contractual and banking structure; information about the relevant regulated entity where applicable It is impossible to determine which legal entity is obliged to return the funds
Who can change the pricing, reserve, or limits? Agreement provisions on amendments and notice The provider may immediately change any economic terms without a defined process
What happens when the service is terminated? Terms governing termination and suspension, holdback, and final settlement The agreement governs the termination of payment processing but says nothing about settlement and the reserve
Can transaction data and history be obtained? Export terms, format, retention period, transition assistance After termination, the operator loses access to transaction history, disputes, and reconciliation
Which subcontractors are critical to the service? List of material downstream partners where disclosure is provided The service is sold as a single solution, but no one can explain the actual chain

Learning the name of the acquirer does not mean that the operator is entitled to bypass the PSP and approach the acquirer directly. The purpose of the review is different: to understand the dependencies of the operator’s own business and to make sure the offer corresponds to the actual payment infrastructure.

Reviewing the MID and aggregator model

The statement “we will give you a MID” is not enough.

A MID may relate to a direct merchant, while in another architecture the operator may work as a Sponsored Merchant through a registered Payment Facilitator. Mastercard Rules expressly provide for this model and impose obligations on the Payment Facilitator in relation to Sponsored Merchants, including maintaining their information, monitoring them, and making payments.[2]

The operator therefore needs answers not only to whether an identifier exists, but also to four more substantive questions: who is registered as the merchant, which legal entity is the Payment Facilitator, who the acquirer is, and which participant bears the obligation to transfer settlement funds to the operator.

Regulatory status should be matched to the function

A company may genuinely appear in a financial register, but that alone does not prove that the specific service falls within the scope of its permission.

For example, the FCA expressly recommends checking not only whether a firm appears in the Financial Services Register, but also whether its permissions correspond to the service actually being offered.[7]

The same principle applies to a group of companies. A permission held by a parent or affiliated company cannot automatically be attributed to the legal entity that signs the agreement with the casino.

Red flag The agreement names an unregulated technical entity, marketing materials refer to the licence of another group company, and the party that actually accepts or controls the funds is not disclosed.

This does not prove a violation, but it means the review should be completed before funds are transferred and processing begins.

Backup routes and payment resilience

A backup payment route is not intended to covertly redirect transactions after the primary acquirer has refused them. Its purpose is to preserve business continuity in the event of a technical failure, commercial termination, a change in risk policy, or a settlement delay.

Resilience starts with the agreement for the primary channel.

The operator should understand when the provider may stop new transactions, when it may hold settlement, which obligations may be covered by the reserve, how long a security balance may remain held after termination under the agreement, and what information will remain available after disconnection.

If these parameters are unknown, a second PSP does not solve the problem by itself.

Own liquidity matters more than the formal number of PSPs

Having two integrations creates technical redundancy, but it does not guarantee access to funds.

One provider may stop accepting new deposits while simultaneously holding unsettled amounts and the reserve. The second channel may technically be available at that point but may not yet be approved for the relevant company, country, product, or volume.

Payment resilience should therefore be assessed through the operator’s own liquidity.

Funds awaiting settlement and a reserve held by the PSP should not be treated as available to meet current obligations until the contractual right to receive them has arisen.

A testable shutdown scenario

A stress test does not require an invented “market percentage.”

The actual contractual terms can be used to model the following scenario:

the primary provider stops accepting new deposits today; all transactions already processed but not yet settled remain unavailable until the next date permitted by the agreement; the reserve continues to be held under the contractual terms; and the second channel may be used only within the scope of approval already obtained.

The finance team then identifies all obligations that will fall due before the operator can again use external settlement funds.

The calculation includes amounts due to players, refunds already confirmed, and other business obligations. The result is compared with the company’s own liquid funds.

Practical conclusion If this scenario produces a cash shortfall, the problem is not only dependence on a single PSP. The business as a whole is underfunded for the terms of its payment agreement.

The second channel should be approved before an emergency

A backup PSP is useful only if it actually knows the operator, product, company, licensing setup, and permitted markets.

A continuity plan should not be based on the assumption that, after the primary channel is disconnected, the same flow can immediately be routed through another MID or another company.

A new onboarding may require its own due diligence, agreements, and technical setup.

Mastercard also provides for ongoing merchant monitoring and re-screening when there are material changes in the business.[1] This further illustrates why a backup route should not be treated as an invisible technical switch made without the acquirer’s knowledge.

Red flag The “backup PSP” is only a technical gateway that promises to find another MID after the primary channel is blocked, without first disclosing to the operator who will be the merchant, acquirer, and settlement party.

What to prepare before the primary channel is terminated

A workable resilience plan should address four tasks.

First, how the operator will continue to meet obligations already owed to players even if new deposits stop.

Second, how the existing channel will be wound down: unsettled transactions, disputes, refunds, the reserve, and the final balance.

Third, which alternative payment methods have already been approved and can be used without changing the disclosed model.

Fourth, which data needs to be obtained from the departing provider in order to preserve transaction history, evidence relating to refunds and disputes, accounting reconciliation, and the ability to respond to subsequent requests.

Mastercard Rules demonstrate the real dependency of a Sponsored Merchant on the upstream chain: the sponsored merchant agreement must provide for termination in specified circumstances, for example if the Payment Facilitator is deregistered or its acquirer ceases to have the relevant status with Mastercard.[2] This relates to the specific Mastercard model, but it clearly illustrates the operational risk of dependency on upstream partners.

Analytical conclusion The resilience of a payment architecture is not determined by the number of PSP logos on a website. It is determined by whether the operator can continue payouts and reconciliation, obtain its data and funds, and then lawfully move new transactions to a pre-approved channel.

Frequently asked questions

How much does it cost to connect a PSP for an online casino?

There is no single rate. The full cost should be calculated from the processing fee, fixed fees, currency conversion, payout costs, refund and dispute costs, monthly minimums, and the economic impact of the reserve and settlement delays.

There may also be separate integration, setup, or service fees if they are included in the specific offer.

Comparing PSPs solely by the processing percentage is not enough. One channel may have a lower base rate but impose materially greater liquidity constraints.

How long does PSP onboarding take?

There is no universal timeline.

The duration depends on the readiness of the documents, the licence and geography, the ownership structure, processing history, the complexity of the flow of funds, the operator’s response time, and the number of participants that need to approve the model.

Preliminary interest from an intermediary or a quoted commercial rate does not mean that the acquirer and settlement party have already completed their review.

For planning purposes, it is better to treat the stages separately: initial assessment, due diligence, contracting, technical integration, and testing.

Is a gambling licence enough to obtain acquiring?

No.

A licence may be a mandatory entry requirement, but the provider also evaluates the company, owners, product, domains, markets, user-facing documents, financial model, flow of funds, and controls.

Visa and Mastercard impose their own requirements on gambling transactions, but compliance with card-scheme rules does not replace the legal right to operate in a specific regulated market.[1][2][3]

What should an operator do if a PSP refuses the project?

First, determine which category the refusal falls into.

If the provider does not in principle accept the relevant licence or GEO, it may make sense to look for a partner with a different risk-acceptance policy.

If the problem is inconsistent documents, an opaque flow of funds, weak controls, or insufficient liquidity, changing the name of the PSP does not solve the problem.

Not every provider discloses the detailed internal reason for a refusal, so the operator still needs to reassess its own project.

What documents are needed for a full review?

There is no universal closed list.

The provider will usually require evidence in several areas: the legal entity and owners, licensing and domains, target markets, product, user-facing documents, flow of funds, financial forecast, and operational controls.

The scope depends on the function of the PSP, acquirer, bank, product, and countries.

The main measure of package quality is not the number of PDF files but the absence of inconsistencies between them.

When is the reserve returned?

Only in accordance with the specific agreement.

A rolling reserve will normally have its own accumulation and release cycle. On termination, a separate hold period may apply to cover contractual refunds, disputes, a negative balance, or other obligations.

Neither the reserve percentage nor the period for its return should be treated as universal.

Before onboarding, the operator should obtain the formula, permitted uses, and final reconciliation procedure in writing.

Can a refund be used instead of a payout of winnings?

For card transactions, these processes cannot simply be treated as interchangeable.

Mastercard Rules expressly prohibit the use of a refund transaction to credit gambling winnings or value intended for gambling to a Mastercard or Maestro Account and provide for a separate Gaming Payment Transaction structure.[2] Visa requires gambling winnings paid by card to be processed through an Original Credit Transaction, and in the Europe Region there is an additional requirement to use the same payment credential that was used for the winning wager.[3]

For other payment methods, the rules of the relevant channel should be checked.

How can an operator tell whether a PSP offer is genuine rather than merely an intermediary presentation?

The operator should establish the exact legal entity, its function, applicable regulatory status, acquirer and settlement partner, merchant and MID model, accepted products and countries, and the contractual settlement terms.

If a company claims to conduct regulated payment activity, its status should be checked in the official register for the relevant jurisdiction. For the EU/EEA, one source is the EBA Register of Payment and Electronic Money Institutions; for the United Kingdom, the FCA Financial Services Register.[6][7]

A bank or payment-scheme logo on a commercial website does not replace this verification.

Does cryptocurrency make a casino more payment-ready?

No. It changes the payment chain and introduces its own participants and regulatory questions.

Accepting a crypto deposit through an external provider does not by itself make the casino a Crypto-Asset Service Provider (CASPCASP means Crypto-Asset Service Provider. It is the term used by the EU’s MiCA framework for providers of cryptoasset services.). Within the scope of MiCAMiCA is Regulation (EU) 2023/1114 on Markets in Crypto-Assets, the EU framework governing cryptoassets and cryptoasset service providers., the actual functions matter: professional custody or control of assets and keys on behalf of players, exchange with clients, or transfers on their behalf require a separate assessment against the list of crypto-asset services. Receiving cryptocurrency as payment for the casino’s own service should not automatically be equated with providing those services.[11]

A gambling licence does not replace the legal basis required for a regulated crypto-asset service. In the EU, the relevant basis is authorisation under MiCA or the Article 60 regime available to certain financial entities. A basic banking or payment licence does not amount to permission to provide every crypto-asset service.[11] The status of an external provider and the scope of services it is permitted to provide should be checked separately; ESMA maintains the relevant public registerA public register is a publicly accessible record of licensed or authorised operators, suppliers, domains or certificates..[8]

EU rules on information accompanying transfers of crypto-assets apply within the scope of Regulation (EU) 2023/1113, including where a provider or intermediary for one of the parties has its registered office in the EU.[10] The EBA Travel RuleThe Travel Rule requires prescribed information about the originator and beneficiary to accompany certain transfers of funds and cryptoassets. Guidelines further specify the information and control requirements for applicable transfers.[9]

A self-hosted address does not remove the information obligations of a participating CASP. For amounts above €1,000, Articles 14(5) and 16(2) provide for an additional assessment of whether the relevant customer owns or controls the address. This is not a universal player-verification threshold or a lower threshold for all information obligations.[10]

The operator should therefore establish who accepts the asset, who holds it and controls the keys, where exchange takes place, who performs the transfer, and which legal entity provides each service. The specific function and its regulatory status should be assessed. These EU rules do not automatically apply to every crypto casino worldwide.

Does an online casino need a second PSP?

There is no universal requirement to have two PSPs.

A second channel may be useful as a continuity measure if dependence on a single processor creates unacceptable operational risk. However, the backup channel should be reviewed and approved in advance for the actual company, product, and markets.

Automatic technical switching should not be used to circumvent an acquirer’s decision, operate through an undisclosed MID, or change the actual merchant without the required approval.

This material is for informational purposes only and does not replace legal, regulatory, financial, or technical review of a specific payment structure. The permissibility of gambling activity, payment services, acquiring, holding of funds, crypto-asset operations, and individual payout methods depends on the jurisdiction, licence, target market, agreement, and actual function of each participant. Payment-scheme and provider rules change, so current primary sources and contractual terms should be checked again before onboarding and before any material change to the model.

Sources

  1. Mastercard — Security Rules and Procedures, Merchant Edition. Version dated 4 August 2026. Sections 9.2 and 9.4.2: registration of remote gambling merchants, documentation, and transaction identification; regional requirements apply within the scope specified in the rules.
  2. Mastercard — Mastercard Rules. Requirements relating to merchant activity and agreements, payouts, Payment Facilitators, and Sponsored Merchants. Sections 5.1.1, 5.1.2.1, and 7.8.1–7.8.2.
  3. Visa — Visa Core Rules and Visa Product and Service Rules. Rules on online gambling, transaction identification, payouts of winnings, and monitoring. Sections 5.8.18.1–5.8.18.3 and 10.4.3.1; the stated regional scope should be taken into account.
  4. PCI SSC — FAQ 1588. February 2025. SAQ A criterion concerning protection against script-based attacks for an embedded third-party payment page or form, and its distinction from redirect.
  5. PCI SSC — FAQ 1604. June 2026. External ASV scanning for relevant merchant webpages under SAQ A in both redirect and embedded-form models.
  6. EBA — Register of payment and electronic money institutions under PSD2. Register of payment institutions and electronic money institutions in the EU/EEA based on data from national competent authorities.
  7. FCA — Financial Services Register. Verification of the status of a specific legal entity, its permissions, and restrictions within the FCA’s jurisdiction.
  8. ESMA — MiCA, Article 109: register. Legal basis for the public register under MiCA, including Crypto-Asset Service Providers.
  9. EBA — Guidelines on information requirements in relation to transfers of funds and certain crypto-assets transfers. Information accompanying transfers of funds and crypto-assets; applicable within the relevant EU requirements from 30 December 2024.
  10. Regulation (EU) 2023/1113 — EUR-Lex. In particular, Article 16(2): applicable obligations for transfers involving a self-hosted address. The €1,000 threshold relates to the specific provision, not to a universal player-verification threshold.
  11. Regulation (EU) 2023/1114 (MiCA) — EUR-Lex. Article 3: definition of a provider and the list of crypto-asset services; Articles 59–60: legal bases for providing services in the EU and the regime for certain financial entities.

Search the site

About High-Risk LicensingiGaming brand protection in 2026: domains, mirror sites, traffic theft and digital attacksLaunching or acquiring an online casinoAnjouan or Tobique in 2026: Price, Licence Verifiability, PSPs and Crypto RisksCuraçao or Anjouan in 2026: Costs, PSPs, LOK and the Real Decision CriteriaCuraçao vs Tobique Gaming Licence in 2026: LOK, Tobique Shield, PSPs and the Cost of Operational ReadinessComparing gambling licences: choosing a comparison and assessing the risksDiscuss your projectCorporate Structure for iGaming and High-Risk Digital Businesses in 2026Nominee directors and shareholders in 2026: legality, UBOs, banking and risksBeneficial ownership registers in 2026: where UBO data is public and who has accessAnjouan Gambling Licence: Requirements and Application ProcessCuraçao Licence: Requirements and Application ProcessGeorgia Gambling LicenceGambling licences: local and offshore frameworksKUNAISA Gambling Licence: Requirements, Costs and Legal StatusNevis Gaming Licence: Requirements and Application ProcessTobique Licence: Requirements and Application ProcessGlossary HRLBusiness infrastructure:from licensing to reliable payment processingLegal Opinion for an iGaming Operator: When It Is Needed and How to Assess Its QualityPSP licensing in 2026: which authorisation a payment business actually needsHow to open an online casino in 2026: licence, company, platform, PSP and KYCOnline Casino AML/KYC Operations: Triggers, Enhanced Due Diligence, Withdrawals and Case ManagementChange management in online casinos: UBOs, domains, products, countries, suppliers and PSPsOnline casino compliance checks: practical tests before launch and changesOnline casino operations: licensing, players, suppliers and risk controlOnline Casino Obligations Calendar: Licensing, AML/KYC, PSPs, Tax and ReportingOnline Casino Player Complaints: Investigation, Time Limits, ADR and Root Cause AnalysisResponsible Gambling in Online Casinos: Risk Monitoring, Customer Interactions, Limits and Self-ExclusionOnline Casino Suppliers: Due Diligence, Contracts, Oversight and Exit PlanningCrypto Casino Payment Readiness in 2026Payment Systems for Online Casinos: Choosing a PSP and Getting ConnectedHow payments work: banks, card schemes and payment providersMerchant profile for iGaming PSPs: how to pass payment underwriting in 2026Payment Readiness of an Offshore Online Casino in 2026PSP red flags for online casinos in 2026Due diligence before buying a company with a gambling licenceBuying a ready-made company with a gambling licence in 2026