---
title: Retail Extension Overview
slug: public-apis/retail-extension-overview
createdAt: 2026-03-10T14:33:44.820Z
---

::::ExpandableHeading
###

**Topic type: Concept**

:::hint{type="warning"}
**Purpose**: Legacy Retail API overview, differences, and hashing requirements.&#x20;

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

**Applies to**: Legacy Retail clients implementing via API.

**Does not apply to**: Universal APIs, any other industry, or retail clients who opt for a non-API integration.
:::
::::

The Universal Retail API extends the Universal Fraud API shared transaction model for consumer goods, fulfillment-oriented purchases, and retail payment workflows.

Retail transactions use the same shared transaction structure as all Universal Fraud APIs and add retail-specific context such as line-item, fulfillment, and delivery information.

## Retail Extension Model

The Universal Retail API consists of:

- Shared Transaction Model
- Account Information
- Payment Information
- Item Information
- Address Information
- Retail-specific fulfillment context

This approach allows Retail integrations to share a common foundation with every other Universal Fraud API while preserving industry-specific risk signals.

:::hint{type="info"}
<font color="#386B84">**Note**</font>: See [Retail Complete Request Structure](docId:72NOkbQ7AifqOp5RGqtsp) for the full path.
:::

## What Makes Retail Different

Retail implementations typically emphasize:

- **Line items** (what was purchased, quantity, price, discounts)
- **Fulfillment and delivery context** (shipping vs pickup patterns, address usage)
- **Payment method mix** (single tender vs split tenders, wallet vs card, etc.)

Retail clients can vary significantly (product types, checkout flows, fulfillment models). This is why the field requirement model is important.

## Hashing Requirements

The Retail API follows the platform hashing rules. Fields designated as hash-required must be hashed before submission, including:

- `giftCardNumber`
- `hashedPassword`

See: **[Hashing Requirements](docId\:yuGHwVL8eOn7vCgSwPcd3)** (Constraint) and **[Accertify Hash Algorithm](docId\:rKIK1Lb6EUUWsz3sxPCe-)** (Reference).

## Field Reference

::::LinkArray{contentSource="CUSTOM"}
:::LinkArrayItem
[Retail pre-authorization risk score](https://atlas.accertify.com/public-apis/retail-pre-authorization-risk-score)
:::

:::LinkArrayItem
[Retail post-authorization risk score](https://atlas.accertify.com/public-apis/retail-post-authorization-risk-score)
:::

:::LinkArrayItem
[Retail fulfillment update](https://atlas.accertify.com/public-apis/retail-fulfillment-update)
:::

:::LinkArrayItem
[Retail chargeback update](https://atlas.accertify.com/public-apis/retail-chargeback-update)
:::

:::LinkArrayItem
[Retail authorization update](https://atlas.accertify.com/public-apis/retail-authorization-update)
:::
::::

