---
title: Payment
slug: public-apis/payment
createdAt: 2026-03-11T19:09:49.133Z
---

::::ExpandableHeading
###

**Topic type: Concept**

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

**Audience:** Developers implementing checkout or payment workflows.&#x20;

**Applies to:&#x20;**&#x41;ccount Protection integrations evaluating payments from an identity risk perspective.&#x20;

**Does not apply to:** Withdrawals, transfers, or non-payment identity events.
:::
::::

The `payment` call is intended to retrieve an Account Protection Score when a user attempts to pay for goods or services on your website.

### Timing

The API call should come to the Interceptas Platform:

- After a user submits an order.
- After they pass error handling, and you retrieve their account details, IP Address, and User Agent.
- Before you send the result of their request.

:::hint{type="info"}
<font color="#386B84">**Note**</font>: If you already use the Interceptas Platform for payment fraud screening and send all payments there, Accertify can call this event on your behalf, so you don't have to code this event.
:::

### Flow

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

1. User chooses a product, checks out, enters details, and submits order.
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 payment was successful or a failure.
5. &#x20;Accertify consolidates data and returns a score.
6. Client determines to process the transaction 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"}
[Payment Fields](docId\:CCIFXtapXELaRkiqddC0g)
:::
::::

