For Gaming Operators
Clear compliance standards. Reduced liability. Simplified responsible gaming.
Why Operators Choose RGCP
✅ Clear Compliance Standard
No more guessing what regulators expect. One uniform standard replaces subjective interpretations
🛡️ Reduced Liability
State-mandated enforcement removes discretionary decisions and liability exposure from your platform
⚡ Simple Integration
RESTful API with comprehensive documentation. Sandbox testing environment. Typical integration: 4-8 weeks
📉 Lower Reputational Risk
Demonstrate commitment to player protection with verifiable, state-backed enforcement
🔄 Operational Efficiency
Offload responsible gaming infrastructure to centralized platform. Focus on core gaming experience
🤝 Level Playing Field
All operators follow the same rules. No competitive disadvantage from responsible gaming compliance
How Integration Works
Registration & Certification
Get Access:
- Register with state gaming authority
- Receive API credentials and documentation
- Access sandbox environment for testing
- Complete technical integration guide
Timeline: 1 week
API Integration
Implementation Points:
- Login Flow: Query RGCP before allowing access
- Deposit Flow: Validate limits before accepting funds
- Session Monitoring: Update activity in real-time
- Enforcement: Respect allow/deny/restrict responses
Timeline: 3-6 weeks development
Testing & Go-Live
Certification Process:
- Test all integration points in sandbox
- State gaming authority reviews implementation
- Production credentials issued
- Phased rollout with monitoring
- Ongoing compliance verification
Timeline: 1-2 weeks
Technical Integration
Simple RESTful API designed for easy implementation
Authentication
OAuth 2.0 with API keys. Secure credential management. IP whitelisting available for enhanced security
Low Latency
Target response time <100ms. High availability 99.99% SLA. Multiple regional endpoints for performance
Comprehensive Documentation
API reference, code samples, SDKs for popular languages. Postman collection for testing
Sandbox Environment
Full-featured testing environment. Mock player data. Test all scenarios before production
Webhooks
Real-time notifications for limit changes, self-exclusions, and policy updates
Technical Support
Dedicated integration support team. Documentation portal. Developer community forum
Key API Endpoints
POST /validate
Purpose: Validate player before login or deposit
Returns: allow | deny | restrict with remaining limits
POST /session/start
Purpose: Register new gaming session
Returns: Session token and active restrictions
POST /session/update
Purpose: Update activity during session
Returns: Updated limits and continue/stop signal
POST /session/end
Purpose: Close session and finalize activity
Returns: Confirmation and final state
GET /player/limits
Purpose: Retrieve current player limits
Returns: All active limits and exclusions
GET /health
Purpose: Check RGCP system status
Returns: System health and latency metrics
Compliance & Requirements
Mandatory Integration Points
State regulations require integration at these critical flows:
- Login: Validate player status before granting access
- Deposit: Check deposit limits before accepting funds
- Wager: Enforce wager limits in real-time
- Session Duration: Track and enforce time limits
- Self-Exclusion: Block access immediately upon activation
Enforcement Requirements
Operators must:
- Respect all RGCP responses before allowing gameplay
- Submit transaction confirmations for audit trail
- Maintain uptime and integration reliability
- Implement fallback procedures for system outages
- Report integration issues within specified timeframes
- Participate in periodic compliance audits
Pricing & Licensing
Fair, transparent pricing based on scale
Annual Licensing Fee
Tiered Structure:
- Based on active player count in jurisdiction
- Scaled by transaction volume
- Multi-state discounts available
- No per-API-call fees
- Unlimited API requests within fair use
What's Included
- Full API access and documentation
- Sandbox environment
- Technical integration support
- 99.99% uptime SLA
- Regular platform updates
- Compliance reporting tools
- Ongoing technical support
Frequently Asked Questions
What happens during system outage?
Documented fallback procedures ensure compliance. Operators maintain last-known limits locally. Full audit trail maintained for reconciliation
Can we customize limits?
No. Limits are set by players and enforced by the state. Operators cannot override or customize. This protects you from liability
What about existing tools?
RGCP replaces state-mandated responsible gaming requirements. You may offer additional voluntary tools, but RGCP is the compliance standard
How is data protected?
SOC 2 Type II certified infrastructure. End-to-end encryption. State-specific data residency. Operators see only their players' status
What about player privacy?
RGCP returns only enforcement decisions (allow/deny/restrict). Operators don't receive detailed limit information unless player chooses to share
How long is integration?
Typical timeline: 4-8 weeks for development and testing. Simpler integrations can be completed faster. Full support provided throughout
Ready to Integrate?
Get technical documentation, sandbox access, and integration support
Request Integration Details