Page History
...
Parameter | Mandatory field | Adopted values | Default value | Description | |||||
Merchant_ID | Yes | Number | The enterprise merchant identifier in IPS Assist | ||||||
OrderNumber | Yes | 128 characters | Order number in the merchant payments system | ||||||
Delay | No | 0 – one-stage operation | 0 | Attribute of a bankcard authorization for the double-stage operation mode.
| |||||
Language | No | RU – Russian, | Language of legal entity/enterprise | Language of authorized pages | |||||
OrderComment | No | 256 4000 characters | Comment. | ||||||
OrderAmount | Yes | Number, 15 digits, two digits after the delimiter (delimiter : '.') | Payment amount, in original currency (e.g., 10.34). | ||||||
OrderCurrency | No | 3 characters | Currency of legal entity/enterprise | Code of currency of the OrderAmount (For currency codes refer to currency codes) . | |||||
Lastname | No | 70 characters | Customer's last name. | ||||||
Firstname | No | 70 characters | Customer's first name. | ||||||
Middlename | No | 70 characters | Customer's middle name. | ||||||
No | 128 characters | Customer's e-mail. | |||||||
Address | No | 256 characters | Customer's address. | ||||||
HomePhone | No | 64 characters | Customer's home phone number. | ||||||
WorkPhone | No | 20 characters | Customer's work phone number. | ||||||
MobilePhone | No | 20 characters | Customer's mobile phone number. | Fax | No | 20 characters | |||
Customer's fax number. | Country | No | 3 characters | Customer's country. | |||||
State | No | 3 characters | Customer's region. | ||||||
City | No | 70 characters | Customer's city. | ||||||
Zip | No | 25 characters | Customer's post zip code. | ||||||
URL_RETURN | No | 256 characters | Page URL, to where a customer should return after performing his/her payment in the system (option "Go to the shop page" should be enabled in merchant's settings in Personal account). ). It is recommended to use HTTPS protocol for secure communication. | ||||||
URL_RETURN_OK | No | 256 characters | URL_RETURN parameter value, or, if none, return URL parameter after successful authorization, specified in Personal account | Page URL, to where a customer should return after successful performing his/her payment in IPS Assist (option "Go to the shop page" should be enabled in merchant's settings in Personal account)). It is recommended to use HTTPS protocol for secure communication. | |||||
URL_RETURN_NO | No | 256 characters | URL_RETURN parameter value, or, if none, return URL specified in Personal account | Page URL, to where a customer should return if the payment is not performed in IPS Assist or payment is still in progress (current payment status "In Progress"), see details. The option "Go to the shop using return URL" should be enabled in merchant's settings in Personal account. It is recommended to use HTTPS protocol for secure communication. | |||||
CardPayment | No | 1 – pay using bankcard,; | 1 | A customer can perform his/her payment using bankcard, if parameter value 1 has been sent, or the parameter is missing (and bankcard payments are enable for the enterprise) | |||||
YMPayment | No | 1 – use YandexMoney payment system, | 1 | A customer can perform his/her payment using YandexMoney payment system, if parameter value 1 has been sent, or the parameter is missing (and YandexMoney payments are enable for the enterprise) | |||||
WMPayment | No | 1 – use WebMoney payment system, | 1 | A customer can perform his/her payment using WebMoney payment system, if parameter value 1 has been sent, or the parameter is missing (and WebMoney payments are enable for the enterprise) | |||||
QIWIPayment | No | 1 – use QIWI payment system, | 1 | A customer can perform his/her payment using QIWI payment system, if parameter value 1 has been sent, or the parameter is missing (and QIWI payments are enable for the enterprise) | |||||
QIWIMtsPaymentFastPayPayment | No | 1; 0 | 0 | A customer can perform his/her payment using the Faster Payment System, if parameter value 1 has been sent and payments via FPS are enable for the enterprise. | |||||
GooglePayPayment | No | 1; 0 | Payment with mobile phone money (MTS) | 0 | Payment via Google Pay attribute (=1) | ||||
ApplePayPaymentQIWIMegafonPayment | No | 1; 0 | 10 | Payment with mobile phone money (Megafonvia Apple Pay attribute (=1) | |||||
QIWIBeelinePaymentSamsungPayPayment | No | 1; 0 | 10 | Payment with mobile phone money (Beelinevia Samsung Pay attribute (=1) | |||||
QIWITele2PaymentMirPayPayment | No | 1; 0 | 10 | Payment with mobile phone money (Tele2via Mir Pay attribute (=1) | |||||
Signature | No* | String | The string is joined according the determined rules Then the MD5 hash prepared from this string. Hash is signed by private RSA key of the merchant. Key length - 1024. Received bit sequence is a signature. Signature is transferred BASE64 coded string.
| ||||||
Checkvalue | No* | String | Request validation code. The string has to be generated as follows: uppercase(md5(uppercase(md5(SALT) + md5(Х)))), where SALT – secret word; Х – the string joined according the determined rules. Note. If the merchant uses request validation code without delimiters, please, contact the support team support@assist.ru
| ||||||
MobileDevice | No | 0 – use merchant's settings; | 0 | Payment pages type (standard or for mobile devices). If no values passed for this parameter in the request then default merchant setting is used (standard pages). In order to switch to the device auto detection mode, please, contact the support team support@assist.ru. | |||||
RecurringIndicator | No | 1 – recurrent payment | 0 | Recurring payment indicator | |||||
RecurringMinAmount | No/Yes | Number, 15 digits, two digits after the delimiter (delimiter '.') | Min amount of recurrent payments. | ||||||
RecurringMaxAmount | No/Yes | Number, 15 digits, two digits after the delimiter (delimiter '.') | Max Amount of recurrent payments. | ||||||
RecurringPeriod | No/Yes | Number, 10 3 digits | Frequency of recurrent payments in days. | ||||||
RecurringMaxDate | No/Yes | Date as string in DD.MM.YYYY format | The end date of recurrent payments. | ||||||
GooglePayPaymentAccount | No | 1; 0 | 0 | Payment via GooglePay attribute (=1) | |||||
ApplePayPayment | No | 1; 0 | 0 | Payment via ApplePay attribute (=1) | |||||
SamsungPayPayment | No | 1; 0 | 0 | Payment via SamsungPay attribute (=1) | FastPayPayment | No | 1; 0 | 0 | Permission to pay via Faster Payment System (=1)|
/Yes** | 30 symbols/12 digits** | Number of the contract or personal account of the buyer | |||||||
Disable3DS | No | 0 - perform 3D-Secure authorization according to the merchant settings; 1 - fulfill payment without 3-D Secure. | 0 | Flag of disabling 3-D Secure.
|
* In order to protect the transmitted data from the possibility of their substitution by intruders, one of the parameters (Signature or Checkvalue) must be passed, and the setting for the check value (or signature) in the Personal account must also be enabled.
**for merchants with mcc 4814 (Telecommunications services), you must pass a billed phone number in the parameter.
Expand | |||||
---|---|---|---|---|---|
| |||||
|
...
Code Block | ||
---|---|---|
| ||
http://URL return/?billnumber=complete_unique_order_number&ordernumber=order_number |
If the parameters URL_RETURN_OK and URL_RETURN_NO are not sent in the authorization request, then URL_RETURN parameter value is used for a customer's automatic redirection. If this parameter is also not sent, then the return URL_RETURN_OK and URL specified in "Merchants settings" section in Personal account are used.
Note |
---|
When customer returns to the merchant site the value of the order number is always transmitted as URL-encoded string: all non alpha-numeric characters (except '-' and '_'.) are replaced by the percent sign '%' followed by two digits hex code; spaces are replaced by '+' sign. This is important when the order number contains characters of non latin alphabet or some special symbols. |
When using the option of a customer's return to the shop, it is recommended to sent an additional request about the authorization result to IPS Assist server after receiving data about the paid order at URL_RETURN_OK (see details) in order to make sure the order payments have been performed. It is recommended as well to send an additional request about the authorization result to IPS Assist server after receiving data about the paid order at URL_RETURN and URL_RETURN_NO, because a customer is redirected to these addresses with different payment state, including the state "In process".