Page History
...
Name | Manda- | Accepted values | Default value | Description | ||||
Merchant_ID | Yes | Number | Merchant identification number in IPS Assist | |||||
Login | Yes | String | Service Login | |||||
Password | Yes | String | Password | |||||
OrderNumber | Yes/No | 128 symbols | Order number (order identification on the merchant side) | |||||
OrderAmount | Yes | Number, 15 digits, two digits after the delimiter (delimiter '.') | Payment amount (ex.: 10.34) | |||||
OrderCurrency | No | 3 symbols | Default currency of enterprise or merchant | Order currency code (for OrderAmount value) Ex.: RUB, USD, EUR and so on. | ||||
OrderComment | No | 4000 symbols | Order comment | |||||
Delay | No | 0 - one stage payment, | 0 | Flag for selection of one or two payment stages
| ||||
Language | No | RU - Russian | Enterprise or merchant language | Language of payment pages | ||||
ClientIP | No/Yes | IP-address of customer. The parameter is mandatory for the 3-D Secure protocol version 2. | ||||||
Cardtype | No | 1 - VISA | Card type | |||||
Cardnumber | Yes | Card number | ||||||
Cardholder | No* | 70 letters (no digits). Space as delimiter | Card-holder | |||||
Expiremonth | Yes | 1-12 | Card expiration month | |||||
Expireyear | Yes | Year in YYYY format | Card expiration year | |||||
Cvc2 | Yes | CVC2 code | ||||||
Lastname | No* | 70 letters (no digits) | Customer second name | |||||
Firstname | No* | 70 letters (no digits) | Customer first name | |||||
Middlename | No | 70 letters (no digits) | Customer middle name | |||||
No* | 128 symbols | E-mail of customer | ||||||
Address | No | 256 symbols | Customer address | |||||
HomePhone | No | 64 symbols | Customer home phone | |||||
WorkPhone | No | 20 symbols | Customer work phone | |||||
MobilePhone | No | 20 symbols | Customer mobile phone | |||||
Country | No | 3 symbols | Customer's country code | |||||
State | No | 3 symbols | Customer's region code | |||||
City | No | 70 symbols | Customer's city | |||||
Zip | No | 25 symbols | Customer's postal index | |||||
isConvert | No | 0 - don't convert to the base currency | 1 | Currency conversion indicator | ||||
Format | No | 1 - CSV | 1 | Results format. If the request is sent in SOAP or in JSON format, then the response will also be in SOAP or in JSON respectively, in other cases, in accordance with the passed format value. | ||||
Signature | No | String | The string is joined according to 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.
| |||||
RecurringIndicator | No | 1 - recurring payment | 0 | Recurring payment indicator
| ||||
RecurringMinAmount | No/Yes | Number, 15 digits, two digits after the delimiter (delimiter '.') | Minimum payment amount for recurring payments. Mandatory when RecurringIndicator = 1.
| |||||
RecurringMaxAmount | No/Yes | Number, 15 digits, two digits after the delimiter (delimiter '.') | Maximum payment amount for recurring payments. Mandatory when RecurringIndicator = 1
| |||||
RecurringPeriod | No/Yes | 3 digits number | Recurring interval in days. Mandatory when RecurringIndicator = 1.
| |||||
RecurringMaxDate | No/Yes | Date in string representation DD.MM.YYYY | Finish date of recurring payments. Mandatory when RecurringIndicator = 1
| |||||
CustomerNumber | No | 32 symbols | Merchant's internal customer identification
| |||||
SaveCard | No | 1 - the card is stored to this customer number; | 0 | This parameter permits to store the card to this client number for subsequent payments, if the current payment is successful. If this card for this client number already has been saved before, the parameter is ignored. | ||||
| 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.
| ||||
| Type | No | cardpayment - customer pays by card; | cardpayment | Type of payment chosen by the customer when paying for the order (by card or via Faster Payments System). | ||||
| Account | No | 30 symbols | Recipient ID (paid phone number) |
...
- Check the version of the 3D-Secure protocol in response to an authorization request to the Assist service. For version 1, support the workflow described above.
- For version 2, create a hidden iFrame on the payment page (for a detailed parameters description see below) and send 3DSMethod request (if available) to the issuing bank ACS.
- To continue authentication, call the ws3dsecver2 web get3dsecver2 web service with additional 3D-Secure parameters. If authentication occurs without additional interaction with the customer (Frictionless Flow), then Assist will receive its result and send the authorization transaction to the processing. The enterprise will receive in response a full payment result, which also contains the result of authorization in processing. If additional authentication of the customer is necessary, then the IPS Assist will return additional fields for verification (Challenge Flow) in response to the request.
- If there are additional fields in the response that indicate the need for additional verification, the enterprise creates an iFrame on the payment page, which implements the display of the ACS page of the issuing bank to enter a one-time password. Customer completes authentication.
- If the response contains additional fields indicating the possibility of Decoupled Authentication, the enterprise awaits the result of the verification check. Buyer authentication can be done through an alternative method supported by the issuing bank (for example, through a push notification on the phone and Face ID or fingerprint authentication in the issuing bank's app).
- IPS Assist will receive the result of the verification to the server on its side (for Challenge Flow and Decoupled Authentication). In case of successful verification, a payment transaction will be processed. If the verification fails, the operation will fail.
- To find out the final result of payment for an order, the enterprise must use one of the methods for obtaining an authorization result.
...