Overview
Query Mechanics
Content-type equal to form-data or x-www-form-urlencodedIt is recommended to maintain a delay of
1500–2000 milliseconds (1.5–2 seconds) between consecutive payment API requests to prevent duplicate transactions and avoid triggering rate limiting or anti-fraud mechanismsData can be sent:
{{domain}}/script.php?param_1=val¶m_2[subParam_1]=val2& param_2[subParam_2]=val3¶m_3=val4<?xml version="1.0" encoding="utf-8"?><request><pg_param1>value1</pg_param><pg_param2>value2</pg_param></request>Signature Formation
;:1.
/ to the end or ?).2.
pg_salt, which consists of an arbitrary number of digits and Latin letters.3.
4.
secret_key, which is set in the store settings and is known only to the merchant and FreedomPay.pg_sig. The MD5 hash is recorded as a 32-character lowercase hexadecimal string.Either party may add additional parameters to the request or response that are not specified in the documentation. These parameters also participate in the signature calculation. A message is not signed, and thus the fields
pg_salt and pg_sig are absent only in one case – when FreedomPay could not identify the merchant and therefore does not know its secret_key. In such a case, the field pg_error_code (numeric error code) takes the value 9998.For a complete list of possible values of the field
pg_error_code, see the Error Code Reference section.Example of request with signature
PHP example