---
title: Refund
slug: public-apis/refund
createdAt: 2026-03-11T19:10:09.460Z
---

::::ExpandableHeading
###

**Topic type: Concept**

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

**Audience:** Developers implementing refund or reversal workflows.&#x20;

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

**Does not apply to:&#x20;**&#x50;ayment authorization or non-financial identity events.
:::
::::

The `refund` call is intended to retrieve a Recommendation Code when a user attempts to request a refund for goods or services on your website.

### Timing

The API call should come to the Interceptas Platform:

- After a user sends a request for a refund. Requests include: Item Not Recieved, Item Damaged, Refund, and Reship.
- After they pass error handling, and you retrieve their IP Address, and User Agent.
- Before you send the result of their request.

### Flow

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

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



***

**See also**:

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

