To test logic, test features and debug the system without risk, you need a sandbox mode - an isolated environment where you can reproduce real scenarios without affecting the combat platform. We are introducing a full-fledged test mode directly into the back office, while preserving all actions, logs and the ability to quickly switch between the "combat" and "sand" interface.
It is the perfect tool for QA, development, support and marketing.
What the sandbox mode gives
| Opportunity | Appointment |
|---|---|
| Testing transactions | Replenishment, withdrawal, cancellation, simulation of failures and check of limits |
| Check bonuses and shares | Test assignment, wagering, burning, and reuse |
| Safe API operation | Debugging integrations without access to real players and data |
| Load Test Scenarios | Run simulated sessions and bulk operations |
| Logging and reporting | Detailed history of all sandbox activities, export to CSV/JSON |
Features of the mode
Switch between combat and test environments in one click
Access by role: QA, development, support, partners
Clear sandbox data without affecting the foreground
Test Failure and Error Notifications
Integration with external CI/CD and bug tracking (Jira, Trello, etc.)
Advantages
Complete safety: no change in production
Confidence in releases and logic changes
Quickly identify bugs without compromising players
Reduced testing and validation time
Convenience for external teams and integrators
Where especially important
Online casinos and platforms with bonus and transaction mechanisms
Financial products with API integrations and KYC/AML checks
SaaS solutions with regular updates
Products with custom business logic and multiple scenarios
The Sandbox is the security zone for all changes. We will introduce a test environment in which you can try everything without fear of breaking anything - and be sure of stability when it comes to production.