Red Tiger - Overview and Integration

2) Briefcase, mechanics and top titles

2. 1 Content and Mechanics

Subjects: adventure/antiquity, fantasy/dragons, "wealth/gold," Asia, classics/fruits.
Math: Wild/Expanding/Stacked, Multipliers, Free Spins/Respins, Locking Symbols, Cascades, Ways/Megaways, Power Reels (extended reels).
RTP profiles: several options (e.g. 96. x/95. x/94. x/92. x) to market.
Volatility: low to very high; game cards are labeled 'volatility', 'hit _ rate', 'max _ win'.

2. 2 Examples of hits

Dragon’s Fire (в т.ч. Megaways), Dynamite Riches, Piggy Riches Megaways, Gonzo’s Quest Megaways, Primate King, Cash Volt, Vault of Anubis, Reel King Mega и др.

3) Promos and jackpots

3. 1 Daily Drop Jackpots Network

Types: Daily Drop (guaranteed win until the end of the day), Hourly Drop (hourly), Must Drop (drop to a given threshold).
Pool options: 'seed', 'contribution%', 'tiers', currency, list of games, minimum bet to participate.
UI: current amount widget, win history, general rules; automatic localization and formats.

3. 2 Smart Spins/Tournaments

Smart Spins: segmented freespins/freebets and tasks (minimum rates/conditions, campaign window).
Tournaments/leaderboards: scoring by win-multiplier, amount of winnings, seriality, conditions of participation (minimum bet, games).
Prize Drops: random awards while playing (optional campaign budget).

4) Jurisdictions and Restrictions

Different: RTP profiles, betting/winning limits, Autoplay/Quick Spin/Feature Buy statuses, requirements for Responsible Gaming banners and fonts/icons.
Not all currencies/countries are connected to specific jackpot pools; promotional tools may be limited.
Regulators require cut-off reporting, round-level log storage, and correct RTP/odds disclosure texts.

• `region → rtp_profile, features_allowed, bet_limits, jackpots/promo_availability, texts_required`.

5) Integration architecture

5. 1 Wallets

Seamless (transfer-less): operator's balance; calls to '/authorize ', '/bet', '/win ', '/rollback'; idempotency is mandatory.
Transfer Wallet: pre-transfer funds to RGS; final synchronization at session close.

5. 2 Interfaces and events

REST/JSON + вебхуки/Callbacks: `bet|win|bonus|jackpot|session_start|session_end|disconnect|reconnect|promo_event`.
/ balance - balance/limits ;/bonus - freespins/promo (if applicable).
Idempotency: unique 'transaction _ id' (UUID/ULID) per 'bet/win'; repeat → return the same result (exactly-once in meaning).
Order: 'round _ id' is required; mapping'provider _ game _ id ↔ internal_game_id'.

5. 3 Timeouts/Retreats

Client timeouts 2-3 s; exponential backoff; replay queue; Response deduplication

5. 4 Localization/devices

Multilingual UI, correct currencies/formats, light assets; mobile-first для Megaways/Power Reels.

6) Event diagram and analytics

6. 1 Mini Event Diagram (JSON)

json
{
"event_id": "01J...RTG",
"event_time": "2025-11-02T12:31:05Z",
"type": "bet    win    bonus    jackpot    promo    session_start    session_end    disconnect    reconnect",
"user": {"id":"u123","tenant":"op1","country":"ES"},
"game": {"id":"rt_dragon_s_fire_megaways","rgs":"red_tiger","category":"slot"},
"session": {"id":"s456","device":"android"},
"wager": {"amount":1. 00,"currency":"EUR","round_id":"r789"},
"payout": {"amount":25. 40,"jackpot":false},
"jackpot": {"pool":"daily_drop_eur","eligible":true},
"promo": {"type":"smart_spins","id":"ss_q4_2025","progress":0. 5},
"meta": {"rtp_profile":"96","jurisdiction":"MGA"}
}

6. 2 Key metrics

GGR/NGR, Hit Rate, Spin Frequency, Bonus Entry/Win Multiplier.
Jackpot Contribution/Win (by pool/currency: Daily/Hourly/Must Drop).
Promo KPIs: participation in Smart Spins/tournaments, conversion and cost of awards.
RGS quality: p95/p99 API, error-rate, webhook lag, retry queue size.
Player/session: ARPPU/ARPU, avg session length, churn signals, complaints/1k rounds.

6. 3 Anti-fraud/anti-arbitrage

Bonus/tournament carousels, abnormal win-profiles, multi-account/device, geo-anomalies.
Reactions: pause promo/play by segment, betting limits, manual check.

7) RTP, volatility and exposure

Store'rtp _ profile'per market; lock Autoplay/Quick Spin/Feature Buy where prohibited.
Control 'max _ potential _ payout' per round/game; separate exposure limits for jackpot pools.
For Megaways/high-volatility titles, VIP guardrails (betting/session limits).

8) Jackpots: Config and Risk

8. 1 Pool parameters

yaml jackpot_pool:
name: "daily_drop_eur"
currency: "EUR"
seed: 10000 contribution_pct: 1. 5 tiers: [hourly_drop, daily_drop, must_drop]
games: ["rt_dynamite_riches","rt_dragons_fire_megaways","rt_cash_volt"]
eligibility:
min_bet: 0. 20 markets: ["MGA","GIB","ISR? no"]

8. 2 Event flows

Webhooks jackpot_contribution and jackpot_win; An entry in an independent payment ledger is required.
Refusals by unavailable currency/market - deterministic, with localized message.

8. 3 UI/UX

Current amount and countdown widgets (for Hourly/Daily); history of winners; RG banners.

9) Reporting and reconciliation

Round-level logs: bets/payouts/bonuses/jackpots/promos/statuses.
Daily Game Report by Games/Currencies/Markets; cut-off according to the provider's server time (store TZ/offset).
Reconciliation: sum of operator events vs provider summary reports; permissible delta - only on unclosed rounds.

10) Observability and SLO integration

yaml slo:
api:
authorize_p95_ms: 350 bet_p95_ms: 250 win_p95_ms: 250 error_rate_pct: <=0. 3 events:
webhook_lag_p95_s: <=3 duplicate_txn_pct: <=0. 1 jackpots:
win_grant_p95_s: <=5 pool_sync_delta_pct: <=0. 2 billing:
report_delta_pct: <=0. 2 closed_by_cutoff_pct: >=99. 7

Monitor: p95/p99 API, error-codes, webhook-lag, retry queue, rollback/void share, report discrepancies, closing rounds to cut-off.

11) Safety and compliance

mTLS + HMAC signatures on webhooks/REST; allowlist IP; short-lived tokens.
PII minimization in events; tokenization'user _ id'; RLS/CLS by region/tenant.
Responsible Gaming: Reality Check, limits, self-exclusion; correct texts/icons by market.
Jurisdictional flags at launch: autoplay/quick spin/feature buy, bid/session limits, RTP disclosure.

12) Test plan and QA

12. 1 Staging checklist

• '/authorize '/close the session; languages/currencies/formats correct.
• '/bet '/'/win 'are idempotent; repeats with the same'traction _ id '→ the same response.
• Free Spins/Smart Spins/Tournaments/Prize Drops accrual → expense → report.
• Jackpots: Win test (including Hourly/Daily/Must Drop), record and cut-off report.
• Jurisdictions: no feature, correct RTP profile, rate/session limits.
• Showcase/assets: location, shelves and jackpot widgets.

12. 2 Negative scenarios

Duplicate transaction _ id → 200 with stored result.
Timeout '/win '→ secure retry without double payout.
Currency/market without pool → correct failure and localized message.
Disconnect/Resume → the integrity of the promo round/states.

13) Frequent errors and anti-patterns

Single RTP to all markets; included prohibited features → compliance risks.
No idempotency '/bet |/win '→ double charge/pay.
Ignore'rollback/void '→ misaligned ledger.
No cut-off/snapshots → floating reports.
Unaccounted jackpot pool currencies → broken exposure and complaints.
SELECT in showcases/logs of fall → during MINOR evolutions of schemes.

14) Configuration templates

14. 1 Game/Market

yaml game_config:
game_id: "rt_primate_king"
markets:
- region: "MGA"
rtp: "96. 0"
features: {autoplay: true, feature_buy: true}
bet_limits: {min: 0. 20, max: 100}
- region: "UKGC"
rtp: "94. 0"
features: {autoplay: false, feature_buy: false}
bet_limits: {min: 0. 10, max: 10}

14. 2 Jackpot Pool

yaml jackpot_pool:
name: "rt_daily_drop_gbp"
currency: "GBP"
seed: 10000 contribution_pct: 1. 5 tiers: [hourly_drop, daily_drop, must_drop]
games: ["rt_piggy_riches_megaways","rt_cash_volt","rt_dragons_fire"]
eligibility: {min_bet: 0. 10}

14. 3 Idempotence policy

yaml idempotency:
key: "transaction_id"
storage: "redis+db"
ttl: "30d"
behavior: "return_last_result"

14. 4 Diagram of events (minimum)

yaml events:
keys: [event_id, event_time, type, user. id, game. id, session. id, wager. round_id]
bet:  [amount, currency, ext_ref]
win:  [amount, jackpot, ext_ref]
promo: [type, id, value]
tech: [client, device, latency_ms]

15) Implementation Roadmap

1. Inventory & Markets: Red Tiger game catalog, RTP profiles, feature flags; Smart Spins availability card/jackpot tournaments and currencies.
2. API & Wallet: choice of wallet model, idempotency, retrai, webhooks.
3. Events & Reports: event schema, round-level logs, cut-off and TZ.
4. Compliance: jurisdictional configs, RG requirements, texts/banners.
5. Promo/Jackpots: Smart Spins/tournaments/Prize Drops; Connecting Daily/Hourly/Must Drop pools display widgets.
6. Observability: SLO panels (API/events/jackpots/billing), alerts, replays.
7. Go-Live: canary traffic, KPI comparison (GGR, hit rate, jackpot participation, complaints), post-mortem of the 1st week.

16) The bottom line

Red Tiger is a portfolio with a strong promotional ecosystem and Daily/Hourly/Must Drop network jackpots that convert traffic well and retain an audience. The key to successful integration is idempotent billing, correct RTP/features by jurisdiction, transparent reporting with cut-off, pool exposure management and SLO observability. With a competent showcase and promo, Red Tiger provides a predictable contribution to GGR/LTV at a controlled risk and cost of service.