---
title: Withdrawal
slug: legacy-fraud-apis/withdrawal
createdAt: 2026-03-11T19:27:37.009Z
---

::::ExpandableHeading{isOpen="true"}
###

**Topic type: Concept**

:::hint{type="warning"}
**Purpose: **Withdrawal event overview and guidance on when to send the event. 

**Audience:** Developers implementing player withdrawal workflows. 

**Applies to: **Gaming integrations evaluating player withdrawal attempts. 

**Does not apply to: **Account Protection withdrawals or non-gaming events.
:::
::::

The `withdrawal` call is intended to retrieve a Gaming Score and Reason Codes when a Producer attempts to withdraw funds on your website.

### Timing

The API call should come to the Interceptas Platform:

- After a user submits a withdrawal request.
- After they pass error handling, you retrieve their IP Address and User Agent.
- Before you send them the result of their request.

### Flow

![Withdrawal flow diagram - Gaming](https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/3GwGfHAwzxvtXiHbsP2aJ-20260318-154722.png "Withdrawal flow - Gaming")

1. User arrives on site and logs in.
2. User initiates a withdrawal request.
3. Client processes frontend validation to ensure all fields are filled in properly.
4. Client processes backend validation (invalid routing number, verification failed, and so forth).
5. Client retrieves account information, IP, and user agent.
6. Client's backend server calls Accertify.
7. Accertify consolidates data and responds with a score.
8. Client determines appropriate action for the `withdrawal` request.



***

**See also**:

::::LinkArray{contentSource="CUSTOM"}
:::LinkArrayItem
[Withdrawal Fields](docId:5i9j9dY6ERj2N-uuCtY0r)
:::
::::