No real-money handling
Cymba returns multipliers only. Your app applies them to virtual coin balances.
Social Casino
Cymba handles the math layer for social casino slot games. You define the game in JSON, Cymba resolves the outcome as a multiplier, and your app decides what that multiplier means in virtual coins or loyalty points.
API example
POST /api/v1/spin
Authorization: Bearer cy_live_...
{
"config": "tropical-fruit-blast",
"lines": 30
}
{
"result": {
"round_id": "01JR4T2W...",
"grid": [[2,5,1],[3,5,4],[5,5,2]],
"summary": {
"total_multiplier": 8,
"breakdown": {
"ways": 8
}
}
},
"provably_fair": {
"server_seed_hash": "7d2b4a...",
"nonce": 19
}
}
Social casino apps let players spin slot games using virtual coins — no real-money wagering, no prize redemption. The business model is typically in-app coin purchases, ad monetisation, or engagement mechanics.
From a math perspective, social casino slots are functionally identical to any other slot game. They still need configurable reel strips, paytable evaluation, feature triggers, RNG, and RTP tuning. The only difference is that the multiplier output maps to virtual coins instead of a real-money balance.
Cymba handles the math layer and leaves the virtual coin economy to the app.
Building a slot math engine from scratch takes longer than most social studio teams expect. You start with basic reels and quickly discover the surface area: symbol weights, win-mode evaluation, free-spin recursion, hold and respin states, multiplier chains, max-win caps, and the testing required to trust the output.
An API makes slot math an integration rather than a build. Your team defines the game, calls the API, and works on what differentiates your product: themes, progression systems, player retention, and the overall app experience.
Social casino apps typically ship with multiple slot games and add new ones regularly to drive retention. With Cymba, each game is a JSON config stored in the dashboard.
Adding a game means creating or cloning a config, adjusting the math settings, validating the config, running test spins in the playground, and assigning it an ID your app calls. That workflow does not require engineering involvement for every new game.
Game designers and math consultants can work directly in the config editor, validate their changes, and see the RTP impact before anything goes live.
In social casino, RTP has a direct effect on coin economy. A higher RTP means players retain coins longer, reducing pressure to purchase. A lower RTP drains coins faster, potentially increasing purchase frequency but also increasing churn if players feel unlucky.
Getting the balance right usually requires iterating. Cymba's RTP tooling lets teams calculate theoretical RTP for any config and track observed RTP from real spin logs. A game performing outside its expected range is detectable early.
Social casino slots benefit from feature-heavy mechanics that drive excitement. Cymba supports free spins, cascades, hold and respin, mystery symbols, wild features, random multipliers, and meters through config. A social studio can enable or combine these mechanics by changing the JSON config rather than writing new evaluation code.
Social casino platforms can generate large spin volumes. Cymba is an API-first service, so scale is an infrastructure concern, not a config problem.
API key tiers control rate limits and production access. Studios testing game configs can work on a free tier; production deployments move to paid tiers as volume grows.
Start with a free API key, clone a template, and run your first provably fair spin.