🏆Jackpots

Smartico is providing a progressive Jackpot engine that is independent of the game providers.

In the base scenario, players contribute a small amount from each casino bet to participate. They can opt into the jackpots they prefer and can opt-out at any time. The Jackpot win is triggered randomly using certified RNG, giving every player a chance to win regardless of their bet size or game outcome.

Jackpots engine requires the following integrations to be in place:

  • Games catalog API - needed to limit jackpots only to selected casino games

  • Bonus API - to issue winning amount to the player. Note that API should allow issuing variable amounts as cash bonuses.

  • Wallet API - Smartico can request a deduction from the player's wallet to contribute to the Jackpot.

  • Bets submission - the operator needs to submit players' bets to the Smartico.

On the Casino front end, the Operator should use front-end APIs to:

  • list all available jackpots

  • show the current jackpot value on the screen of a specific casino game

  • show current participation statutes for the player and provide him the possibility to opt in/out

  • handle winning notification

You can find examples of implementation at https://expo.smartico.ai/jackpots and in the API Reference - https://github.com/smarticoai/public-api/blob/main/docs/classes/WSAPI.md

General capabilities of Jackpot engine

General Features

  • Operators can set up multiple Jackpots running in parallel, targeting different segments of users and games.

  • Games of different providers can participate in one Jackpot

  • Support of recurring or one-time jackpots

  • Supporting players with different currencies

  • The winner (s) is chosen using certified RNG logic.

  • Built-in reporting and support interface with the possibility to see historical pots, opted-in users, contributions, etc.

  • Can run on players of different brands

Contribution logic, bets & games limitations

  • Jackpot can be operator-funded or based on contributions from the Player's wallet.

  • Supporting seed amount and minimum and maximum winnings boundaries

  • Has control of eligible games and minimum bet amount

  • Has control of real & bonus bets participation in the jackpot

Customization:

  • Integrated with Smartico CRM to announce the winner(s) using Marketing campaigns

  • Support of localization and the possibility to customize in multi-brand environments

  • Row data of Jackpot transactions are available in the Smartico Data warehouse and can be exported to the operator's side.

  • Fully customizable front-end UI that can be built using API

How to setup Jackpot

To set the Jackpot configuration, you need to complete 5 steps:

1. "Core" configuration

  • Internal name

  • Status

  • Currency

  • Segment of eligible users

  • Eligible games (available in the "Eligible games" tab after saving jackpot)

  • Bonus template that will be used to issue the winning via Bonus API

2. Contribution rules

  • Type of contribution (percentage from the bet or fixed amount per bet)

  • Contribution money type

  • % of bet to contribute (e.g. 0.5% of 1 EUR, will deduct from the player wallet 0.005 EUR)

  • Percentage of contribution from the player. If the whole amount is taken from the player, or part of it will be covered by the operator (see explanation below)

  • Minimum bet amount per currency. It can be left empty if there are no restrictions.

3. Exploding logic

You can define:

  • seed amount

  • minimum amount at which the jackpot can explode

  • maximum amount at which the jackpot can explode

  • recurrence count, in case you want the jackpot to restart after it explodes.

Leaving "Recurrence count" empty will make the jackpot recurring for unlimited times.

4. UI configurations

Here, the operator can define the basic parameters for the jackpot visualization.

The first set is used in the Gamification widget and is also available in the front-end API:

  • Name

  • Description

  • Image

  • Priority

The second set of configurations defines who will get notifications about the winner and what the notification UI will look like.

Note that there are two ways to notify players:

  • those that are online at the moment of the winning can be addressed with visual animation indicating the winner

  • those that are offline can be addressed from the Marketing campaigns using Events & Properties described below

You can adjust Winner and Non-winner HTML templates to design your custom winning notification and use Placeholder 1/2 as translatable fields available as {{placeholder1}} and {{placeholder2}} in the HTML.

You can also handle visualization of the winner with fully custom implementation using the callback on the front end:

smartico.on('jackpot_win', (winner_info) => console.log(winner_info))

Check for the example of custom winning on https://expo.smartico.ai/jackpots

5. Branding

In case you are operating multiple brands under one setup, you can customize the UI to be different

Additional details

Eligible games, pots & players list

You can manage the list of eligible games, review the pots history, including details for all users who contributed to the pots, review the list of players participating in the jackpot, and opt out of players.

Operation-funded vs players-funded jackpots

Jackpots engine supports three modes of contribution:

  1. Player funded - when, after each bet, the engine requests from the Wallet an additional contribution amount that should be deducted from the Player's balance.

  2. Operator funded - in this case the defined contribution is added to the "pot" without deducting money from the user balance.

  3. Mixed - when part of the money is taken from the players' balance and the operator contributes another part. Note that operator contribution will be applied only after a successful contribution from the player wallet is completed.

The following screen shows the setup with 1 % of the bet contribution taken from the players' wallets.

By changing the "Percentage of contribution from the player" to 0, you can fully fund this Jackpot by the operator.

Events & properties to build campaigns & automation rules

There is a set of events and properties that can be used to build a marketing campaign or players in the Automation rules

  • jackpot_opt_in - sent for the player when he opts into the jackpot.

  • jackpot_opt_out - sent for the player when he opts out from the jackpot

  • jackpot_user_nonwin - sent to the participants (non-winners) of the jackpot when the jackpot is exploded

  • jackpot_user_win - sent to the participants (winners) of the jackpot when the jackpot is exploded

Depending on the context, you can use the following properties of events:

  • {{state.jackpot_template}} - name of the jackpot template

  • {{state.jackpot_winner_name}} - public username of the winner

  • {{state.jackpot_currency}} - currency of the jackpot

  • {{state.jackpot_amount}} - winning amount of the jackpot

Multi-currency usage

In the context of the jackpot we need to keep in mind three currencies:

  • The main currency of the player (also called Core Wallet currency). Let's take for example user currency EUR

  • The currency of the bet placed by the player. In the setups with multi-wallets, this currency could be different from the main currency of the wallet. For example, user can bet in BGN.

  • Currency of the jackpot - used as a base currency for aggregating the contributions of different players. For our example, let's take Jackpot currency as USD.

On the front end, the operator can choose which currency to show the current Jackpot value, which could be either user currency, EUR in our example, or Jackpot currency. (USD). You can find both values in the front-end API documentation - https://github.com/smarticoai/public-api/blob/main/docs/interfaces/JackpotPot.md

What happens when a player places a bet of 1 BGN

  1. Smartico is converting 1 BGN to jackpot currency and calculating the needed contribution, let's assume it is 1% of the bet, so 1 BGN = 0.56 USD, and the player contribution should be 0.0056 USD

  2. Smartico is requesting that contributions be deducted from the Casino Wallet. The integration API is flexible, and the request for deduction can be made in the BGN (player bet) or in EUR (player core currency),. In the case of the currency of the bet, it will be 0.01 BGN

  3. As soon as the contribution is deducted from the Casino Wallet, the current Jackpot amount is increased by 0.0056 USD

  4. Based on the RNG decision, if the player wins the jackpot, the jackpot value is converted from the Jackpot currency to the player currency (EUR) and issued as a bonus using the Bonus API

FAQ

Q: Can the Smartico Jackpot be used without additional work?

A: Yes, the Smartico Jackpot system can be seamlessly integrated with your existing CRM and Gamification setup, especially if you opt for an operator-funded model. In this configuration, the operator can allocate a marketing budget for the jackpot, which is then awarded through the Bonus API as either a bonus or real cash. This approach allows you to implement the jackpot feature without requiring additional front-end integration with the games or back-end integration with the wallet, keeping the setup straightforward and efficient.

In such a case, the only needed integrations that are usually already in place are:

  • Game catalog API, so you can choose which games are eligible for the jackpot

  • Bonus API with the possibility to issue variable bonus amount

  • Bets integration with game_id present in every bet

Q: What will the player see if he bets in USD but the current jackpot is in EUR?

When a player places a USD bet, Smartico automatically converts the contribution amount to EUR (the jackpot currency). In the Gamification widget, the player will see this Jackpot in EUR, but you can build your UI using the API provided by Smartico. In the API, you will have the jackpot amount in 2 currencies of your choice—the user's and Jackpot's currency.

Last updated