This page details the technical specifications for the Gamgem dataset, including data models, file formats, and distribution mechanisms. The dataset uses a structured schema approach to organize gambling platform information for seamless integration with banking systems.

The Gamgem dataset organizes gambling platform data into several entities that represent different payment destinations:

Platform

Gambling websites and applications with identifying information like platform name, services offered (casino, betting), and primary website URL. These serve as the parent entities that tie together all payment methods for a specific gambling operator.

Merchant

Card payment processing details for platforms, including merchant data that appear in authorization requests and show up on card statements. This data enables blocking of card transactions to known gambling processors.

BankAccount

Bank transfer details for platforms, including account numbers (local and IBANs), bank codes (BICs, UK sort codes, ABA routing numbers, etc.), and account holder information. This data enables blocking of direct bank transfers and open banking payments to gambling-controlled accounts.

CryptoWallet

Cryptocurrency payment details for platforms, including wallet addresses across various blockchain networks. This data enables blocking of cryptocurrency transactions to gambling-controlled wallets.

Each Merchant, BankAccount, and CryptoWallet entity references its associated Platform entity, allowing you to understand the complete payment destination landscape for any gambling operator.

Common structure

All entities in the Gamgem dataset follow a consistent structure with common metadata fields and entity-specific attributes.

{
  "id": "01931b08-efc8-49bf-85d1-b80da3bed482",
  "schema": "ENTITY_TYPE",
  "createdDate": "2025-01-19T13:51:56.793Z",
  "updatedDate": "2025-03-06T21:33:04.559Z",
  "state": "ACTIVE",
  "attributes": {
    // Entity-specific attributes
  }
}
id
string
required

Unique UUID identifier for the entity

schema
enum<string>
required

Entity type identifier: PLATFORM, MERCHANT, BANK_ACCOUNT, or CRYPTO_WALLET

createdDate
timestamp
required

ISO 8601 timestamp when the entity was first identified

updatedDate
timestamp
required

ISO 8601 timestamp of the most recent update to this entity

state
enum<string>
required

Current operational status: ACTIVE or OBSOLETE

attributes
object
required

Entity-specific data, varies by schema type (detailed below)

Entity-specific attributes

The attributes object contains different fields depending on the entity type:

Represents gambling platforms and their core attributes.

{
  "id": "5c3ecbde-2fcc-4175-b0c2-5a95ca020a23",
  "schema": "PLATFORM",
  "createdDate": "2025-01-19T13:51:56.793Z",
  "updatedDate": "2025-03-06T21:33:04.559Z",
  "state": "ACTIVE",
  "attributes": {
    "name": "Mystake Casino",
    "services": ["CASINO"],
    "url": "https://mystake.com"
  }
}
attributes.name
string
required

Display name of the gambling platform

attributes.services
enum<string>[]
required

Types of gambling services offered. Possible values: CASINO, BETTING, POKER, LOTTERY, BINGO

attributes.url
string
required

Primary website URL for the gambling platform