Topic type: Constraint
Purpose: Explain hashing requirements for sensitive data submitted to Accertify APIs.
Audience: API integrators and client developers.
Applies to: Accertify APIs that require hashed field submission.
Does not apply to: Internal batch processing or non‑request‑based integrations.
Certain data elements submitted to Accertify APIs must be cryptographically hashed 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.
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:
The specific fields that require hashing are documented in the API ReferenceAPI Reference. 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.
Hashing is not encryption.
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.