Selecting a payment service provider is one of the most consequential operational decisions a licensed gaming operator will make. Regulators scrutinise your payment architecture during licensing reviews, banking partners conduct their own due diligence on your PSP relationships, and a poorly chosen provider can trigger account terminations or licence conditions at the worst possible moment. Here is what the relevant stakeholders actually expect to see.
Why Gaming Is Treated as a High-Risk Merchant Category
Banks and card schemes classify gaming merchants as high-risk for two structural reasons: elevated chargeback rates and AML exposure. Chargebacks in gaming commonly exceed the 1% threshold that card schemes use as a warning trigger, and the sector's cash-flow intensity creates money-laundering risk that attracts close regulatory attention. Any PSP that accepts your business is taking on those risks alongside you, and banking partners know this. When a bank evaluates your payment stack, it is not only vetting you; it is vetting every third party that touches your funds flow.
Regulatory Expectations Around PSP Selection
Regulators across Malta, Gibraltar, the Isle of Man and the UK treat your choice of PSP as part of your broader fit-and-proper and AML obligations. Specifically, they look for the following:
- PSP licensing status: The provider must hold the appropriate e-money institution or payment institution licence in the jurisdiction where it processes funds. An unlicensed aggregator sitting between you and a licensed acquirer is a red flag during audits.
- Documented due diligence: Your compliance file should contain evidence that you assessed the PSP's own AML programme, chargeback management processes and fraud controls before onboarding them. A signed questionnaire is not enough; you need to review their policies and record your conclusions.
- Contractual safeguards: Regulatory bodies increasingly expect data-sharing clauses in PSP contracts so that suspicious transaction data can flow back to your MLRO without legal obstruction.
- Segregation of player funds: Where your licence requires segregated player accounts, the PSP arrangement must technically support that segregation. Commingled settlement accounts are a frequent cause of licence conditions.
What Banking Partners Want to See in Your Payment Stack
Acquiring banks that sit behind your PSP will conduct periodic merchant reviews. Their underwriting teams look beyond your licence certificate and focus on operational substance.
- Chargeback ratios below scheme thresholds: Visa's threshold is 0.9% and Mastercard's is 1.5% under their dispute monitoring programmes. Banks want to see a credible, documented chargeback management workflow, not just a current ratio that happens to be acceptable.
- Transaction monitoring integration: Banking partners are increasingly asking whether your PSP feeds transaction data into your AML monitoring system in near-real time. Batch reporting is no longer considered adequate for high-volume operators.
- Reserve arrangements: Banks often require rolling reserves of between 5% and 15% of monthly processing volume for gaming merchants. Understanding the reserve structure a PSP operates under tells you a great deal about the risk appetite of the bank behind it.
- Geographic payment flows: If your player base includes restricted jurisdictions or high-risk countries under FATF guidance, your bank will want to see that your PSP actively blocks or flags those transactions rather than simply passing them through.
Practical Steps for Operators Evaluating a PSP
The evaluation process should be treated as a procurement exercise with compliance weight, not simply a commercial negotiation.
- Request the PSP's most recent AML policy, chargeback dispute procedures and fraud detection methodology. Assess them against your own regulatory obligations before signing.
- Identify the acquiring bank behind the PSP and verify that it actively services gaming merchants rather than tolerating them through an intermediary. Banks that do not want gaming business will eventually deprioritise your settlement queue.
- Negotiate uptime SLAs separately from fraud tools. A PSP that offers 99.9% uptime but has no velocity controls on suspicious card testing is a liability.
- Confirm that the PSP can produce the transaction-level data your MLRO needs for SAR reporting within the timeframes your licence requires.
A PSP relationship is a regulated third-party relationship. The compliance burden does not transfer to the provider; it stays with the operator. Document your selection rationale as carefully as you would document a new high-value player.
The Onboarding Process Itself Signals Your Compliance Culture
How smoothly you can provide a PSP with your corporate structure, UBO documentation, licence certificates and financial projections during their onboarding process tells both the PSP and the bank behind them how mature your compliance function is. Operators who struggle to produce clean corporate documentation at this stage typically encounter higher reserves, tighter transaction limits or outright refusals. Investing in organised compliance records before starting PSP conversations pays direct commercial dividends.
