Generating Terms and Conditions hashes#
For compliance reasons, it is required to present Terms and Conditions documents to customers.
The merchant is obligated to receive confirmation that the documents have been read and accepted. The merchant should send SHA256 hashes of compliance documents when creating or updating a customer using the designated parameters:
- Privacy Policy -
accepted_privacy_policy_hash - Terms and Conditions -
accepted_terms_and_conditions_hash - Terms of Service -
accepted_terms_of_service_hash
An example script for hash generation is available here: Generating Terms and Conditions Hashes for Compliance
The generated hashes (base64-encoded) must be included in the following APIs when creating or updating users:
For a new user:
For an existing user:
The latest versions of the documents at the time of writing are available here:
- Privacy Policy - https://objects.xgateway.tech/policies/bank-transfer/privacy-policy.pdf
- Terms and Conditions - https://objects.xgateway.tech/policies/bank-transfer/T&C.pdf
- Terms of Service - https://objects.xgateway.tech/policies/bank-transfer/ToU.pdf
While we make every effort to keep this page up to date, some information may become outdated. Merchants will be notified in advance of any documentation changes, allowing sufficient time to update and support their existing customers.
Hashes for testing
- Privacy Policy
bnHdpiGWwmIAis8TxOE2w57cyFAHu1EY8UVaeoRqOkw= - Terms and Conditions
HqKJAiAyPqBFOs386w6EVO5KlKQt5z8EzGvSB+iQeTQ= - Terms of Service
txe1kBGpON3xpEWHmifnZolpxg54lW0oPe+J/5py8xQ="