Multi-Currency Support

The ThrillPots Platform provides advanced multi-currency support. It uses bespoke a bespoke system of algorithms known as the Always Fair Multi-Currency system to provide operators with fine grained control over the multi-currency configuration aspects of their jackpots.

The Basics

At a basic level, every Jackpot has a base currency. This is the currency that the jackpot operates in at the lowest level.

In order to process contributions for players that may be using wallet currencies that are different from the jackpot's base currency, the platform uses exchange rates that are updated frequently by the system.

In this basic scenario, all contributions are based on the jackpot's base currency.

Example

A Jackpot is configured to have a base currency of EUR and accept a minimum contribution of €0.10. An opted-in player is using GBP as their wallet currency.

We know that EUR:GBP is not 1:1. For the purposes of this example, we will assume an exchange rate of 1:0.85.

Therefore, the GBP account player will be contributing a minimum of €0.10 to the jackpot, but in their transaction history, they will correctly see £0.085 being deducted from their account.

In this simple example, although the GBP player does not see an aesthetically pleasing bet amount for each contribution, they are wagering the correct amount into the jackpot. There are a few downsides with this approach, one of which is that the contribution amount in GBP may fluctuate over time depending on the prevailing exchange rate.

Always Fair Multi-currency Support

The Always Fair Multi-currency system allowed operators to define both minimum and maximum contributions on a per supported currency basis without compromising on the fairness and integrity of their jackpot maths.

With the system, the operator can specify more appealing and intuitive minimum (and maximum) contribution values as follows:

While this table of Jackpot Contribution sizes may look much better than if we simply used exchange rates to calculate the contribution value, a question of fairness does need to be raised.

What is the problem?

Lets imagine a EUR player is wagering €0.10 into a jackpot while a JPY player is wagering 10 JPY. Based on the above configuration, this will be accepted by the system. But what about fairness. If we simply "accepted" bets of different sizes into the jackpot, the JPY player would have an unfair advantage over the EUR player since the real world value of 10 JPY is not equal to €0.10 (based on the exchange rate at the time of writing, 10 JPY = ~€0.06). This would mean that there would be greater value to be contributing in JPY than in EUR.

This is where the Always Fair technology comes into play.

What does Always Fair actually do?

The Always Fair Multi-Currency system ensures that the maths of the jackpot is scaled proportionally to the currency being used for contributions. Therefore, in the example above, the Always Fair algorithms ensures that the JPY player has their probabilities of hitting the jackpot scaled based on the value of their contribution in relation to the base currency of the jackpot. (Yes, we know thats a lot!)

While the detailed workings of the algorithm are beyond the scope of this document, here are the important take aways about what the Always Fair Multi-currency system enables:

• Allowed minimum and maximum contribution values to bet set per currency
• Ensuring that regardless of currency, contributions are always processed fairly - no player will receive an unfair advantage

Multi-Currency Opt-ins

The system supports two distinct modes of operation when it comes to player opt-ins.

1. Simple Opt-in/Opt-out

In this mode (which is default), if a player opts-in with Currency A, they are opted in. If they are able to change their currency to Currency B, they will still be opted in. If the Jackpot has a minimum contribution size defined for the player's currency (Currency B), then the contribution will be based on that configured minimum. If the jackpot does not have a minimum contribution defined for Currency B, the players contribution will be the value of minimum contribution of the jackpot's base currency.

If the jackpot does support Currency B as an alternate currency and the player opts out while using Currency B, they will also be opted out for Currency A.

2. Per-Currency Opt-In/Opt-out

In this mode, players are required to opt-in on a per currency basis. For example, if Player A opts in while using Currency A, but later on changes to using Currency B, they will not be considered opted in while using Currency B. In this mode, the player will need to explicitly opt-in for Currency B as well.

This logic extends to opting out as well. If a player has opted in for Currency A and separately for Currency B and then layer opts out for Currency B, they are still considered opted in (but only for Currency A). This is an important factor when it comes to community payout jackpots where only opted-in players are considered when picking the community winners.