Legacy Gaming API Overview

\<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 \<font color="#386b84"> legacy api notice \</font> 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 gaming api standardizes how gaming‑related transactions and events are submitted to the 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 requirements docid\ yughwvl8eon7vcgswpcd3 (constraint) and accertify hash algorithm docid\ rkik1lb6euuwsz3sxpce (reference) event references view field requirements, paths, and try it out! overviews account create docid 4i3sabac9s3ax6mv3npjx login docid\ s oj6c7dvgz0pfwtl190s deposit docid\ ntfvpsx 4a7jkq4r1bvpp withdrawal docid 2w6 ccm6l0otj49pbalhd field references account create fields docid 1 npbjcpcf4o5yvwnwgyp login fields docid 60jplhtjtfaj5a3vsypm6 deposit fields docid\ hd1csgklemfbc6rfwp iq withdrawal fields docid 5i9j9dy6erj2n uucty0r