iGaming Extension Overview
4 min
\<font color="#78b5c7">\</font> topic type concept purpose provide an overview of the legacy gaming 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 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 \<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 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 requirements docid\ yughwvl8eon7vcgswpcd3 (constraint) and accertify hash algorithm docid\ rkik1lb6euuwsz3sxpce (reference) field reference igaming preauth risk scoring docid\ flgmkdj5roclbruod0dno igaming postauth risk scoring docid\ liat95wf wvct90timo5a igaming authorization update docid\ jqhglnqn5nbl3fd7ufz3r igaming fulfillment update docid\ frjezjy9uxka0rbtvqhdz igaming chargeback update docid\ nluvplmnekwmyweeer6px