---
title: Deposit
slug: legacy-fraud-apis/deposit
createdAt: 2026-03-11T19:27:29.316Z
---

::::ExpandableHeading
###

**Topic type: Concept**

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

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

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

**Does not apply to: **Account creation, authentication, or non-financial events.
:::
::::

The `deposit` call is intended to retrieve a Score and Reason Codes when a user attempts to deposit money on your website or application.

### Timing

The API call should come to the Interceptas Platform:

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

### Flow

![Deposit flow diagram](https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/K_7JFPeIXgB9zmk2pT5rQ-20260318-154722.png "Deposit flow")

1. User navigates to client website and clicks deposit.
2. Client processes front end validation to ensure all fields are filled in properly.
3. Client retrieves account information, IP, and user agent.
4. Client's backend server calls Accertify whether the deposit was successful or a failure.
5. Accertify consolidates data and returns a score.
6. Client determines to process the transaction or not.



***

**See also**:

::::LinkArray{contentSource="CUSTOM"}
:::LinkArrayItem
[Deposit Fields](docId\:Hd1cSgkLEmfBc6rFWP_Iq)
:::
::::