Retail Extension Overview
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.
Note: See Retail Complete Request Structurerr 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 RequirementsHashing Requirements (Constraint) and Accertify Hash AlgorithmAccertify Hash Algorithm (Reference).