---
title: iGaming Extension Overview
slug: public-apis/igaming-extension-overview
createdAt: 2026-03-11T14:59:53.177Z
---

::::ExpandableHeading
###

**Topic type: Concept**

:::hint{type="warning"}
**Purpose: **Provide an overview of the Legacy Gaming Fraud API, supported gaming and identity events, and the scope of fraud and abuse evaluation. 

**Audience:** API integrators and client developers working with regulated gaming platforms. 

**Applies to: **Legacy Gaming clients implementing transaction‑level fraud and abuse detection via the Gaming API. 

**Does not apply to: **Universal APIs, any other industry, or identity-only use cases without gaming context.
:::
::::

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

:::hint{type="info"}
<font color="#386B84">**Note**</font>: See [iGaming Complete Request Structure](docId\:n1CJz-xfC8oMtMVg4nHvK) 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.&#x20;
- **Account‑centric risk**
  Fraud and abuse often target accounts directly through credential compromise, bonus abuse, or coordinated activity rather than isolated transactions.&#x20;
- **Regulatory oversight**
  Gaming environments are frequently subject to jurisdiction‑specific regulations, which place additional requirements on monitoring, traceability, and risk controls.&#x20;
- **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.&#x20;

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 Requirements](docId\:yuGHwVL8eOn7vCgSwPcd3)** (Constraint) and **[Accertify Hash Algorithm](docId\:rKIK1Lb6EUUWsz3sxPCe-)** (Reference).

## Field Reference

::::LinkArray{contentSource="CUSTOM"}
:::LinkArrayItem
[iGaming preAuth risk scoring](docId\:fLGMkdj5RoClbRuod0DnO)
:::

:::LinkArrayItem
[iGaming postAuth risk scoring](docId\:LIat95wF-WvCT90TiMO5A)
:::

:::LinkArrayItem
[iGaming authorization update](docId\:jQHgLNQn5NBl3Fd7ufz3r)
:::

:::LinkArrayItem
[iGaming fulfillment update](docId\:frJEzjY9Uxka0rbtVQHdz)
:::

:::LinkArrayItem
[iGaming chargeback update](docId\:NLUvpLmnekwMyweEer6Px)
:::
::::