---
title: Transaction Lifecycle Contexts
slug: public-apis/transaction-lifecycle-contexts
createdAt: 2026-03-09T14:10:22.838Z
---

::::ExpandableHeading
###

**Topic type: Constraint**

:::hint{type="warning"}
**Purpose**: Explain transaction lifecycle contexts and how they affect event submission and processing.

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

**Applies to**: Explain transaction lifecycle contexts and how they affect event submission and processing.&#x20;

**Does not apply to**: Internal batch processing or non‑request‑based integrations.
:::
::::

Accertify API requests represent transactions at specific points in their lifecycle. These lifecycle contexts determine **how an event should be interpreted**, **which data is expected**, and **which Importer ID and endpoint configuration applies**.

Accertify APIs support multiple transaction lifecycle contexts to reflect how transactions evolve over time. Each context represents a distinct evaluation moment with different expectations and constraints.

The primary lifecycle contexts are:

- Universal Fraud API preAuth
- Universal Fraud API postAuth
- Universal Fraud API Update workflows

Each context may be associated with a **different Importer ID**, even when the underlying transaction relates to the same customer or order. (See [Importer ID and Endpoint Provisioning](docId\:y8UkvWykacAfL-X06Y-Hf).)

## Universal Fraud API Mapping

The Universal Fraud APIs implement transaction lifecycle contexts through:

- preAuth
- postAuth
- authorizationUpdate
- fulfillmentUpdate
- chargebackUpdate

:::ExpandableHeading
## Pre-Authorization Lifecycle Context

A **Pre‑Authorization** event represents a transaction **before final authorization or fulfillment**.

**This context is typically used when:**

- A transaction is being evaluated prior to approval
- Funds have not yet been captured
- The outcome of the fraud decision may influence whether the transaction proceeds

**Pre‑Authorization events often emphasize:**

- Intent and risk assessment
- Initial payment and device context
- Customer behavior signals available at checkout

Pre‑Authorization requests are commonly associated with Importer IDs configured specifically for pre‑decision evaluation.
:::

:::ExpandableHeading
## Post-Authorization Lifecycle Context

A **Post‑Authorization** event represents a transaction **after authorization has occurred**.

**This context is typically used when:**

- Authorization has already been granted
- Additional fraud evaluation is required
- Downstream actions (such as review, reversal, or escalation) are being considered

**Post‑Authorization events may include:**

- Finalized payment details
- Authorization outcomes
- Additional context not available earlier in the transaction flow

Post‑Authorization events are often sent to a different Importer ID than Pre‑Authorization events, reflecting different processing rules and expectations.
:::

:::ExpandableHeading
## Update Lifecycle Context

An **Update** event represents a change to a previously submitted transaction.

**This context is typically used when:**

- Transaction details have changed
- Additional information has become available
- Corrections or adjustments are required

Update events do not represent new transactions. They modify or augment an existing event and must reference the original transaction identifier.

**Update requests may be associated with:**

- A dedicated Importer ID, or
- The same Importer ID as the original event, depending on client configuration
:::

