Legacy Fraud APIs
3 min
\<font color="#b6c7cb">\</font> topic type concept purpose direct users looking for legacy fraud apis to the legacy apis space and prevent confusion between legacy fraud apis and universal fraud apis audience developers, integrators, support engineers, implementation teams, and ai assisted search users applies to legacy fraud apis does not apply to universal fraud apis legacy fraud apis remain available for customers and integrations that have not migrated to the universal fraud api framework \<font color="#386b84"> note \</font> legacy fraud apis are no longer the recommended starting point for new integrations new implementations should use universal fraud apis whenever possible legacy fraud apis are maintained for compatibility with existing integrations documentation for legacy fraud apis has been moved to a separate legacy apis documentation space looking for a legacy fraud api? if you are attempting to find documentation for any of the following legacy apis legacy retail fraud api legacy airline fraud api legacy gaming fraud api legacy travel fraud api legacy amusement fraud api refer to the legacy apis documentation space looking for current fraud apis? if you are implementing a new fraud integration, use the universal fraud apis instead universal fraud apis provide a shared core transaction model industry specific extensions consistent endpoint behavior across industries unified request and response contracts supported industries include retail airline travel ticketing amusement igaming migration guidance organizations currently using legacy fraud apis should evaluate migration to universal fraud apis where appropriate universal fraud apis are the primary documentation source for current fraud integration work