🏆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.

There are 2 modes that jackpot engine supports:

• with player contribution, when jackpot amount is based on additional fee taken from the wallet on every bet

• with marketing budget, when the jackpot is increasing automatically on every player bet and no additional fee is taken from the players' wallet

In addition to this, jackpots can be:

• Multi-player - when many players are contribution to the shared jackpot

• Personal - when every player has own pot that is contributed by this player and only this player can win it

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

Customisation:

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

• Support of localisation and the possibility to customise 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 customisable 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)

• Auto opt-in. When enabled, all players that are matching to the segment will participate in the jackpot from the first bet matching to the conditions (bet was placed on one of eligible games and minimum bet amount conditions were met)

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

Core configurations of the jackpt

2. Contribution rules

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

• Contribution money type

• Contribution money source as: Funded by operator, Taken from player wallet or Mixed

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

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

You can also customise default contribution percentage by defining specific rules for the exact games or providers. Check "Contribution rules" tab for details

The maximum contribution value is capped by 10% of max amount to explode.

For example, if jackpot is set to explode on 100 EUR, the maximum contribution will be capped to 10 EUR.

This setting can be adjusted to lower or higher value by request from the Operator

3. Exploding logic & seed amount

You can define:

• Seed amount

• Next seed contribution. You can define if every next seed will be build from the players contribution of the current pot.

• Min. amount at which the jackpot can explode

• Max. amount at which the jackpot can explode

• Recurrence count, in case you want the jackpot to restart after it explodes. Leaving it empty will make jackpot running without limit in number of explodings

• Require manual approval - gives a possibility to approve every winning manually, or to require approval only for winning above specific amount. Note that even with enable manual approval, players will be notified about winning, but Smartico will not issue winning amount through the Bonus API until its approved.

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

Building next seed from players contribution

if you are building recurring jackpot, you may want to define seed to be built from players contribution.

With this approach, your first jackpot will have fixed seed as you define it, but all next pots will have seed collected from the contribution of previous pot.

For example, you set pot contribution to be 1% from bet and contribution to next seed 5%, this means that from 1 EUR bet, system will calculate contribution to the jackpot as 1 cent, from this cent, 0.95 cent will go to the current jackpot and 0.05 cent will be reserved for the next seed.

To continue this example, lets assume that 1st jackpot had 100 EUR seed defined by you, and players did total bets of 75,165 EUR till the point when its exploded, which result 751.65 EUR total contribution. This contribution was split in two parts - 714.0675 (95%) were used for jackpot and 37.5825 EUR were reserved for the next seed.

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.

Configuration of Jackpot controbution

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

Winning protection options

There are few important options that can be used to control the winnings from jackpot

1. Max amounts - Multi-user jackpots are limited to 1000 EUR of max amount and Personal jackpots are limited to 10 EUR of max amount. This means that operator cannot create jackpots with max amounts above this limits. These configurations can be adjusted by written request from Operator.

2. Manual approval - we are highly recommending to use "Manual approval" option, that is requiring to issue winnings manually by approval from operator, this way operator can double check winnings before they are attributed to the players via Bonus API

3. Daily cap - there is a daily cap limit for the total won jackpots during a day for the whole setup. The default configuration is 1000 EUR and can be adjusted by request. Winnings above this limit will be still counted, but will require manual approval.

4. Hard limit for max winning - every jackpot has "Max" definition for the winning amount, but there are logical cases when jackpot can go above defined max (explained in FAQ below). There is a "hard limit" that is controlling that jackpot will never go above 10% from max limit.

FAQ

Q: Are the minimum and maximum winning amounts always preserved?

A: The minimum amount is always preserved, which means that jackpot will never explode on the amount lower then defined as minimum.

There is a possible case when maximum amount is not preserved, for example - the current amount in the jackpot is 99.9 EUR, the maximum is set to be 100 EUR, and some players is placing a bet that results in the contribution of 0.02 EUR. This bet will be winning and the winning amount will be 100.01 EUR.

There is also a "hard limit" definition in the system which is preserving jackpot from explode above 10% of maximum under any conditions. For example, the max winning is set to 10 EUR, but because of the high contribution from last bet the winning is calculated as 11.5 EUR, in such case "hard" limit will cap winning to 10% on top of 10 EUR, so the winning amount will be 11 EUR without 50 cents

Q: If the 0 amount bet is reported to the Jackpot system, is it triggering contribution and can participate in the winning.

A: 0-amount bet is participating in contribution and winning only in case jackpot is setup to have "fixed" contribution and not as % of the bet amount.

Q: Can Smartico report additional details when taking contribution from the wallet and when triggering Bonus API to issue jackpot winning?

A: Yes, the integration is flexible. Smartico can report - bet id that triggered jackpot, original amounts and contributions, ID of the jackpot template and ID of the pot, currency of the jackpot template, currency of the user and currency of the bet (as in some setups with multi-wallet, all 3 currencies could be different)

Q. Do Smartico have any attributes that derived from jackpot contribution or payout that can be use as triggers in your other Smartico modules?

A: There are 4 base events triggered by jackpot engine that can be used in other systems (campaigns, missions, automation rules, communication templates):

• Jackpot opt-in & jackpot opt-out - triggered when players opt-ins/outs.

• Jackpot win - triggered in the context of the player who won jackpot

• Jackpot non-win - trigger in the context of all players that participated in the jackpot, and when its exploded, didn't win it

This information also can be used in the segmentation, for example to find all past participants of the jackpot or all winnirs of any type of jackpot

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.