Platform connection rule and sigature logic

Notice: All data (marked in RED COLOR) needs to be converted to [queryString] with this following pattern: key_1=value_1&key_2=value_2....&api_key=xxxxxxx order by ASCII sorted from small to large (lexicographic order)

Pay particular attention to the following important rules:

1. Parameter names are sorted from small to large (lexicographic order) based on ASCII’s order.

2. Parameter names are case-sensitive.

3. Parameters that do not participate in the signature:

   1. Empty parameter name and value.

   2. Signature Itself in payload data.

   3. Call_back URL.

4. The spacing will be accepted in the [queryString] but no special characters: Ex: “..&player_name=NGUYEN VAN A&...”

Add “&api_key=your_api_key” at the end of the [queryString] then hash the [queryString] with MD5 (Please replace your_api_key with your real api_key given in ATT PAY official website’s admin page)

Take note:

• You can check if the signature is correct by visiting this website: http://www.md5hasher.net/ and parse the [queryString] ( which added api_key ) to generate. If the signature matches, the information is correct.

• All payload data limited in UTF-8.