---
title: Core Concepts
slug: public-apis/core-concepts
createdAt: 2026-03-04T14:49:39.107Z
---

::::ExpandableHeading
###

**Topic type: Concept**

:::hint{type="warning"}
**Purpose**: Explain how Accertify evaluates fraud risk across events, time, and customer behavior.

**Audience**: API integrators and client developers.&#x20;

**Applies to**: Applies to all Accertify APIs involved in fraud detection and risk assessment.&#x20;

**Does not apply to**: Does not apply to Data Privacy APIs, which exist solely to support regulatory requirements.
:::
::::

## The Accertify Event Model

At the center of Accertify’s risk intelligence is an event. An event represents a specific customer action, transaction, or claim submitted for evaluation at a particular moment in time.&#x20;

Depending on the API, an event may represent a login attempt, a purchase, a return, a dispute, or another fraud‑relevant action.

While each API request describes a single event, **fraud evaluation does not occur in isolation**. Every event is evaluated within a broader analytical context informed by historical data, industry‑specific patterns, and global fraud activity observed across the Interceptas Platform.

:::ExpandableHeading
### What an Event Represents

A fraud event captures the immediate details of a transaction, including:

- The action or transaction being evaluated
- The customer, account, or identity involved
- The merchant or client context
- The device, payment method, or channel
- The timing and surrounding circumstances

This event data provides the **current snapshot** needed to perform evaluation, but it is only one input into the overall decision-making process.
:::

:::ExpandableHeading
### How Events Are Evaluated

Risk evaluation incorporates multiple layers of context beyond the individual event, including:

- **Historical customer behavior**
  Patterns associated with the customer or account over time, where applicable.&#x20;
- **Client‑specific history**
  Observed transaction behavior, fraud outcomes, and risk characteristics associated with the client submitting the event.&#x20;
- **Industry‑specific intelligence**
  Long‑term fraud patterns and behaviors observed within the relevant industry, reflecting how fraud manifests differently across sectors such as Retail, Airline, Travel, Ticketing, Amusement, and iGaming.&#x20;
- **Global and real‑time fraud trends**
  Signals derived from fraud activity occurring across the platform, including emerging patterns that may be developing at the moment the event is evaluated.&#x20;

The submitted event is therefore evaluated as part of a **continuum of observed behavior**, not as a standalone occurrence.
:::

:::ExpandableHeading
### Why This Model Matters

Fraud is inherently adaptive. Risk signals that were reliable in the past may change as fraud techniques evolve, and patterns that appear safe in isolation may indicate elevated risk when viewed in aggregate.

By combining:

- pre‑transaction signals (Account Protection)
- transaction signals (Universal Fraud APIs)
- post‑transaction signals (CARE, Chargeback)

the Accertify APIs provide risk evaluation that reflects both **long‑term trends** and **current conditions&#x20;**&#x61;cross a customer's journey.

This approach allows decisions to incorporate context that cannot be captured by a single event alone, while still enabling real‑time integration at the point where decisions must be made.
:::

:::ExpandableHeading
### Universal Fraud APIs

Universal Fraud APIs implement this event model through a shared transaction structure and industry-specific extensions.

Regardless of industry, every Universal Fraud API evaluates events using the same foundational fraud intelligence framework while allowing additional context to be supplied for industry-specific risk signals.
:::

## The Role of the API Request

The API request supplies the **event‑level data** required for evaluation. It does not attempt to replicate or expose the full historical dataset or analytical processes used by the Interceptas Platform.

Instead, it provides the necessary context for Accertify to:

- correlate the event with historical and industry‑level intelligence,
- apply fraud detection logic informed by ongoing trends, and
- return a decision that reflects the broader risk landscape.



***

**See also**:

::::LinkArray{contentSource="CUSTOM"}
:::LinkArrayItem
[Getting Started](docId\:Mff0KeZ4dG0xsDELd1tae)

Introduce the Accertify APIs and their role within the Accertify Interceptas Platform
:::

:::LinkArrayItem
[Global Constraints](docId\:Hxd7WT2raxTW6NH2h3YN0)

Authentication methods, hashing requirements, and other API parameters
:::

:::LinkArrayItem
[API Reference Page](docId:40sCZ3HvGItTH6c2I6jjA)

Field definitions and requirements for every API
:::
::::

