TITLE TAG : Casino Game Aggregator API Integration: 2026 Operator Guide
CHARACTERS : 57 — within 60-char hard limit
META DESC : Casino game aggregator API integration explained —
unified gaming servers, seamless wallets, webhooks,
jackpot FX, SubID tracking & compliance across 8
regulated markets. Full operator guide 2026.
CHARACTERS : 152 — within 155-char limit/casino-game-aggregator-api/ → casino game aggregator api integration
CANONICAL : https://www.sudonex.com/casino-game-aggregator-api/
REDIRECT MAP
301 if any of these slugs exist or were previously used:
/casino-api-integration/ → /casino-game-aggregator-api/
/game-aggregator-api/ → /casino-game-aggregator-api/
/casino-software-api/ → /casino-game-aggregator-api/
/unified-gaming-server/ → /casino-game-aggregator-api/
/casino-api-guide/ → /casino-game-aggregator-api/
Most operators underestimate what they are actually building when they integrate a casino game aggregator. It is not a plugin. It is a live financial and compliance infrastructure connecting your platform to thousands of game rounds, multiple currencies, real-time wallet transactions, affiliate tracking systems, and the geo-restriction requirements of eight separate regulatory frameworks — simultaneously. This guide maps every layer of that stack, from unified gaming server architecture to jackpot currency conversion parameters, so that technical product managers can make informed integration decisions before a single line of code is written.
What Is a Casino Game Aggregator API and How Does It Work?
A casino game aggregator API is a single integration point — built on RESTful architecture using JSON data exchange — that connects an operator's platform to a Unified Gaming Server (UGS), giving access to thousands of games from dozens of independent studios through one standardised technical bridge. Instead of negotiating, integrating, and maintaining separate connections with every game provider, the operator integrates once with the aggregator and inherits the entire library.
The scale this enables is significant. According to Platin Gaming's integration documentation, platforms like Alea aggregate over 15,000 games through a single secure API. KingMaker's UGS architecture handles the complex protocol translation required when different studios use different data formats, session management approaches, and wallet models — converting all of them into one consistent language for the operator's backend.
The core workflow operates in four layers. First, player authentication: the operator sends player data to the aggregator via API, receives an authentication token that identifies that player across every game in the library regardless of the original developer. Second, game session management: API endpoints build Game Launch URLs directly, allowing players to enter game sessions without passing through a separate aggregator lobby. Third, wallet orchestration: every bet and win is processed in real-time through either the aggregator's intermediate wallet or a direct pass-through to the operator's own system. Fourth, reporting: round IDs, timestamps, and financial data from every provider flow into a single consolidated reporting format for reconciliation and regulatory audit.
The critical decision at integration stage is not which aggregator to choose — it is which wallet model to build against. That decision determines your entire backend architecture
Bottom line: A casino game aggregator API replaces dozens of direct integrations with one unified connection. The UGS handles protocol translation, session management, and financial flow — but the operator's wallet architecture choice determines how much backend infrastructure they must own.
External Wallet vs Seamless Wallet: Which Model Is Right?
The choice between external and seamless wallet models is the single most consequential architectural decision in any aggregator API integration. Both solve the same problem — how to move money between the operator's platform and the aggregator's game library — but they do so in fundamentally different ways, with different operational trade-offs.
External Wallet Model
In the external wallet model, the aggregator maintains an intermediate wallet for every player on its platform. The operator's system initiates all transactions: before a player can access games, the operator sends an API call to fund credits into the aggregator's wallet. When the player finishes and the session closes, the operator retrieves the remaining balance.
The direction of request initiation matters here. The operator drives everything — fund-in, fund-out, balance check. The aggregator's wallet is a staging area between the operator's primary ledger and the game studios. This model is operationally simpler for the operator to implement because it requires fewer custom API endpoints on their side. It is, as KingMaker's architecture documentation describes, largely a legacy integration method — effective but less efficient for high-volume real-time operations.
Seamless (Single) Wallet Model
The seamless wallet model eliminates the intermediate staging layer entirely. The aggregator does not hold player funds. Instead, the UGS acts as a proxy — every time a player places a bet, the aggregator sends a real-time debit request to the operator's API; every win triggers a credit request back. The operator's system remains the sole source of truth for the player's balance at every moment.
The direction reverses: the aggregator initiates all requests. To support this, the operator must implement and host specific API endpoints — including /wallet/debit, /wallet/credit, and /wallet/balance — secured using OAuth 2.0 authentication protocols. Every transaction fires in real-time, per bet and per win, across every concurrent game session.
| Feature | External Wallet | Seamless (Single) Wallet |
|---|---|---|
| Balance ownership | Aggregator (intermediate) | Operator (primary) |
| Request initiator | Operator | Aggregator (UGS) |
| Transaction timing | Pre-play and post-play | Real-time per bet and win |
| Operator API requirements | Lower — fewer endpoints needed | Higher — must host debit/credit/balance |
| Player experience | Minor session gaps possible | Fully seamless — no interruptions |
| Implementation complexity | Lower | Higher |
| Operational control | Shared | Full operator control |
| Also known as | Transfer wallet | Common wallet |
The cost efficiency argument for seamless integration is real. Traditional high-risk payment processors charge operators between 5% and 10% per transaction. Operators running self-hosted seamless wallet infrastructure via direct aggregator API bypass those processors entirely for in-session transactions, reducing per-round processing costs to near-zero.
Bottom line: Seamless wallet is the modern standard — better player experience, full operator control, lower long-term transaction costs. External wallet remains viable for operators with limited backend development resources. The choice must be made before integration begins, as switching models post-launch requires a full backend rebuild.
Real-Time Webhooks: Bonus Triggers, Jackpots and CRM Events
Webhooks are the mechanism by which an aggregator's Unified Gaming Server pushes real-time event notifications to the operator's backend without the operator needing to poll the API continuously. They are not a supplementary feature — in regulated markets, they are a compliance requirement.
Configuration and Payload Structure
Operators subscribe to specific event types by registering destination URLs with the aggregator's webhook API. According to Platin Gaming's integration documentation, the core endpoint is POST /api/v1/webhooks. Once configured, whenever a predefined event occurs on the UGS, a JSON-formatted payload fires automatically to the operator's registered URL.
The events that matter most operationally are: spin start, round end, bonus trigger, and jackpot win. Each carries a structured payload containing the user ID, session ID, game ID, round ID, and event-specific parameters. For a bonus_trigger event — when a player enters a free spins round, a second-screen bonus, or a symbol transformation feature — the payload includes bonustype and bonuscode parameters that specify exactly which campaign or game feature activated.
CRM and Player Engagement Applications
The operational value of real-time webhook data extends well beyond transaction logging. Because the notification fires the instant a gameplay milestone occurs, operators can power intelligent engagement systems that respond to live player behaviour. A player entering a bonus round triggers an automatic progress update to any active promotional mission. A jackpot win triggers immediate congratulatory messaging to the player's interface. Retention ladder thresholds — loyalty reward milestones — update in real-time rather than in batch processing cycles.
This is the architecture that separates modern CRM-integrated platforms from static bonus systems. The webhook is the data pipeline connecting the game studio's event to the operator's engagement layer, with zero manual intervention.
GLI-19 Intermediate Phase Compliance
Under GLI-19 — Gaming Laboratories International's technical standard for online gaming systems, which governs regulated markets including Malta MGA, UKGC, and Spelinspektionen — operators must maintain accurate game history for every game round including intermediate phases. A bonus feature is an intermediate phase. Without webhook-based real-time tracking of bonus_trigger events, the operator's ledger cannot satisfy the GLI-19 requirement for complete round-status documentation.
The practical consequence: a GLI-19 audit that finds gaps in intermediate phase logging can result in licence compliance failure. Webhook integration is not optional in any of the eight markets covered by this guide.
Bottom line: Webhooks are the real-time nervous system of an aggregator integration. Configure them before go-live, not after. The bonus_trigger event specifically carries GLI-19 compliance implications that make its implementation a regulatory requirement in every major licensed market.
Jackpot Currency Conversion: The API Parameters Operators Must Know
Network-wide jackpots — pooled across multiple operators and multiple markets simultaneously — require a specialised set of API parameters to ensure that players wagering in different local currencies contribute accurately to the pool and receive correctly converted payouts. This is one of the most technically specific aspects of aggregator API integration, and it is absent from every existing guide in this SERP.
The Four Core Parameters
When a jackpot event occurs — either a contribution from a spin or a final win settlement — the aggregator transmits four parameters to the operator's backend via the API. Understanding these is essential for finance team reconciliation.
jpcur — Jackpot Currency. Identifies the base currency in which the network-wide jackpot pool is maintained. A global jackpot might be anchored in EUR regardless of where contributing players are located.
jprate — Exchange Rate. The specific conversion rate applied at the exact moment of the transaction, converting the jackpot's base currency value into the player's registered local currency.
jpamt — Hit Amount. The original win value is expressed in the jackpot's base currency (jpcur). This is the amount deducted from the shared pool.
jpcvtamt — Converted Amount. The final value credited to the player's wallet in their local currency, calculated by applying jprate to jpamt. This is the number that actually moves in the operator's financial ledger.
For win settlement specifically, the aggregator sends a txtype=511 Win Jackpot request that includes the full conversion data set — jprate and jpcvtamt — so the operator's system can update the player's balance accurately without any manual currency conversion step.
GLI-19 Display and Rounding Requirements
GLI-19 imposes specific requirements on how jackpot values are displayed and how conversions are handled. The jackpot's current pool value must be displayed to the player in their local currency format, updated at minimum every 30 seconds to reflect the current pool size and the live exchange rate. Operators who update the displayed jackpot value less frequently than this cadence are in breach of the standard.
On rounding: jackpot payoffs cannot be rounded down or truncated during the conversion process. If the conversion produces a fractional amount below the minimum currency unit, that fraction must be carried over to the next jackpot's reset amount rather than discarded. This protects the player from systematic micro-losses through rounding that would not be visible at individual transaction level.
For operators reconciling multi-currency jackpot payouts across several markets, the aggregator provides unified reporting that includes the jprate used for every transaction. Finance teams match local currency payouts against the aggregator's global pool records using these parameters — without them, reconciliation is manual, error-prone, and unauditable.
Bottom line: If your platform participates in network-wide jackpots, your finance team needs to understand jpcur, jprate, jpamt, and jpcvtamt before integration goes live. GLI-19 requires 30-second display updates and prohibits truncation — both have direct financial implications at scale.
Tracker and Postback Integration: Connecting APIs to Affiliate Analytics
Most operator technical guides treat API integration and affiliate tracking as separate disciplines. They are not. The SubID parameter system and S2S postback architecture connect directly to the aggregator's API event layer — and operators who do not build this bridge at integration stage cannot measure the true ROI of their marketing spend.
SubID Parameters and the Traffic Attribution Chain
SubID parameters are dynamic variables embedded in affiliate referral links that carry information about the traffic source — the specific campaign, ad creative, landing page, or affiliate segment that generated the click. According to JackCode's affiliate tracking framework, when a player clicks a tracked link, the SubID is carried through to the operator's platform and can be passed into the aggregator's API during the player authorisation process.
Once the SubID is embedded in the player's session record, every subsequent gameplay and financial event — tracked by the aggregator's UGS through the webhook pipeline — is linked to the originating traffic source. A player's first deposit, their bonus trigger activity, their gross gaming revenue contribution — all map back to the specific campaign that acquired them.
The S2S Postback Flow
The postback is a Server-to-Server notification sent from the casino platform back to the affiliate tracker when a defined conversion event occurs. The event triggers are drawn directly from the aggregator's API event layer: player registration, KYC verification completion, first-time deposit (FTD), subsequent deposits, and active gameplay sessions.
The postback payload transmits the event status, the payout amount where applicable, and the original click_id — the unique identifier that links the conversion back to the specific click that originated it. These transmissions are secured by unique tokens to prevent payload manipulation. The tracker receives this data in real-time and reconciles it against the click record, allowing the affiliate partner to confirm the conversion and trigger their own commission processing.
Fraud Detection and Campaign Optimisation
The integration between aggregator API data and tracker postbacks creates a powerful fraud detection layer. Trackers can identify geographically inconsistent logins — a player whose click_id originated in London but whose game session IP resolves to a different jurisdiction — and flag the discrepancy against the aggregator's geo-verification data. This allows operators to shut down fraudulent traffic sources instantly rather than discovering the problem in monthly reconciliation cycles.
GLI-19 requires a time-stamped postback request log for every notification sent to external trackers, including the unique player ID and IP address associated with each tracked event. Any automated decision made on the basis of tracker data — including blocking a player flagged for fraud — must have a logged justification available for regulatory review.
Bottom line: SubID-to-postback integration is not a marketing team concern — it is a platform architecture decision that must be made at API integration stage. Operators who defer it cannot retroactively attribute revenue to acquisition channels. Build it in from day one.
Geo-Restriction, Fraud Detection and Compliance by Jurisdiction
Geo-restriction in a regulated casino API is not a checkbox. It is a multi-layer technical system that must operate continuously, log every exception, and satisfy the audit requirements of eight different licensing bodies. The implementation gap between what operators assume is sufficient and what regulators actually require during a technical compliance audit is consistently significant.
The IP Verification Chain
When an operator authorises a player or launches a game session via the aggregator API, the player's IP address must be transmitted to the UGS as part of the authorisation request. This is not optional — it is a mandatory parameter. The system validates the player's region against the licence's permitted territory, and if the IP address changes unexpectedly during an active session, the system terminates the session automatically.
Advanced implementations do not rely on IP address alone. Per KingMaker's geo-restriction architecture, location accuracy requires multiple simultaneous data sources — Wi-Fi triangulation, GPS where available, and GSM network data — to establish a confidence radius around the player's physical location. If that confidence radius overlaps with a jurisdictional boundary that the licence prohibits, the game does not initiate. The boundary check must pass before session launch, not after.
In jurisdictions with enhanced compliance requirements, subsequent location checks must occur every 30 minutes throughout the active session or whenever any change to the player's IP address is detected — not just at login. This is a live monitoring requirement, not a one-time verification gate.
VPN, Proxy and Virtual Machine Detection
Fraud detection at the geo-restriction layer requires active identification and blocking of location masking tools: VPNs, proxy servers, remote desktop software, and virtual machines. Players using these tools to access games from jurisdictions where the operator is not licensed represent both a regulatory exposure and a financial risk for the operator.
The audit logging requirement for location violations must capture a time-stamped record of the violation, the unique player ID, and the detected location data. These logs must be available for regulatory review on demand. An audit that finds undocumented geo-violations is treated as a compliance failure regardless of whether the operator's platform actually served the player.
8-Jurisdiction API Compliance Reference Table
| Market | Regulator | Key API Compliance Requirement | Geo-Restriction Standard | Wallet Model Preference | Audit Log Requirement |
|---|---|---|---|---|---|
| UK | UKGC | Full KYC before first deposit; source-of-funds above threshold | IP verification + VPN blocking mandatory | Seamless preferred | GLI-19 compliant round history; postback log |
| Malta | MGA | GLI-19 certification required; RNG audit trails | IP + confidence radius; 30-min re-check | Seamless standard | Full round-level reconciliation; intermediate phase logs |
| Italy | ADM | ADM technical homologation; certified RNG | IP verification; ADM geo-filter integration | Seamless required for licensed ops | ADM-format audit trail; session logs |
| Spain | DGOJ | DGOJ technical certification; player session limits | IP verification + DGOJ territory filter | Seamless preferred | DGOJ-format transaction logs |
| Netherlands | KSA | KSA Remote Gambling Act 2021; Cruks integration mandatory | IP + Cruks self-exclusion check per session | Seamless required | KSA-format event logs; Cruks query records |
| Sweden | Spelinspektionen | Spelpaus integration required; bonus restrictions | IP + Spelpaus exclusion check | Seamless required | Spelinspektionen audit trail; bonus event logs |
| Ontario | AGCO / iGaming Ontario | AGCO registration; Ontario-specific player protections | IP + province verification | Seamless preferred | AGCO-format logs; responsible gambling event records [VERIFY] |
| Brazil | SPA | Law 14.790/2023 framework — rollout ongoing | IP verification framework in development | TBC — verify current SPA guidance [VERIFY] | SPA audit requirements pending full rollout [VERIFY] |
The Netherlands row deserves specific attention. Beyond standard geo-restriction, the KSA requires that operators query the Cruks national self-exclusion register at every login — not once at registration, but at every session initiation. The Cruks check must be completed before the game session is permitted to launch. Operators who implement session launch without a real-time Cruks API query are in breach of the Remote Gambling Act 2021 regardless of other compliance measures.
Sweden's Spelinspektionen imposes equivalent requirements around Spelpaus — the national self-exclusion register — with the added complexity of strict bonus eligibility rules that must be enforced at the API level for players who have previously self-excluded and subsequently re-registered.
Bottom line: Geo-restriction implementation that passes a basic functionality test does not automatically pass a regulatory audit. The confidence radius methodology, 30-minute re-check requirement, VPN/proxy blocking, and time-stamped violation logging are all distinct requirements — each must be explicitly implemented and documented.
Regulation, Safety and Responsible Gambling
Casino game aggregator API integration carries direct responsible gambling obligations that sit at the platform architecture level — not just in the front-end player interface. For operators across all eight markets in this guide, the responsible gambling tool set must be built into the integration from the start, not retrofitted after launch.
At the API integration layer, responsible gambling tools that must be technically implemented include: deposit limits enforceable at wallet API level, session time limits enforced via session token expiry, reality check notifications triggered by webhook at defined time intervals, cooling-off period locks that prevent session initiation after the player triggers them, and self-exclusion status checks that query national registers (Cruks, Spelpaus, GamStop) before every session launch where required by the relevant regulator.
For UK-licensed operators, GamStop integration is not optional — every UKGC-licensed operator must query GamStop's API at registration and at login. For Netherlands operators, Cruks queries are required at every session initiation. For Sweden, Spelpaus. These are not UX decisions — they are API requirements with direct licence compliance consequences.
Licensed operators in all eight markets are required to make responsible gambling tools immediately visible and accessible within the platform's player interface. Account settings must surface deposit limits, session limits, reality checks, and self-exclusion within two navigation steps from the logged-in home screen. If a platform's integration does not expose these controls at the front end, the API-level implementation is insufficient.
Problem gambling support resources for operators building in each market, and for players using integrated platforms, are as follows. UK: GamStop (gamstop.co.uk) and BeGambleAware (begambleaware.org) — National Gambling Helpline 0808 8020 133. Malta: Responsible Gaming Foundation (rgf.org.mt). Italy: Gioco Responsabile (giocoresponsabile.it). Spain: Juego Responsable (jugarresponsable.es). Netherlands: KSA Cruks (cruks.nl). Sweden: Stödlinjen (stödlinjen.se) and Spelpaus (spelpaus.se). Brazil: emerging support infrastructure under Law 14.790/2023 — general mental health services recommended in the interim. Ontario: ConnexOntario (connexontario.ca) and the Responsible Gambling Council (responsiblegambling.org).
Frequently Asked Questions
Q: What is a casino game aggregator API?
A casino game aggregator API is a single RESTful integration point that connects an operator's platform to a Unified Gaming Server, providing access to thousands of casino games from multiple studios through one standardised technical bridge. Instead of building and maintaining individual integrations with each game provider, the operator integrates once and accesses the aggregator's entire library. Platforms like Alea and Platin Gaming aggregate over 15,000 games through a single secure API, handling protocol translation, session management, and wallet orchestration for all connected studios simultaneously.
Q: How does a unified gaming server work?
A Unified Gaming Server (UGS) acts as a central translation layer between an operator's platform and dozens of independent game studios. When a player places a bet, the UGS receives the request, identifies the correct game provider's protocol, translates it, and returns the result — all in real-time. The UGS also manages player authentication tokens, session governance tied to jurisdictional rules, wallet transaction requests (debit for bets, credit for wins), and the webhook event pipeline that notifies the operator's backend of gameplay milestones. The operator never interacts directly with individual studios — the UGS handles all studio-level communication.
Q: What is the difference between external and seamless wallet?
External wallet means the aggregator maintains an intermediate wallet holding player funds, and the operator must send API calls to transfer credits in and out. Seamless wallet means the aggregator holds no funds — instead, it sends real-time debit and credit requests to the operator's own API endpoints as gameplay occurs. Seamless wallet is the modern standard: it provides a better player experience, gives the operator full balance control, and eliminates the need for pre-play fund transfers. External wallet is simpler to implement but less efficient for high-volume real-time operations.
Q: How do casino aggregators handle currency conversion?
Aggregators anchor each player session to a specific ISO 4217 currency code transmitted during authorisation. For network-wide jackpots involving multiple currencies, the API transmits four specific parameters: jpcur (the jackpot pool's base currency), jprate (the exchange rate applied at the moment of the transaction), jpamt (the win amount in the base currency), and jpcvtamt (the final converted amount credited to the player's wallet in their local currency). Under GLI-19, jackpot values must be displayed to players in their local currency updated every 30 seconds, and conversions cannot round down or truncate fractional amounts.
Q: What is a postback in iGaming affiliate tracking?
A postback is a Server-to-Server notification sent from the casino platform to an affiliate tracker when a defined conversion event occurs — such as player registration, KYC verification, first deposit, or active gameplay. The postback payload transmits the event status, the payout amount where applicable, and the original click_id that links the conversion back to the specific affiliate click that originated it. Postbacks are secured by unique tokens to prevent data manipulation and must be time-stamped and logged per GLI-19 audit requirements.
Q: How do webhooks work in casino platforms?
Webhooks are push notifications sent by the aggregator's UGS to the operator's configured backend URL when specific gameplay events occur. The operator subscribes to event types by registering a destination URL with the aggregator's webhook API (for example, POST /api/v1/webhooks). When a defined event fires — spin start, round end, bonus trigger, jackpot win — the UGS sends a JSON payload to the operator's endpoint in real-time without the operator polling for updates. Webhooks power CRM engagement, mission tracking, loyalty triggers, and GLI-19 intermediate phase compliance logging.
Q: What compliance standards apply to casino API integrations?
GLI-19 (Gaming Laboratories International Technical Standard 19) is the primary compliance framework for online gaming system architecture across MGA Malta, UKGC, Spelinspektionen Sweden, and other major regulated markets. It governs game history accuracy, intermediate phase logging, RNG certification, currency display standards, and geo-restriction audit requirements. Market-specific obligations layer on top: Netherlands KSA requires real-time Cruks self-exclusion queries at every session launch; Sweden requires Spelpaus integration; UK requires GamStop. Each jurisdiction also specifies its own audit log format and data retention requirements.
Q: What are idempotency keys and why do casino APIs use them?
An idempotency key is a unique identifier attached to an API transaction request that allows the system to safely detect and ignore duplicate calls — ensuring the same financial operation is never processed twice. In casino API integration, failed network requests can cause a transaction to be retransmitted. Without idempotency keys, a wallet debit for a single bet could be processed multiple times, creating reconciliation errors across thousands of concurrent game rounds. Aggregator APIs include idempotency key handling as a standard feature precisely because high-volume real-time gaming creates conditions where duplicate or failed transactions are statistically inevitable.
Q: How does geo-restriction work in a regulated casino API?
Geo-restriction in a casino API operates through a chain of verification steps. First, the player's IP address is transmitted to the UGS as a mandatory parameter during authorisation. The system validates the region against the licence's permitted territories. For enhanced accuracy, geolocation combines multiple data sources — Wi-Fi, GPS, GSM — to establish a confidence radius around the player's physical location. If that radius overlaps a prohibited boundary, the session does not launch. In regulated markets, location re-checks must occur every 30 minutes during active sessions, and any detected VPN, proxy, or virtual machine usage must trigger an immediate session block.
Q: What is GLI-19 and which markets require it?
GLI-19 is Gaming Laboratories International's technical standard governing the architecture, security, and audit requirements of online gaming systems. It covers game history accuracy, intermediate phase documentation (including bonus feature tracking), RNG certification standards, currency conversion display rules, geofencing requirements, and audit log formats. GLI-19 compliance is required or referenced by MGA Malta, UKGC, Spelinspektionen Sweden, and ADM Italy, among others. Operators integrating casino game aggregators in any of these markets must ensure their UGS and reporting architecture satisfies GLI-19 requirements before applying for or renewing a licence.
Q: How do SubID parameters connect affiliate campaigns to casino API data?
SubID parameters are dynamic variables embedded in affiliate referral links that carry traffic source information — campaign, creative, landing page, or affiliate segment — through to the operator's platform. During player authorisation via the aggregator API, the operator passes these SubID identifiers into the player's session record. From that point, every gameplay and financial event tracked by the UGS — deposits, bonus triggers, GGR contributions — is linked to the originating traffic source. When conversion events occur, the platform fires S2S postbacks to the affiliate tracker carrying the click_id, allowing full ROI attribution from initial click through to lifetime player value.
Q: What is the difference between jpcur and jpcvtamt in jackpot payouts?
jpcur is the Jackpot Currency — the base currency in which the network-wide jackpot pool is maintained (for example, EUR for a European network jackpot). jpcvtamt is the Converted Amount — the actual value credited to the player's wallet in their local currency, calculated by applying the exchange rate (jprate) to the base jackpot hit amount (jpamt). The distinction matters for finance reconciliation: jpcur and jpamt tell you what left the shared pool; jpcvtamt tells you what arrived in the player's account. Discrepancies between these values that cannot be explained by the jprate are a reconciliation error requiring investigation.
Sources & References
- Platin Gaming API Integration Documentation — technical source for Unified Gaming Server architecture, webhook configuration (POST /api/v1/webhooks), bonus_trigger event payload structure, and game library scale (15,000+ titles via single API) cited throughout this article
- KingMaker iGaming Platform Documentation — technical source for external vs seamless wallet model definitions, OAuth 2.0 endpoint requirements, geo-restriction confidence radius methodology, and 30-minute location re-check requirement
- JackCode Affiliate Tracking Framework — technical source for SubID parameter architecture, S2S postback flow, click_id reconciliation, FTD/deposit/registration event triggers, and GLI-19 audit logging requirements for postback records
- Gaming Laboratories International GLI-19 Standard — https://www.gli.com — authoritative reference for round history requirements, intermediate phase compliance, currency display rules, jackpot rounding/truncation standards, and geo-restriction audit logging requirements
- KSA Remote Gambling Act 2021 (Netherlands) — https://www.kansspelautoriteit.nl — source for Cruks per-session query requirement and KSA technical compliance obligations cited in jurisdiction table