Payment ID in the merchant system It is recommended to keep this field unique
pg_amount
number
required
Payment amount in pg_currency
>= 0.01
pg_currency
string
optional
Currency in which the amount is specified
pg_description
string
required
Payment description (These parameters may include parameters from other sections. For the effective operation of SecureBox, it is recommended to follow the validation guidelines and field examples from this section)
pg_testing_mode
integer
optional
Payment mode 0 - production, 1 - test. If the mode is not specified, then the mode set in the shop settings is taken
>= 0<= 1
pg_user_id
string
optional
User ID in the merchant's system (These parameters may include parameters from other sections. For the effective operation of SecureBox, it is recommended to follow the validation guidelines and field examples from this section)
Example:
No65GFR755789T
pg_user_email
string<email>
optional
Payer's email or email linked (specified during registration) to the personal account ID or wallet number of the payer. (These parameters may include parameters from other sections. For the effective operation of SecureBox, it is recommended to follow the validation guidelines and field examples from this section)
Example:
example@site.com.
pg_user_phone
string
optional
Payer's phone number or phone number linked (specified during registration) to the personal account ID or wallet number of the payer. Digits without spaces, plus signs, or parentheses (These parameters may include parameters from other sections. For the effective operation of SecureBox, it is recommended to follow the validation guidelines and field examples from this section)
pg_card_pan
string
required
Card number
>= 13 characters<= 20 characters
pg_card_cvc
integer
required
CVC/CVC2/CVV card password
pg_card_year
integer
required
Card expiration year
pg_card_month
integer
required
Card expiration month
pg_card_name
string
required
Name and surname of card holders
Example:
John Doe
pg_auto_clearing
boolean
optional
Clearing type (0 or 1) 1 - automatic write-off after successful authorization, 0 - write-off by launching the clearing method
pg_3ds_challenge
boolean
optional
Determines the need to complete the Challenge Flow (1 - it is mandatory to conduct the Challenge Requested, 0 or empty - the method is determined by the issuer) the issuing bank can ignore this parameter and make a payment according to its own Challenge Flow
pg_exchange_params
object
optional
Exchange rate parameters passed when a fixed rate needs to be used
rate
string
optional
The exchange rate provided by the merchant. Payments will be converted using this exact rate.
rates_code
string
optional
Unique currency rate source identifier. Contact your account manager to obtain this code.
ex_date
string
optional
Historical date for applying the exchange rate. If empty, current date applies.
pg_param1
string
optional
Additional parameter 1
pg_param2
string
optional
Additional parameter 2
pg_param3
string
optional
Additional parameter 3
pg_recurring_start
integer
optional
Flag that accepts a value of 0 or 1. For detailed information, see the Recurrent Payments section. To use this parameter, please contact your account manager.
Examples:
01
pg_recurring_lifetime
integer
optional
The duration for which the merchant intends to use the recurrent payment profile. Minimum allowed value: 1 (1 month). Maximum allowed value: 156 (13 years).
>= 1<= 156
pg_salt
string
required
Random string consisting of arbitrary numbers and Latin letters