Preparing Your Game for the Spinkings Certification Process
The first step in getting your game tested and certified for the Spinkings platform involves gathering all required technical documents. You will need a detailed Game Design Document (GDD), the latest build of your game (preferably in HTML5), and a valid RNG certificate from an accredited lab like iTech Labs or BMM Testlabs. The typical timeline for document review is 5-7 business days. Be prepared to provide proof of your game’s theoretical RTP (Return to Player) — the Spinkings team expects a minimum RTP of 92% for slots and 95% for table games. Missing paperwork is the most common reason for rejection at this stage, so double-check your submission package before sending it to the certification department.
Step-by-Step Technical Compliance Review
Once your documents are accepted, the technical compliance team at Spinkings will run your game through a series of automated and manual tests. This phase typically takes 10-14 business days. The testers will check for:
- Correct payout percentage calculation over 10 million simulated rounds.
- Proper implementation of the random number generator (RNG) with a tolerance of ±0.5% from the stated RTP.
- Compliance with local jurisdiction rules, including maximum bet limits (usually capped at £10 per spin for slots).
- Functionality of the “Autoplay” feature and the “Reality Check” pop-up timer (mandatory every 60 minutes).
If your game fails any of these checks, you will receive a detailed report with specific error codes. Common failures include incorrect symbol weighting, autoplay not respecting loss limits, or the RTP deviating outside the allowed margin. You must correct these issues and resubmit within 30 days to avoid a new review fee.
Payment Method Integration Testing
Following the core game logic review, Spinkings requires integration testing with its supported payment gateways. The platform works with providers such as Trustly, Neteller, Skrill, Visa, and Mastercard. Each deposit and withdrawal method has unique API requirements and processing times. For example, e-wallet withdrawals (Skrill, Neteller) are processed within 24 hours, while bank transfers via Trustly can take 2-5 business days. The table below outlines the standard limits and fees you must program into your game’s backend:
| Payment Method | Minimum Deposit | Maximum Withdrawal per Transaction | Processing Fee (Spinkings side) |
|---|---|---|---|
| Neteller | £10 | £5,000 | 0% (free for players) |
| Skrill | £10 | £5,000 | 1% (capped at £5) |
| Visa/Mastercard | £20 | £2,000 | 0% (free for players) |
| Trustly | £10 | £10,000 | 0% (free for players) |
You must program these exact limits using the API endpoints documented in the Spinkings payment integration guide. A typical mistake is forgetting to cap the Skrill fee at £5 when the 1% fee exceeds that amount, leading to a compliance failure.
Troubleshooting Common Certification Roadblocks
During the testing phase, developers often encounter three specific issues. The first is a mismatch between the game’s displayed RTP and the actual mathematical model after the reset condition. This usually happens when the “Respin” feature is not correctly calculating house edge. To fix it, run a standalone mathematical audit using a tool like “MathEngine” before submitting. The second problem involves the “spinkings free spins” feature not triggering correctly when the bet value changes mid-session. The trigger logic must be locked to the initial bet amount. Finally, the “Spinkings no deposit” bonus round integration sometimes fails because the free game mode is not properly sandboxed from the real-money mode. Ensure your API calls for the “fun” mode use a separate test endpoint.
Final Approval and Live Deployment Checklist
Once all technical tests pass, your game enters the final review stage which takes about 5 business days. At this point, the certification team verifies that your game correctly displays all mandatory disclaimers, including the UK Gambling Commission terms and the “Spinkings bonus” terms and conditions link. They will also check that your game’s metadata (title, description, category) is correct. During this stage, the quality assurance team will also verify that a valid “Spinkings promo code” field appears correctly in the cashier interface if your game offers a promotional integration. After approval, you are given a live deployment window — typically a Tuesday or Thursday between 06:00 and 10:00 GMT. You must push your final build through the Spinkings deployment portal during this window. If you miss the window, you have to wait for the next slot. Congratulations — your game is now live on the Spinkings casino platform.
No comments yet.