---
title: Transfer
slug: public-apis/transfer
createdAt: 2026-03-11T19:10:29.752Z
---

::::ExpandableHeading
###

**Topic type: Concept**

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

**Audience:** Developers implementing fund, value, or asset transfer workflows.&#x20;

**Applies to:&#x20;**&#x41;ccount Protection integrations evaluating internal or external transfer activity for identity risk.&#x20;

**Does not apply to:&#x20;**&#x50;ayments, refunds, or authentication events.
:::
::::

The `transfer` call is intended to retrieve an Account Protection Score when a user attempts to transfer funds, points, or goods on your website. This can apply to external and internal (user to user on your site) transfers.

### Timing

The API call should come to the Interceptas Platform:

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

### Flow

![Transfer flow diagram](https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/celsIgvufhRI5QEqQHsdQ-20260318-154723.jpg "Transfer flow")

1. User arrives on site and logs in.
2. User initiates a transfer 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 `transfer` request.



***

**See also**:

::::LinkArray{contentSource="CUSTOM"}
:::LinkArrayItem{headerType="IMAGE" headerImage="https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/4VRPIgGNjk81XwCl3Q2ea-20260326-200545.png"}
[Transfer Fields](docId:0ZUqSflzV-AMuNhTohob-)
:::
::::

