Hashing Requirements
2 min
\<font color="#78b5c7">\</font> topic type constraint purpose explain hashing requirements for sensitive data submitted to apis audience api integrators and client developers applies to apis that require hashed field submission does not apply to internal batch processing or non‑request‑based integrations certain data elements submitted to 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 fields subject to hashing some fields in 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 hashing vs encryption hashing is not encryption encryption is reversible with a key hashing is irreversible and produces a fixed output the apis require hashing specifically because it allows correlation and verification without exposing sensitive values clients must not substitute encryption where hashing is required