Hash Validations

Transaction Identifier (Hash)

For most transactional API endpoints, you must provide a unique transaction identifier, referred to as a "hash." This hash must be different for every transaction, even if a user is retrying an old transaction. Maintaining the uniqueness of the hash is crucial to ensure each transaction has a distinct result and to associate users with their transactions effectively.

Hash Format

The hash must be in MD5 string format.

Generating a unique hash is your responsibility, and you should use a suitable algorithm.

We strongly advise against using simplistic hashing methods, such as hashing only a timestamp, to minimize the risk of collisions with other customers using similar techniques.

Repeated Hash Error

When you attempt to use a hash that already exists in our records, you will receive an error similar to the following:

{
    "success": false,
    "message": "INVALID_OR_INCOMPLETE_PARAMS",
    "data": [
        {
            "param": "hash",
            "message": "HASH_ALREADY_EXISTS"
        }
    ]
}

Please ensure that you adhere to best practices when generating unique and distinctive hashes. This approach will help maintain transaction integrity and prevent conflicts with other users' transactions.

Hash Validations

Hash Validations#

Transaction Identifier (Hash)#

Hash Format#

Repeated Hash Error#

Hash Validations

Transaction Identifier (Hash)

Hash Format

Repeated Hash Error