Generating Terms and Conditions hashes

For compliance reasons it is required to show the customers Terms and Conditions documents. A merchant is obligated to receive a confirmation from a customer that the documents are read and accepted. A merchant should send the SHA256 hashes for compliance documents when creating or updating a customer using designated parameters:

  • Privacy Policy - accepted_privacy_policy_hash

  • Terms and Conditions - accepted_terms_and_conditions_hash

  • Terms of Service - accepted_terms_of_service_hash

Example of a script for hash generation: Generating Terms and Conditions Hashes for Compliance

The generated hashes must be included in the following API when creating or updating users:

The latest documents version at the time of writing is here:

Hashes for testing

  1. Privacy Policy +hKGaGhIRpUJAW9vMG5y51WMvbTOYb8C1Ln42IuTX4A=

  2. Terms and Conditions HqKJAiAyPqBFOs386w6EVO5KlKQt5z8EzGvSB+iQeTQ=

  3. Terms of Service lIPG8x6y+ObLv5bDWhn8h7QP0z221Iu3Ge1rLH4uvHI=

Last updated