Authentication & Signature

Notice:

All parameters marked in RED COLOR must be converted into a [queryString] using the following format: key_1=value_1&key_2=value_2&...&api_key=xxxxxxx

All parameters must be sorted in ascending ASCII (lexicographic) order before generating the signature.

Important Rules

Please pay close attention to the following rules when generating the signature:

Parameter names must be sorted in ascending ASCII (lexicographic) order.

Parameter names are case-sensitive.

The following parameters must NOT be included in the signature calculation:
a. Parameters with empty names or empty values.
b. The signature field itself in the request payload.
c. The callback_url parameter.

Spaces are allowed in the [queryString], but special characters are not permitted.
Example: ...&player_name=NGUYEN VAN A&...

After constructing the [queryString], append the following parameter to the end: &api_key=your_api_key. Then generate the MD5 hash of the complete [queryString].

Note: Replace your_api_key with the actual API key provided in the ATT PAY official admin portal.

Additional Notes:

You may verify the generated signature by visiting http://www.md5hasher.net/ and hashing the complete [queryString] (including the appended api_key).
If the generated hash matches the signature, the data is valid.

All payload data must be encoded in UTF-8.

Important Rules#

Important Rules