---
title: Withdrawal
slug: public-apis/withdrawal
createdAt: 2026-03-11T19:11:22.633Z
---

::::ExpandableHeading
###

**Topic type: Concept**

:::hint{type="warning"}
**Purpose:&#x20;**&#x57;ithdrawal event overview and guidance on when to send the event.&#x20;

**Audience:** Developers implementing fund withdrawal workflows.&#x20;

**Applies to:&#x20;**&#x41;ccount Protection integrations evaluating withdrawal activity for identity risk.&#x20;

**Does not apply to:&#x20;**&#x47;aming withdrawals or non-financial identity events.
:::
::::

The `withdrawal` call is intended to retrieve an Account Protection Score when a Producer attempts to withdraw funds on your website.

### Timing

The API call should come to the Interceptas Platform:

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

### Flow

![Withdrawal flow diagram Withdrawal flow - Account Protection](https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/kyvMQ6zUwR9J4sY3qjytf-20260318-154723.jpg "Withdrawal flow - Account Protection")

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 back-end 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{headerType="IMAGE" headerImage="https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/4VRPIgGNjk81XwCl3Q2ea-20260326-200545.png"}
[Withdrawal Fields](docId\:zGd5y4l72MZku1cvxWog9)
:::
::::

