Yggdrasil - Overview and Integration

2) Portfolio, mechanics and series

2. 1 Content

Slots (core): classics/fantasy/mythology, "book" themes, grid and cascade mechanics.
RTP variability: usually several profiles (e.g. 96. x/95. x/94. x/92. x) under jurisdiction.
Volatility: low to very high; the game card contains' volatility ',' hit _ rate ',' max _ win '.

2. 2 Branded mechanics

Gigablox - large "glued" characters (from 2 × 2 to 6 × 6 +) in each back.
MultiMax/DoubleMax - animators accumulating on reels/combinations (DoubleMax doubles the series).
Splitz - one symbol "splits" into several, increasing the lines/ways.
GigaRise - dynamic growth of drum heights in a round/session.

2. 3 Top titles (examples)

Vikings Go Berzerk/To Hell - a series with rage progress and battles with wilds.
Valley of the Gods (1/2) - respins, removal of blockers, multipliers and extra-life.
Raptor DoubleMax - cascades + doubling the multiplier after each win.
Hades Gigablox, Cazino Zeppelin/Cosmos, Golden Fish Tank, Easter Island - "evergreen" hits.

3) Promotional platform and campaigns

BOOST: tournament tables (by win-multiplier/sum of wins), Prize Drops (random drops of prizes), Missions (fulfill N conditions in K games), Cash Race.
Free Spins/bonus packages: issue for specific games/denominations (if included in the config).
Widgets/banners: ready-made UI elements for the showcase and game pages (localized).

4) YG Masters and GATI (for Ecosystem)

YG Masters is a program for publishing games from partner studios under an umbrella distribution stack.
GATI (Game Adaptation Tools & Interface): unified templates and adapters for billing/localization/regulatory packages → one operator integration - many studios/titles.
For the operator: it is important to store the catalog of the origin of the game ('origin: ygg' yg _ masters: <studio> ') for reporting and showcases.

5) Jurisdictions and Restrictions

Requirements vary by: RTP, betting/winning limits, Buy Feature/Autoplay/Quick Spin, mandatory Responsible Gaming texts, age limit icons.
Not all campaigns/prizes and currencies are available in every region.
Regulators require cut-off reporting and round-level log storage (see § 9).

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

6) Integration architecture

6. 1 Wallets

Seamless (transfer-less): operator's balance; endpoints '/authorize ', '/bet', '/win ', '/rollback'; need strict idempotence.
Transfer Wallet: pre-transfer funds to RGS; calculations and closing session synchronization.

6. 2 Interfaces and events

REST/JSON + вебхуки/Callbacks: `bet|win|bonus|jackpot|session_start|session_end|disconnect|reconnect|promo_event`.
/ balance - current balance/limits ;/bonus - activation of freespins/missions (if API accrual is used).
Idempotence: 'transaction _ id' (UUID/ULID) for each 'bet/win'; repeat → return the past result (exactly-once in meaning).
Order: 'round _ id' is required; mapping'provider _ game _ id ↔ internal_game_id'.

6. 3 Timeouts/Retreats

Client timeouts 2-3 s; exponential backoff; replay queue and deduplication; "at-least once" webhooks on your side → idempotent handlers.

6. 4 Localization/devices

Multilingual UI, correct currency formats, light assets (especially for grid and Gigablox), mobile-first.

7) Event diagram and analytics

7. 1 Mini Event Diagram (JSON)

json
{
"event_id": "01J...YGG",
"event_time": "2025-11-02T12:31:05Z",
"type": "bet    win    bonus    promo    session_start    session_end    disconnect    reconnect",
"user": {"id":"u123","tenant":"op1","country":"DE"},
"game": {"id":"ygg_raptor_doublemax","rgs":"yggdrasil","category":"slot"},
"session": {"id":"s456","device":"android"},
"wager": {"amount":1. 00,"currency":"EUR","round_id":"r789"},
"payout": {"amount":18. 40,"jackpot":false},
"promo": {"type":"mission","id":"msn_2025w44","progress":0. 6},
"meta": {"rtp_profile":"96","jurisdiction":"MGA","mechanics":["DoubleMax","Cascade"]}
}

7. 2 Key metrics

GGR/NGR, Hit Rate, Spin Frequency, Bonus Entry/Completion Rate, Mission Completion, Prize Drop Participation.
RGS quality: p95/p99 API, error-rate, webhook lag, retry queue size.
Player/session: ARPPU/ARPU, avg session length, churn signals, complaints/1k rounds.

7. 3 Anti-fraud/anti-arbitrage

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

8) RTP, volatility and exposure

Store'rtp _ profile'per market; Block Autoplay/Feature Buy where prohibited.
Control 'max _ potential _ payout' per round/game; for highly flexible mechanics (DoubleMax/MultiMax), put VIP guardrails on limits.
For Gigablox/Splitz, track exposure peaks on "long runs" of freespins.

9) Reporting and reconciliation

Round-level logs (bets/payments/bonuses/promo/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; delta is only allowed on unclosed rounds.

10) Observability and SLO integration

API: `/authorize`, `/bet`, `/win` — p95/p99 и error-rate; Share of duplicate transactions

Events: webhook-lag, retry queue size, 'rollback/void' share.
Promo: delivery-rate missions/drops, prize accrual lag.
Billing: reporting discrepancy <threshold, percentage closed to cut-off.

SLO (sketch)

yaml slo:
api:
bet_p95_ms: 250 win_p95_ms: 250 error_rate_pct: <=0. 3 events:
webhook_lag_p95_s: <=3 duplicate_txn_pct: <=0. 1 promo:
reward_grant_p95_s: <=5 mission_state_lag_s: <=10 billing:
report_delta_pct: <=0. 2 closed_by_cutoff_pct: >=99. 7

11) Safety and compliance

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

12) Marketing & Showcase

Shelves: "Yggdrasil Hits," "Gigablox," "DoubleMax/MultiMax," "Splitz," "High Volatility," "Classic."

Теги: `Gigablox`, `DoubleMax`, `Splitz`, `Cascade`, `Book`, `High Volatility`.
Campaigns: tournaments/drops through BOOST, missions with progress, freespins for onboarding.
Assets: 1:1 icons, 16: 9/4: 3 posters (webp), short preview videos; localized titles/descriptions.

13) Test plan and QA

13. 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/Bonus/Missions/Prize Drops accrual → expense → report.
• Jurisdictions: Autoplay/Feature Buy ban, correct RTP profile, bid/session limits.
• Reports: event matching, cut-off, multi-currency.

13. 2 Negative scenarios

Duplicate transaction _ id → 200 with stored result.
Timeout on '/win '→ secure retry without double payout.
Region without promo/currency → deterministic failure and correct localization.
Disconnect/Resume → the integrity of the state and round; true progress of missions.

14) Frequent errors and anti-patterns

A single RTP and display of prohibited features → compliance risks.
No idempotency '/bet |/win '→ double charge/pay.
Ignore'rollback/void '→ misaligned ledger.
No cut-off/snapshots → floating reports.
Failure to take into account lags of promotional charges → complaints and controversial cases.
SELECT in showcases/logs of fall → during MINOR evolutions of schemes.

15) Configuration templates

15. 1 Game/Market

yaml game_config:
game_id: "ygg_hades_gigablox"
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}

15. 2 Idempotence policy

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

15. 3 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. 4 BOOST/missions (sketch)

yaml promo_campaign:
id: "boost_q4_2025"
type: ["tournament","prize_drop","mission"]
games: ["ygg_raptor_doublemax","ygg_valley_of_the_gods_2"]
rules:
tournament: {scoring: "win_multiplier", min_bet: 0. 2}
prize_drop: {budget_eur: 20000, prizes: 1500, min_bet: 0. 2}
mission:
steps:
- {game:"ygg_raptor_doublemax", goal:"win_x>=25", count:1}
- {game:"ygg_valley_of_the_gods_2", goal:"free_spins_trigger", count:1}

16) Implementation Roadmap

1. Inventory & Markets: Yggdrasil/YG Masters games list, RTP profiles, feature flags/limits; promo/currency availability card.
2. API & Wallet: wallet selection, idempotency, retrai, webhooks; config promo BOOST.
3. Events & Reports: event schema, round-level logs, cut-off and TZ.
4. Compliance: jurisdictional configs, RG requirements, texts/banners.
5. Promo: tournaments/missions/drops, window integration and CRM.
6. Observability: SLO panels (API/events/promo/billing), alerts, replays.
7. Go-Live: canary traffic, KPI comparison (GGR, hit rate, mission completion, complaints), post-mortem of the 1st week.

17) The bottom line

Yggdrasil combines strong native mechanics and a scalable GATI-based YG Masters ecosystem, and the BOOST platform simplifies network-level promos. Successful integration relies on idempotent billing, correct RTP/features by jurisdiction, transparent reporting with cut-off and SLO observability. With a thoughtful showcase and promo, Yggdrasil's portfolio provides a sustainable contribution to GGR/LTV at a manageable risk and cost of service.