Gamingtec
Gamingtec CORE is the shared player-account and back-office layer behind the brand's casino and sportsbook delivery. It covers accounts, wallet and transaction records, bonuses, player controls, reporting, and administration across a multi-product operation.
Page updated
Gamingtec is an active multi-entity trading brand. EG Interactive Ltd (09569922) is active and provides project management and consultancy services. No single company is assigned to every platform, casino, sportsbook, turnkey, or white-label order. The signed order must name the technology seller, any host-license entity, the player counterparty, and each data-role party.
Buyer decision brief
Use this summary to decide whether the offer belongs on your shortlist and which terms need a written answer.
Fit and use case
Editorial fitOperators evaluating one PAM layer for casino and sportsbook products and willing to define the seller, wallet authority, integration map, operating duties, and exit format in the order.
Primary offer: Gamingtec CORE PAM · 2 additional offers below
Primary offer delivery
- Software license
Integration boundary: CORE is configured as the account and operational layer, then connected to the selected casino content, sportsbook, payments, KYC, CRM, and front end.
Critical contract questions
Start with unresolved terms, negotiated terms, and dependencies that need a named owner.
Resolve before shortlist
No usable standard answer is available on the public terms.
8 of 9 shown- Wallet, ledger, and service levelsNot disclosed
- Gamingtec CORE PAM · Operations and service
- White-label market authorityNot disclosed
- Gamingtec Casino Platform · Market and approvals
- Feed and incident operationsNot disclosed
- Gamingtec Sportsbook · Operations and service
- PAM fees and usage baseNot disclosed
- Gamingtec CORE PAM · Commercial terms
- Casino price stackNot disclosed
- Gamingtec Casino Platform · Commercial terms
- Sportsbook fee and risk modelNot disclosed
- Gamingtec Sportsbook · Commercial terms
- Player, wallet, and history exportNot disclosed
- Gamingtec CORE PAM · Exit and portability
- Casino brand and player portabilityNot disclosed
- Gamingtec Casino Platform · Exit and portability
Next buyer step
Ask Gamingtec to resolve “Wallet, ledger, and service levels” and “White-label market authority” before moving Gamingtec CORE PAM to a commercial shortlist. Then compare the answer with the complete product record below.
Confirm every selected term in the proposal and signed order. No price, market approval, availability, or contracting entity is implied unless it is stated above.
What this provider offers
3 offerings- OfferingGamingtec CORE PAMTypePAM · Multi ProductOwnership and packagingFirst Party · Standalone and BundledDeliverySoftware LicenseCompare in
- iGaming Platform Providers · Technology Owner
- iGaming PAM Providers · Technology Owner
- Casino Platform Providers
- OfferingGamingtec Casino PlatformTypePlatform · CasinoOwnership and packagingFirst Party · Standalone and BundledDeliveryTurnkey, White LabelCompare in
- iGaming Platform Providers
- Casino Platform Providers · Technology Owner
- Turnkey Casino Platform Providers · Service Provider
- White Label Casino Platform Providers · Service Provider
- OfferingGamingtec SportsbookTypePlatform · SportsbookOwnership and packagingFirst Party · Standalone and BundledDeliveryAPI, iFrame, Turnkey, White LabelCompare in
- iGaming Platform Providers
- Sportsbook Platform Providers · Technology Owner
- Turnkey Sportsbook Platform Providers · Service Provider
- White Label Sportsbook Platform Providers · Service Provider
Gamingtec CORE PAM
Multi ProductFirst PartyAvailability: Standalone and BundledGamingtec CORE is the shared player-account and back-office layer behind the brand's casino and sportsbook delivery. It covers accounts, wallet and transaction records, bonuses, player controls, reporting, and administration across a multi-product operation.
CORE can sit inside a turnkey or white-label stack and is also positioned as a modular platform component. A separate order still needs to define the exact seller, wallet and ledger authority, migration scope, interfaces, support duties, and data-export rights.
Products
Integration: CORE is configured as the account and operational layer, then connected to the selected casino content, sportsbook, payments, KYC, CRM, and front end. API access, data mapping, wallet migration, certification, acceptance tests, and cutover responsibilities are defined for each implementation.
Key facts
- CORE provides the account, wallet-record, transaction, bonus, reporting, and back-office layer used across Gamingtec casino and sportsbook deployments
- Gamingtec uses a multi-entity sales structure, and the signed order determines which company supplies CORE, implementation, and support
- CORE is a first-party Gamingtec product line, while the legal IP owner and software licensor remain order-specific
Delivery options
Software License
Delivery modelA modular PAM and back-office layer for an operator-controlled gaming stack.
- Operator license
- Operator
- Merchant of record
- Operator
- Player data controller
- Operator
Included
- + Player accounts and wallet records
- + Back-office administration and reporting
- + Bonus and player-control tooling
- + Connections to selected gaming and service modules
Not included
- ! Operator gambling authorization
- ! Automatic ownership of integrated games or sportsbook data
- ! A universal legal seller across all Gamingtec orders
- ! Guaranteed source-code or unrestricted database access
Procurement record
Current product boundaries and the terms that still have to be fixed in the signed order or service agreement.
Known is usable now. Contract specific changes by order or market. Not disclosed has no usable standard term. Unknown remains unresolved. Outside provider scope is handled by the operator or another supplier.
Contract and supplier
- CORE seller and software rightsContract specific
- The order must identify the Gamingtec group company selling CORE, the legal owner or licensor of each component, the governing terms, and any group company performing implementation or support.
Implementation
- PAM migration and acceptanceContract specific
- Data mapping, wallet reconciliation, duplicate handling, interface ownership, environments, testing, certification, cutover, rollback, and acceptance criteria depend on the selected legacy stack and delivery route.
Operating responsibilities
- Operator-controlled deployment rolesKnown
- For the own-license turnkey route, the operator controls licensing, payment relationships, and player data. The contract must translate that control into named entities, systems, approval rights, and incident duties.
Operations and service
- Wallet, ledger, and service levelsNot disclosed
- The authoritative balance ledger, reconciliation sequence, availability target, recovery objectives, support response, release process, and incident ownership are not fixed outside the customer order.
Commercial terms
- PAM fees and usage baseNot disclosed
- Setup, minimum, platform, account, transaction, environment, support, integration, and revenue-linked charges require a complete price schedule and an auditable calculation base.
Market and approval scope
- Market and build approvalContract specific
- Each launch needs an entity, jurisdiction, product build, technical approval, hosting, payment, KYC, reporting, and operator-responsibility matrix. A modular product offer does not create market authorization.
Exit and portability
- Player, wallet, and history exportNot disclosed
- The order must define export schemas, wallet reconciliation, document and audit-history delivery, migration assistance, deletion, retained records, access after termination, and charges for transition work.
Strengths
- + The PAM, casino, and sportsbook are presented as modules of one operating stack.
- + The own-license route keeps licensing, payments, and player data under operator control.
- + Casino and sportsbook can share account, wallet-record, reporting, and back-office functions.
What to verify in procurement
- ! Gamingtec is not one legal company. The order must name every seller, licensor, implementation party, support party, and data-role party.
- ! Confirm whether CORE is the authoritative wallet ledger, how balances reconcile, and which interfaces remain available during an outage or migration.
- ! Require testable service levels, recovery objectives, release controls, security duties, audit access, and incident escalation in the signed schedule.
- ! Define complete player, wallet, transaction, document, consent, restriction, and audit-history exports before committing to the platform.
Gamingtec Casino Platform
CasinoFirst PartyAvailability: Standalone and BundledGamingtec's casino platform combines CORE player accounts, CRM and bonus controls, back-office tools, payment connections, and a casino lobby. Game content comes from integrated third-party studios rather than becoming Gamingtec-owned content.
An operator can procure the casino stack as an own-license turnkey build or through a licensed white-label route. Those models assign licensing and operating control differently, so they are separate buying decisions even when they share the same platform components.
Products
Integration: The casino platform is assembled around CORE and connected to selected game studios, payments, KYC, CRM, and front-end components. The implementation plan must map each provider, content contract, certification, wallet call, callback, failure path, test environment, and production approval.
Key facts
- Gamingtec supplies the casino platform and CORE layer, while the games connected to the casino are third-party content
- The own-license turnkey route leaves gambling authorization, payment relationships, and player-data control with the operator
- The white-label route does not use one named host-license entity, merchant, player counterparty, or player-data controller across every order
Delivery options
Turnkey
Delivery modelA complete casino build for an operator that controls its own gambling authorization, payments, and player data.
- Operator license
- Operator
- Merchant of record
- Operator
- Player data controller
- Operator
Included
- + CORE PAM and casino platform
- + Casino lobby and back-office configuration
- + Selected game and payment integrations
- + Implementation support for the scoped launch
Not included
- ! Provider-held B2C authorization
- ! Automatic approval in the target market
- ! Ownership of third-party game content
- ! Unlisted payment, KYC, or marketing contracts
- Launch time
- An approximately four-week implementation target applies only when scope, inputs, approvals, and third-party dependencies are ready
White Label
Delivery modelA hosted casino route using a provider licensing framework and a pre-integrated operating stack.
- Operator license
- Provider
- Merchant of record
- Unknown
- Player data controller
- Unknown
Included
- + Casino platform and CORE PAM
- + Licensing-framework support for an accepted market
- + Compliance, payment-system, and back-office tooling
- + Selected game-content integrations
Not included
- ! A universal host-license entity
- ! Guaranteed acceptance of every brand, owner, domain, or market
- ! A fixed merchant-of-record or funds-custody model
- ! Automatic transfer of player relationships or domains at exit
- Launch time
- A six-to-eight-week launch target depends on completed onboarding, content, payments, approvals, and brand inputs
Procurement record
Current product boundaries and the terms that still have to be fixed in the signed order or service agreement.
Contract and supplier
- Casino seller and host entitiesContract specific
- The order must name the casino-platform seller, software licensor, implementation and support companies, and any white-label host, player counterparty, merchant, funds holder, and data controller.
Implementation
- Casino launch dependenciesContract specific
- Brand assets, lobby configuration, game contracts, certifications, payments, KYC, geolocation, CRM, responsible-gambling controls, test environments, acceptance, and regulator or host approvals determine the real launch sequence.
Operating responsibilities
- Turnkey and white-label control splitKnown
- The own-license turnkey route leaves licensing, payments, and player data with the operator. The white-label route uses a provider licensing framework, but the host, merchant, player contract, and data roles require explicit terms.
Operations and service
- Game and payment dependency ownershipContract specific
- Gamingtec integrates external game studios and payment services. The responsibility matrix must assign commercial contracts, certification, configuration, monitoring, incident triage, reversals, reconciliation, and supplier escalation for each dependency.
Commercial terms
- Casino price stackNot disclosed
- Setup, platform, minimum, revenue-share, content, payment, compliance, support, environment, localization, and managed-operation charges need separate line items and calculation rules.
Market and approval scope
- White-label market authorityNot disclosed
- The host entity, authorization number, permitted product, approved domain, target players, responsible functions, platform build, game approvals, and payment route must be matched before launch.
Exit and portability
- Casino brand and player portabilityNot disclosed
- Domain, front-end, content agreements, player accounts, balances, histories, restrictions, documents, consent records, reporting data, and migration support need named owners, export formats, timing, and termination charges.
Strengths
- + The casino product shares one PAM and back-office layer with the sportsbook route.
- + The own-license turnkey model keeps core operating control with the operator.
- + The white-label route separates licensing support from the operator-controlled turnkey model.
What to verify in procurement
- ! Do not price the casino platform without separate schedules for game content, payments, KYC, messaging, certification, localization, and managed services.
- ! For white label, require the exact host-license entity, player contract, merchant and funds model, controller allocation, approved domains, and market conditions.
- ! Confirm who resolves disputed game rounds, failed callbacks, reversals, wallet mismatches, payment failures, and third-party outages.
- ! Treat launch targets as scoped planning assumptions until dependencies, acceptance criteria, approval gates, and remedies are written into the order.
Gamingtec Sportsbook
SportsbookFirst PartyAvailability: Standalone and BundledGamingtec Sportsbook combines a betting engine, odds and data, trading and risk operations, back-office controls, and configurable front-end components. It can connect to an existing stack through an API or iFrame or run inside Gamingtec's wider platform.
Turnkey and white-label sportsbook routes add different operating layers around the same core product. The contract still needs to separate software, data rights, trading decisions, liability, operator licensing, payment control, player relationships, and host-license duties.
Products
Integration: An operator can integrate the sportsbook through an API, embed an iFrame, or deploy it with Gamingtec CORE. The plan must define account and wallet calls, bet acceptance, settlement, cash-out, bonus behavior, feed rights, front-end ownership, event monitoring, test data, certification, and production acceptance.
Key facts
- Gamingtec Sportsbook is available through API, iFrame, or the wider CORE-based platform
- The sportsbook scope can include odds, sports data, trading, risk tools, back office, and configurable front-end components
- A white-label sportsbook order must define the host-license entity, merchant, player counterparty, funds model, data roles, and approved domains
Delivery options
API
Delivery modelA sportsbook engine connected to the operator's own front end, PAM, wallet, and operating stack.
- Operator license
- Operator
- Merchant of record
- Operator
- Player data controller
- Operator
Included
- + Sportsbook engine and integration interfaces
- + Odds, event, and settlement data for the contracted scope
- + Selected trading and risk functions
- + Back-office access
Not included
- ! Operator PAM, wallet, payments, or gambling authorization
- ! Automatic ownership of sports-data rights
- ! An operator front end unless separately scoped
- ! A fixed liability and trading-risk allocation
iFrame
Delivery modelA hosted sportsbook interface embedded into an operator-controlled account, wallet, and brand experience.
- Operator license
- Operator
- Merchant of record
- Operator
- Player data controller
- Operator
Included
- + Hosted betting interface
- + Sportsbook engine and back office
- + Contracted odds, trading, and risk functions
- + Integration with the operator account and wallet
Not included
- ! Operator license, PAM, wallet, or payment processing
- ! Guaranteed visual control over every interface element
- ! Unrestricted sports-data redistribution rights
- ! Automatic acceptance in every regulated market
Turnkey
Delivery modelA complete sportsbook build on Gamingtec CORE for an operator that retains its own authorization and operating control.
- Operator license
- Operator
- Merchant of record
- Operator
- Player data controller
- Operator
Included
- + Sportsbook engine and CORE PAM
- + Front end, back office, and selected trading scope
- + Payment and service integrations
- + Scoped implementation support
Not included
- ! Provider-held B2C authorization
- ! Automatic market or product approval
- ! Unlisted data, payment, or marketing contracts
- ! Undefined trading-loss or data-rights liability
White Label
Delivery modelA hosted sportsbook route using a provider licensing framework and pre-integrated operating stack.
- Operator license
- Provider
- Merchant of record
- Unknown
- Player data controller
- Unknown
Included
- + Sportsbook platform and CORE PAM
- + Licensing-framework support for an accepted market
- + Back-office, compliance, and payment-system tooling
- + Selected trading and risk services
Not included
- ! A universal host-license entity
- ! Guaranteed market, owner, brand, or domain acceptance
- ! A fixed merchant, funds, or data-role model
- ! Automatic player, domain, or front-end portability
Procurement record
Current product boundaries and the terms that still have to be fixed in the signed order or service agreement.
Contract and supplier
- Sportsbook seller and service partiesContract specific
- The order must name the engine seller, software licensor, data and odds suppliers, trading operator, implementation and support companies, and any white-label host, merchant, player counterparty, and controller.
Implementation
- Betting integration and acceptanceContract specific
- Account, wallet, bet, settlement, cash-out, bonus, limit, feed, front-end, reporting, and responsible-gambling flows need defined interfaces, failure tests, performance criteria, certification, cutover, and rollback.
Operating responsibilities
- Trading, risk, and liability splitContract specific
- Trading tools and services are available, but pricing authority, limit changes, event suspension, settlement corrections, risk acceptance, data errors, palpable errors, and trading-loss liability require a signed responsibility matrix.
Operations and service
- Feed and incident operationsNot disclosed
- Feed rights, event coverage, latency measurement, source redundancy, settlement hierarchy, correction windows, support response, availability, recovery, and escalation ownership are not fixed outside the customer order.
Commercial terms
- Sportsbook fee and risk modelNot disclosed
- Setup, minimum, platform, data, trading, risk, support, environment, integration, revenue-share, and liability-related charges need separate definitions and an auditable revenue base.
Market and approval scope
- Market, data, and product rightsContract specific
- Each jurisdiction needs a named operator or host, betting authorization, approved product and domain, data and streaming rights, technical build, player controls, payments, reporting, and localization scope.
Exit and portability
- Betting history and front-end handoverNot disclosed
- Open bets, settled bets, corrections, limits, exclusions, liabilities, player histories, reports, interface code, configuration, domain assets, export schemas, transition support, and post-termination access need explicit terms.
Strengths
- + API and iFrame routes let an operator choose between deeper front-end control and a hosted interface.
- + Sportsbook and casino can share the CORE account and back-office layer.
- + Trading, risk, odds, data, and front-end scope can be separated during procurement.
What to verify in procurement
- ! Define the commercial and legal boundary between software, odds and data rights, trading decisions, risk acceptance, and liability for pricing or settlement errors.
- ! For iFrame delivery, test wallet calls, session handling, consent, accessibility, localization, analytics, failure behavior, and control over the embedded interface.
- ! For white label, require the exact host, player contract, merchant and funds model, controller allocation, approved products, domains, and target players.
- ! Require export and transition terms for open bets, liabilities, settled history, restrictions, reports, configurations, and any operator-funded front-end work.
Reference documents7
Key public documents supporting the company identity, primary offer, delivery route, and highest-priority questions above.
- DocumentCompanies House — find-and-update.company-information.service.gov.uk / company / 09569922
- DocumentGamingtec — gamingtec.com / about us
- DocumentGamingtec — gamingtec.com / privacy policy
- DocumentGamingtec — gamingtec.com / gt turnkey
- DocumentGamingtec — gamingtec.com / gt casino
- DocumentGamingtec — gamingtec.com / gt sportsbook
- DocumentGamingtec — gamingtec.com / gt white label
