Check request

Freedom Pay asks your server whether the order can still be paid: right before the money is charged.

Sent only if Freedom Pay enabled the check for the merchant: contact your Freedom Pay manager.

URL: pg_check_url of the payment request, or the Check URL from the merchant settings. Without a URL the check is skipped.

Not sent for recurring payments.

Signed with the payment secret key: check the signature before you answer.

Common rules for all callbacks (method, signature): see Callbacks Overview.

Payment check flow

After the check the payment goes on as usual: the result comes in Result notify.

Result

Answer with an XML body:

Your answer	Meaning	Next step
XML with `pg_status = ok`	The order can be paid.	Freedom Pay charges the client. Wait for the result in Result notify.
XML with `pg_status = rejected`	The order cannot be paid: for example, it is cancelled or the amount is wrong.	Freedom Pay declines the payment: the client sees an error.
Not XML (an empty body, JSON, HTML), with any HTTP code	The answer is treated as a refusal.	Freedom Pay declines the payment.
Any other XML, for example with `pg_status = error`	The answer is treated as `ok`.	Freedom Pay charges the client.
No answer within 30 seconds, or no connection	The check is skipped.	Freedom Pay charges the client.

The check is not repeated: answer within 30 seconds.

Compare pg_amount and pg_currency with your order before you answer ok.

Request example

pg_check_url = https://merchant.example.com/payment/check.
One field per line for reading: in the POST body the fields are joined with & and the values are URL-encoded.

pg_order_id=order-1001
pg_payment_id=1022123804618
pg_amount=1000
pg_currency=KZT
pg_ps_amount=1000
pg_ps_full_amount=1000
pg_ps_currency=KZT
pg_salt=Hq7mZ2pX5wL9cR3t
pg_sig=13daffe1fc8c7cbc197ab5d40c40ad04

Payment check flow#

Result#

Request example#

Request

Responses

Payment check flow

Result

Request example