iGaming Extension Overview
The Universal iGaming API extends the Universal Fraud API shared transaction model for regulated gaming activity.
Unlike other industries, iGaming supports both deposit and withdrawal transaction flows and may include gameplay, sportsbook, and player-statistics context.
Each request represents a single gaming‑related event. When the API accepts the data you submit, it creates a new transaction or updates an existing one. If the API rejects the request, it returns detailed validation warnings or errors in the response.
iGaming Extension Model
The Universal iGaming API extends the shared transaction model with:
- Deposit Information
- Withdrawal Information
- Game Information
- SportsBook Information
- Member Statistics
Note: See iGaming Complete Request Structuremm for the full path.
What Makes Gaming Different
Gaming platforms present a unique fraud and abuse profile compared to traditional commerce.
Key characteristics of gaming environments include:
- Bidirectional financial flows Gaming platforms support both deposits and withdrawals, which introduces abuse patterns that are not present in one‑directional purchase models.
- Account‑centric risk Fraud and abuse often target accounts directly through credential compromise, bonus abuse, or coordinated activity rather than isolated transactions.
- Regulatory oversight Gaming environments are frequently subject to jurisdiction‑specific regulations, which place additional requirements on monitoring, traceability, and risk controls.
- High‑velocity activity Gaming events can occur rapidly and repeatedly within short time windows, requiring evaluation that considers behavior across multiple events rather than a single action.
The Gaming API is designed to evaluate these characteristics using event‑level signals combined with historical and cross‑event context, allowing risk to be assessed accurately without applying unnecessary friction to legitimate players.
Hashing Requirements
The Gaming API follows the platform hashing rules. Fields designated as hash-required must be hashed before submission, including:
- giftCardNumber
- hashedPassword
See: Hashing RequirementsHashing Requirements (Constraint) and Accertify Hash AlgorithmAccertify Hash Algorithm (Reference).