---
title: Legacy Fraud APIs
slug: legacy-fraud-apis
createdAt: 2026-08-24T14:44:29.276Z
---

::::ExpandableHeading
###

**Topic type: Concept**

:::hint{type="warning"}
**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.

:::hint{type="info"}
<font color="#386B84">**Note**</font>:&#x20;

- 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.