Payment ID in the merchant system. It is recommended to keep this field unique.
Example:
00102
pg_merchant_id
integerÂ
required
Merchant ID in {{project}}. Issued upon connection.
pg_amount
numberÂ
required
Payment amount in pg_currency. Minimum 0.01.
Example:
10
pg_description
stringÂ
required
Description of the product or service. Displayed to the customer during the payment process.
Example:
Ticket
pg_salt
stringÂ
required
Random string.
Example:
some random string
pg_sig
stringÂ
required
Request signature.
pg_currency
stringÂ
optional
The currency in which the amount is specified. KZT
Example:
KZT
pg_check_url
stringÂ
optional
URL to check the possibility of payment. Called before the payment
pg_result_url
stringÂ
optional
URL to report the result of the payment. Called after payment on success or failure.
pg_request_method
stringÂ
optional
GET
Example:
POST
pg_success_url
stringÂ
optional
URL to which the user is sent in case of a successful payment (for online systems only).
pg_failure_url
stringÂ
optional
URL to which the user is sent in case of unsuccessful payment (for online systems only).
pg_success_url_method
stringÂ
optional
GET is a button that is submitted by the GET method. POST is a button that is submitted using the POST method.
Example:
GET
pg_failure_url_method
stringÂ
optional
GET is a button that is submitted by the GET method. POST is a button that is submitted using the POST method.
Example:
GET
pg_site_url
stringÂ
optional
URL of the merchant's site to show the buyer a link by which they can return to the merchant's site after creating an account. Applies to offline PS (cash).
Example:
http://site.kz/return
pg_lifetime
integerÂ
optional
Default: 86400. Time (in seconds) during which the payment must be completed. Minimum: 300 seconds (5 minutes). Maximum: 604800 seconds (7 days).
Example:
86400
pg_user_phone
stringÂ
optional
The user's phone number (starting with the country code). If not specified
Example:
77777777777
pg_user_contact_email
stringÂ
optional
User's contact email address. If specified
Example:
mail@customer.kz
pg_user_ip
stringÂ
optional
Client's IP address. Necessary for the analysis of disputable situations in case of suspected fraud.
Example:
127.0.0.1
pg_language
stringÂ
optional
The language of the payment pages on the {{project}} site and (if possible) payment systems. Options: 'en'
Example:
ru
pg_testing_mode
integerÂ
optional
Creating a payment in test mode.
Example:
1
pg_user_id
stringÂ
optional
User ID in the merchant system.
Example:
No65GFR755789T
pg_param1
stringÂ
optional
Additional parameter 1.
Example:
Additional information
pg_param2
stringÂ
optional
Additional parameter 2.
Example:
Additional information
pg_param3
stringÂ
optional
Additional parameter 3.
Example:
Additional information
pg_payment_method
stringÂ
optional
Value - Payment method. Example: mobile_commerce.
Example:
mobile_commerce
pg_generate_qr
booleanÂ
optional
In case you want to receive a QR code with a link to the {{project}} payment form in base64 format
Example:
1
pg_commission_discount
booleanÂ
optional
If you want to use a discount on the commission
Example:
1
pg_commission_discount_fix
numberÂ
optional
To use a fixed discount amount.
pg_commission_discount_percentage
numberÂ
optional
To use a percentage discount.
pg_idempotency_key
stringÂ
optional
Idempotency key. Used to prevent duplicate request creation. A unique value within the merchant's scope; the same key cannot be used for different operations.
The unique identifier of the payment transaction in {{project}}. Serves as a key for all further work with the transaction.
pg_redirect_url
stringÂ
required
The URL to redirect the user to. It can be both on the site {{site}} and on the site of the payment system.
pg_redirect_url_type
stringÂ
required
The type of page to which the redirect occurs. Possible values:
need data: Dialogue with the buyer to clarify the parameters (e.g., payment system, phone number, required parameters).
payment system: Page of the payment system website or a page with instructions for paying through this payment system.
If the merchant receives a response with pg_redirect_url_type="need data", the merchant may not redirect the buyer to the received URL but clarify missing parameters on your site. After specifying the parameters and re-requesting the creation of a payment transaction, a new transaction will be created.
pg_redirect_qr
stringÂ
optional
URL to redirect the user as a QRCode. Transmitted in base64 format.