---
title: Account Protection API Overview
slug: public-apis/account-protection-api-overview
createdAt: 2026-03-11T15:17:04.207Z
---

::::ExpandableHeading
###

**Topic type: Concept**

:::hint{type="warning"}
**Purpose:&#x20;**&#x45;xplain how the Account Protection API evaluates risk associated with account activity prior to, during, and outside of a purchase transaction.&#x20;

**Audience:** API integrators and client developers implementing pre‑transaction fraud prevention.&#x20;

**Applies to:&#x20;**&#x43;lients using the Account Protection API for account-level and identity-driven events.&#x20;

**Does not apply to:&#x20;**&#x49;ndustry‑specific Fraud APIs, Dispute APIs, or regulatory‑only APIs such as Data Privacy.
:::
::::

The Accertify Account Protection API evaluates **risk associated with user activity on your website or application**, with a focus on **Account Takeover (ATO)** and **New Account Opening (NAO)** fraud. It is designed to assess risk **before a transaction occurs**, or in cases where no payment is involved at all.

Account Protection operates at the **event level**. Each request represents a specific user action—such as a login attempt, password reset, account update, or withdrawal—that should be evaluated for risk at the moment it occurs.

The API does not take action on accounts directly. Instead, it returns **risk signals and scores** that you use to determine how your systems should respond.

:::ExpandableHeading
## How Account Protection Works

![Account Protection Architecture Data Flow](https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/FWAoUS_tFIxYJkZ4vJDMI-20260318-154721.jpg "Account Protection Architecture")

At a high level, the flow is:

1. A user triggers an event in your application (for example, login or account update).
2. Your system submits the event to the Account Protection API.
3. Accertify evaluates the event using behavioral signals, historical context, and machine‑learning models.
4. The API returns a risk score and supporting details.
5. Your system decides how to proceed.

While each request represents a single event, evaluation does not occur in isolation. Accertify measures **consistency, change, and correlation** across events over time to identify abnormal behavior that may indicate fraud.
:::

:::::ExpandableHeading
## Supported Event Types

The Account Protection API currently supports the following event types.

Each event type has its own expected context and field requirements, which are documented in the linked event‑specific overview pages:

::::VerticalSplit{layout="middle"}
:::VerticalSplitItem
- [accountCreate](docId:_OPUuvx5wyXGMQlkwnp-7)
- [accountUpdate](docId\:bb5PTMhWVNee1vYbobcSg)
- [login](docId\:J1OUfKnGEm49C9R0IuWoA)
- [logout](docId:5h9UfD7Hp1TfIU6dU6Ddv)
- [passwordForgot](docId\:j31c2d4egcmELXyUp-tuO)
- [passwordUpdate](docId\:gtZFcu_mrJYs-7SwyUYJW)
- [usernameForgot](docId\:AOfHG63WbpeqmkEBk8cuR)
- [verification](docId\:re89E0j7wlsnO40d-hccR)
- [payment](docId\:Soon_wRdEXtQcPtXz7y9z)
:::

:::VerticalSplitItem
- [refund](docId\:gHhhZonthcUz3oqlW-C2k)
- [withdrawal](docId\:JeygsgpwNZXlkj6EzhtFk)
- [transfer](docId\:hfoytZ7xK36sv_LtKKfe3)
- [inventoryHold](docId:-M1u_merTwNgWY1XuMBDM)
- [listingCreate](docId\:RKPGQJ7qaKB8lqFbw4y30)
- [listingUpdate](docId\:t0cG3JzEFoOhgEnUvV6Ko)
- [giftCardBalance](docId\:hiyhls1ov4pCVTWmCjAYj)
- [chargeback](docId\:UUxisnkfIrADxRtDln0KX)
:::
::::
:::::

:::ExpandableHeading
## Taking Action

The Account Protection API provides **decision support**, not enforcement.

Using the returned risk score and event details, you determine how your systems respond. Common response patterns include:

- **Preventative actions:**&#x20;
  - Require multi‑factor authentication
  - Reset a password
  - Block or reject a high‑risk action
- **Supportive actions:**
  - Allow one‑click checkout
  - Reduce friction for trusted users
  - Enable expedited flows for low‑risk activity

The appropriate response depends on your business logic, risk tolerance, and regulatory obligations.
:::

:::ExpandableHeading
## Request Origin and Integration Model

Account Protection requests **must be submitted from a back‑end system**. Client‑side JavaScript API submission is not supported.

This requirement exists because:

- Some required data elements are available only from server‑side systems.
- Error handling and retry behavior must be controlled centrally.
- Requests are accepted only from **whitelisted IP addresses.**
- Certain fields require cryptographic hashing prior to transmission.

Details on authentication, hashing, field classification, and validation behavior are documented in **[Global Constraints](docId\:Hxd7WT2raxTW6NH2h3YN0)**.
:::

:::ExpandableHeading
## Field Availability and Imperative Data

Some Account Protection fields are labeled **Imperative**, meaning they provide high‑value signals when available.

Imperative fields should be sent **whenever your system can legitimately provide them**. However, there are valid scenarios where an Imperative field may be unavailable for a given event. In those cases:

- Do not suppress the request
- Do not fabricate placeholder values
- Send the event with the available data

For example, automated attacks may prevent generation of a device identifier, but the event should still be evaluated using the remaining context.

Refer to **[Global Constraints](docId\:Hxd7WT2raxTW6NH2h3YN0)** for full definitions and expectations.
:::

:::ExpandableHeading
## Field Hashing

Prior to sending certain sensitive fields, you must hash the clear-text value using our Accertify Hash Algorithm.

The fields that require hashing are:

- `cardNumber `
- `giftCardNumber `
- `hashedPassword `
- `previousHashedPassword `
- `updatedHashedPassword `

Refer to [Hashing Requirements](docId\:yuGHwVL8eOn7vCgSwPcd3)and [Accertify Hash Algorithm](docId\:rKIK1Lb6EUUWsz3sxPCe-) for more information.
:::

:::ExpandableHeading
## Webhooks and Downstream Actions

Account Protection includes a set of **standard webhooks** that allow Accertify to notify your systems when follow‑up action is recommended.

Webhooks act as a reverse API, enabling Accertify to push messages—such as account‑level actions or payment flags—back to your environment. These notifications are commonly used to:

- Force password resets
- Trigger verification flows
- Flag or cancel suspicious payments
- Apply account‑level restrictions

Webhook payloads may reference a single object or multiple related objects, depending on the action taken.
:::

## Event References

::Image[]{src="https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/4VRPIgGNjk81XwCl3Q2ea-20260326-200545.png" size="34" width="1200" height="600" darkWidth="1200" darkHeight="600" position="center" caption="Account Protection fields" alt="Account Protection fields" showCaption="true"}

::::VerticalSplit{layout="middle"}
:::VerticalSplitItem
### Overviews

- [Account Create](docId:_OPUuvx5wyXGMQlkwnp-7)
- [Account Update](docId\:bb5PTMhWVNee1vYbobcSg)
- [Chargeback](docId\:UUxisnkfIrADxRtDln0KX)
- [Gift Card Balance](docId\:hiyhls1ov4pCVTWmCjAYj)
- [Inventory Hold](docId:-M1u_merTwNgWY1XuMBDM)
- [Listing Create](docId\:RKPGQJ7qaKB8lqFbw4y30)
- [Listing Update](docId\:t0cG3JzEFoOhgEnUvV6Ko)
- [Login](docId\:J1OUfKnGEm49C9R0IuWoA)
- [Logout](docId:5h9UfD7Hp1TfIU6dU6Ddv)
- [Password Forgot](docId\:j31c2d4egcmELXyUp-tuO)
- [Password Update](docId\:gtZFcu_mrJYs-7SwyUYJW)
- [Payment](docId\:Soon_wRdEXtQcPtXz7y9z)
- [Refund](docId\:gHhhZonthcUz3oqlW-C2k)
- [Transfer](docId\:hfoytZ7xK36sv_LtKKfe3)
- [Username Forgot](docId\:AOfHG63WbpeqmkEBk8cuR)
- [Verification](docId\:re89E0j7wlsnO40d-hccR)
- [Withdrawal](docId\:JeygsgpwNZXlkj6EzhtFk)
:::

:::VerticalSplitItem
### Field References

- [Account Create Fields](docId\:BCDXuXrE7ESkKJE0Wsb5U)&#x20;
- [Account Update Fields](docId:-wY_S-KsW48N1_LdOrXP3)
- [Chargeback Fields](docId\:YbElfDICFamnDdzko2Mhn)
- [Gift Card Balance Fields](docId:7jcOH2k-aZAx6T0569IiH)
- [Inventory Hold Fields](docId\:qwW76R-5x9nMLnrk06Bg8)
- [Listing Create Fields](docId:6anGg1YDq-K3_t2DGQSis)
- [Listing Update Fields](docId\:t8tFXkACkwCXfTCLPffhM)
- [Login Fields](docId:0DG-4GT8p9N0pc25js9Z1)&#x20;
- [Logout Fields](docId\:ndCIWn_kYWtPn5wbOxuR9)
- [Password Forgot Fields](docId:35sRKjaeLSXzcA71y0_ur)
- [Password Update Fields](docId\:YoPRMJ4aKJZiPPy8M8mCY)
- [Payment Fields](docId\:CCIFXtapXELaRkiqddC0g)
- [Refund Fields](docId\:XzqfTrtpR-Fdtk__j_jcO)
- [Transfer Fields](docId:0ZUqSflzV-AMuNhTohob-)
- [Username Forgot Fields](docId\:IEgdNIWhw6RKIlNovW6F-)
- [Verification Fields](docId\:RDPe3e4Uo_Q9SpYPN0Dpq)
- [Withdrawal Fields](docId\:zGd5y4l72MZku1cvxWog9)
:::
::::



