Legacy Gaming API Overview
Legacy API Notice: This API is part of the Legacy Fraud API framework and is maintained for compatibility with existing implementations.
New integrations should use the Universal Fraud APIs instead.
The Universal Fraud APIs provide:
- A shared core transaction model
- Consistent request and response contracts
- Industry-specific extensions
- Unified documentation and onboarding
- Ongoing feature investment
Use this Legacy API documentation only if:
- You are maintaining an existing Legacy Fraud API integration.
- You have not yet completed migration to Universal Fraud APIs.
- Accertify has specifically directed your implementation to remain on the Legacy API framework.
For new implementations, start with Universal Fraud APIs Overview.
The Accertify Gaming API standardizes how gaming‑related transactions and events are submitted to the Interceptas Platform for fraud and abuse evaluation. It enables gaming operators to integrate quickly while ensuring submitted data is validated and evaluated using industry‑specific machine learning models.
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.
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.
Gaming Events
The Gaming API allows you to submit events when the following actions occur on your website or application:
- accountCreate
- login
- deposit
- withdrawal
Each event type has its own expected context and field requirements, which are documented in the event‑specific reference pages below.
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).
Event References
View field requirements, paths, and try it out!
