Selecting a payment service provider as a high-risk gaming merchant is rarely a single decision; it is a structured process that, when rushed, produces costly failures at the worst possible moments. A disciplined 90-day roadmap gives operators the time to assess providers properly, negotiate terms that reflect their actual risk profile, and integrate payment rails without disrupting live player flows.
Why PSP Selection Deserves a Full 90 Days
Many operators treat PSP onboarding as a procurement task rather than a risk management exercise. In practice, acquiring banks and payment networks scrutinise gaming merchants far more rigorously than they do standard e-commerce businesses. Underwriting timelines alone can run four to eight weeks. Factor in integration testing, compliance reviews, and reserve negotiations, and a 90-day window is conservative rather than generous.
Rushing the process creates predictable problems: accounts terminated shortly after launch, reserve ratios that strangle working capital, or chargeback thresholds breached because the PSP's fraud tooling was never calibrated to gaming transaction patterns.
Days 1 to 30: Due Diligence and Shortlisting
Define Your Acceptance Criteria First
Before approaching any provider, document your requirements across four dimensions:
- Geographies and currencies you need to process on day one and within 12 months
- Expected monthly volume, average transaction size, and anticipated chargeback ratio
- Preferred payment methods, including cards, open banking, e-wallets, and local payment schemes
- Regulatory licences you hold and the jurisdictions those licences cover
Evaluate Provider Stability, Not Just Pricing
A PSP offering the lowest MDR is worthless if its acquiring relationship collapses six months after launch. Request references from gaming merchants of comparable size. Verify the provider's own regulatory standing in each jurisdiction where you operate. Ask specifically which acquiring banks sit behind their gaming MIDs and how long those relationships have been active.
Also assess their chargeback management tooling. Gaming generates card-not-present disputes at higher rates than most verticals, and a PSP without robust pre-chargeback alert integrations will cost you far more than a higher processing fee would.
Days 31 to 60: Negotiation, Onboarding, and Technical Integration
Negotiate Rolling Reserves and Settlement Cycles Carefully
Rolling reserves are standard for gaming merchants, but the percentage and release period vary considerably. A 10 percent reserve held for 180 days against a high-volume operation represents a substantial working-capital lock-up. Push for tiered reserve structures that reduce over time as your chargeback history demonstrates low risk. Similarly, negotiate settlement frequency; weekly or twice-weekly settlement materially improves cash flow versus monthly cycles.
Complete Technical Integration in Parallel with Underwriting
Underwriting and technical integration can run concurrently. Use this period to complete API integration, configure 3DS2 authentication flows, set up webhook-based reconciliation, and test decline-recovery logic. Engage your PSP's technical team early; gaming platforms have unique session and wallet management requirements that generic integration guides rarely address adequately.
Ensure your platform can route transactions dynamically. Even if you are launching with a single PSP, build your architecture to accommodate a secondary provider later. Single-PSP dependency is an operational risk that regulators and auditors increasingly scrutinise.
Days 61 to 90: Testing, Compliance Alignment, and Go-Live
Run a Controlled Soft Launch
Before full traffic is routed through the new PSP, conduct a staged rollout, starting with a small percentage of transactions. Monitor authorisation rates, decline codes, and latency in real time. Set clear escalation thresholds so your payments team responds immediately if authorisation rates drop below acceptable levels.
Align PSP Data with Your AML and Responsible Gambling Frameworks
Transaction data from your PSP must feed into your AML monitoring system without gaps. Confirm that all payment method identifiers, card BINs, and wallet tokens are captured in a format compatible with your transaction monitoring rules. This is a compliance requirement, not an afterthought.
At OnlineShine, we have seen operators complete technically sound integrations only to discover that their PSP's data exports do not map cleanly to their AML case management system. That gap creates regulatory exposure the moment an auditor requests a complete transaction trail.
Document Everything Before Go-Live
Compile a payment operations handbook covering escalation contacts, reserve release schedules, chargeback dispute procedures, and settlement reconciliation workflows. This documentation supports audit readiness and reduces operational disruption when staff change.
Key Metrics to Track After Launch
- Authorisation rate by card scheme and geography
- Chargeback ratio against your contractual threshold
- Reserve balance and projected release dates
- Settlement timing versus contractual commitment
- Fraud loss rate and 3DS2 friction impact on conversion
