---
title: Hashing Requirements
slug: public-apis/hashing-requirements
createdAt: 2026-03-09T12:40:30.092Z
---

::::ExpandableHeading
###

**Topic type: Constraint**

:::hint{type="warning"}
**Purpose**: Explain hashing requirements for sensitive data submitted to Accertify APIs.

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

**Applies to**: Accertify APIs that require hashed field submission.&#x20;

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

Certain data elements submitted to Accertify APIs must be **cryptographically hashed&#x20;**&#x20;prior to transmission. Hashing is a mandatory requirement for specific fields and is enforced as part of request validation and authentication.

Hashing requirements apply consistently across all industries and transaction lifecycle contexts.

:::ExpandableHeading{isOpen="true"}
## Fields Subject to Hashing

Some fields in Accertify APIs are designated as **hash‑required fields**. These fields must be submitted as hashed values rather than plain text.

Hash‑required fields typically include:

- Credentials or authentication‑related values
- Sensitive identifiers
- Values that should not be transmitted or stored in clear form

The specific fields that require hashing are documented in the **[API Reference](docId:40sCZ3HvGItTH6c2I6jjA)**. Clients must follow these requirements exactly.

Within Universal Fraud APIs, hash-required fields appear in both the shared transaction model and industry-specific extensions. Always follow the requirements defined in the API Reference for the specific field being submitted.
:::

:::ExpandableHeading{isOpen="true"}
## Hashing vs Encryption

Hashing is **not encryption**.

- Encryption is reversible with a key.
- Hashing is irreversible and produces a fixed output.

The Fraud APIs require hashing specifically because it allows correlation and verification without exposing sensitive values.

Clients must not substitute encryption where hashing is required.
:::

