FASTSPIN Integration
0
Games Synced
0
Transactions
0.00
Total Bets
0.00
Total Payouts
Settings
Sync Games
Transactions
Callback URLs
FASTSPIN API Credentials
Enter Security Key to View
Display name for this provider integration
All API calls POST to this single endpoint
Provided by FASTSPIN (stored as client_id)
Used for MD5 digest signing (stored as client_secret)
ISO currency code (e.g. PHP, USD, CNY)
Integration Status
Enable/disable FASTSPIN integration site-wide
Log all FASTSPIN API requests/responses
FASTSPIN Setup
Setup Steps:
1. Enter Merchant Code & Security Key
2. Set API Base URL (staging or production)
3. Test connection (calls getGames)
4. Enable the provider
5. Sync games
6. Provide callback URLs to FASTSPIN
1. Enter Merchant Code & Security Key
2. Set API Base URL (staging or production)
3. Test connection (calls getGames)
4. Enable the provider
5. Sync games
6. Provide callback URLs to FASTSPIN
Auth Method: MD5 Digest
All API calls use
All API calls use
Digest: MD5(body + securityKey) HTTP header. No OAuth tokens needed.
Mode: One Wallet (Seamless)
Player balance stays on your server. FASTSPIN calls your callbacks for bets/payouts.
Player balance stays on your server. FASTSPIN calls your callbacks for bets/payouts.
Sync Games from FASTSPIN
Fetch the latest game list from FASTSPIN and sync them into your local database. FASTSPIN is a single provider — all games are synced at once.
Recent FASTSPIN Transactions
No transactions yet.
One Wallet Callback URLs
Provide these URLs to FASTSPIN support for One Wallet integration. They must configure these in their back office. Also ensure your server IP is whitelisted.
https://royaljilibet.com/api/provider2-balance.php
FASTSPIN calls this to query player balance (POST, Digest auth)
https://royaljilibet.com/api/provider2-transaction.php
FASTSPIN calls this for bet/payout transactions (POST, Digest auth)
https://royaljilibet.com/api/provider2-batch-transactions.php
FASTSPIN calls this for bonus/promotion transfers (POST, Digest auth)
FASTSPIN authenticates callbacks using MD5 Digest verification.
Your server validates the
Digest = MD5(requestBody + securityKey)Your server validates the
Digest HTTP header on every incoming request.Player accounts use format:
e.g. local user ID 42 becomes
PLAYER_{userId}e.g. local user ID 42 becomes
PLAYER_42 on FASTSPIN.