---
title: Account Update
slug: public-apis/account-update
createdAt: 2026-03-11T19:06:30.209Z
---

::::ExpandableHeading
###

**Topic type: Concept**

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

**Audience:** Developers implementing account profile or settings changes.&#x20;

**Applies to:&#x20;**&#x41;ccount Protection integrations evaluating changes to existing account details.&#x20;

**Does not apply to:&#x20;**&#x41;ccount creation or authentication events.
:::
::::

Call `accountUpdate` when a user attempts to update the address, payment method, password, or other account information post authentication on your website.

### Timing

The API call should come to the Interceptas Platform:

- After a user attempts to update an account.
- After they pass error handling and you retrieve their IP Address and User Agent.
- Before you update the account.

### Important Considerations

- When calling `accountUpdate `we recommend you send all values associated with the account even if they are not being updated.
  - `previousValues`: Send all values from before the update.
  - `updatedValues`: Send all values from after the update (changed or unchanged).
- `emailAddress `is an important field and should always be present with the value post-update. This means, if your site does not allow email updates, the same email address will be passed 3 times in the `emailAddress `field, the `previousValues `block, and the `updatedValues `block.
- We suggest you call the `accountUpdate `event even if something we don't collect is changed.&#x20;

:::hint{type="success" indent="1"}
****<font color="#4f6228">**Example**</font>: Some clients have preferences such as a user's avatar or preferred rental car type.
:::

### Flow

![Account Update flow diagram](https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/bJm4-czvnfBTh-SO3lgwa-20260318-154721.jpg "Account Update flow")

1. User logs in.
2. User goes to Account Update and changes something (address, payment methods, personal info).
3. Client processes frontend validation to ensure all fields are filled in properly.
4. Send changes to backend.
5. Client's backend server calls Accertify with All `previousValues `(before the change) and `updatedValues `(after change) regardless if they changed or not.



***

**See also**:

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

