Page History
...
The processes of bankcard authorization (payment operation) and financial transaction (financial confirmation) in the double-stage operation mode are split.
| Note |
|---|
If you want to use the double-stage payment mechanism, you should first consult with the support service staff (support@assist.ru). |
Bankcard payment operation
...
Internet-shop can issue a financial confirmation within 4 days in Personal account, or using Web service.
To confirm the payment, send a request to IPS Assist server via HTTP POST or SOAP method (in UTF-8 coding).
...
Parameter | Mandatory field | Adopted values | Default values | Description |
Billnumber | Yes | 15 or 16 digits, extended payment number | Unique number of payment corresponding to the order number in IPS Assist; extended payment number can be passed | |
Merchant_ID | Yes | Number | The enterprise identifier in IPS Assist | |
Login | Yes | 20 characters | Login (Latin letters, digits and symbol _) | |
Password | Yes | 30 characters | Password (Latin letters and digits) | |
Amount | No*Number | 15 digits, two digits after the delimiter (delimiter '.') | The amount of financial confirmation | |
Currency | No* | 3 characters | Confirmation currency code. Only the currency code of the payment operation can be used. | |
ClientIP | No | IP-address of the operator's computer that confirms the payment | ||
Language | No | RU – Russian | RU | Language of the results output |
Format | No | 1 – CSV (delimited fields) | 1 | Format of the results output |
* The parameters Amount and Currency can be passed or missed in the request only simultaneously. If the above parameters are missing, the full amount confirmation operation will be performed.
| Note |
|---|
All request parameters are automatically validated. The validation rules are given in table "The validation rules for input parameters". |
The confirmation can be performed to both the complete amount and a part of the amount. It is allowed to issue a partial confirmation of amount not exceeding the amount of payment, if the payment operation by bankcard was completed through processing with correspondent settings.
Please, note that confirmation amount should be provided (using both Personal account and Web service) in the same currency which was used in the payment operation (normally, in Roubles).
The parameter billnumber can be passed either in ordinary format (when there was only one successful payment on this order) or in extended format in the confirmation. While using the extended format it is required to provide the exact number of the successful authorization operation (in some cases it can be not a first operation in the order, 500000000000001.2 for example).
. Format of the results output. 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. | |||||||||
| AutoDeposit | No | 1 – flag on 0 – flag off | Online deposit flag. It is used in cases when it is necessary to immediately unblock the unconfirmed part of the order amount.
|
* The parameters Amount and Currency can be passed or missed in the request only simultaneously. If the above parameters are missing, the full amount confirmation operation will be performed.
| Note |
|---|
All request parameters are automatically validated. The validation rules are given in table "The validation rules for input parameters". |
The confirmation can be performed to both the complete amount and a part of the amount. It is allowed to issue a partial confirmation of amount not exceeding the amount of payment, if the payment operation by bankcard was completed through processing with correspondent settings.
Please, note that confirmation amount should be provided (using both Personal account and Web service) in the same currency which was used in the payment operation (normally, in Roubles).
The parameter billnumber can be passed either in ordinary format (when there was only one successful payment on this order) or in extended format in the confirmation. While using the extended format it is required to provide the exact number of the successful authorization operation (in some cases it can be not a first operation in the order, 500000000000001.2 for example).
| Expand | ||
|---|---|---|
| ||
If enterprise uses double-stage operation mode together with THANK YOU Bonus | ||
| Expand | ||
| ||
If enterprise uses double-stage operation mode together with THANK YOU Bonus Program from Sberbank then payment confirmation (on order with two operations – by card and by bonus) should be performed with parameter billnumber in non-extended format (without point) and parameters amount and currency should not be provided in the request. Such request confirms the card payment only. Confirmation for bonus payment is not required (bonuses withdrawals is performed on the first stage). There is no possibility to perform partial payment confirmation on such order. |
...
If the payment has been successfully confirmed, the order in IPS Assist adopts the status Approved Approved or PartialDelayed, the Response_code is AS000.
...
Parameter | Value |
ordernumber | Order number |
responsecode | Response code |
recommendation | Recommendations |
message | Message |
ordercomment | Comment |
orderdate | Date of order |
amount | Operation amount |
currency | Currency of operation |
meantypename | Type of payment means |
meannumber | Number of payment means |
lastname | Payer's last name |
firstname | Payer's first name |
middlename | Payer's middle name |
issuebank | Name of issue bank |
Payer's e-mail | |
bankcountry | Country of issue bank |
rate | Currency rate |
approvalcode | Authorization code |
meansubtype | Payment means subtype |
cardholder | Payment means holder |
cardexpirationdate | Card expired date |
ipaddress | Payer's IP-address |
protocolname | Protocol |
testmode | Test mode |
customermessage | Result message for a customer |
orderstate | Order state |
processingname | Processing |
operationtype | Operation type |
billnumber | Billnumber extended format |
orderamount | Original amount of operation |
ordercurrency | Original currency of operation |
slipno | Financial transaction identifier |
packetdate | Request issue date |
signatureSignature | The X value without delimiters, signed with IPS Assist private key, encoded in BASE64, where X - billnumber,ordernumber,responsecode,orderamount,ordercurrency,meannumber,approvalcode,orderstate,packetdate |
Examples
Request example for HTTP POST format:
...
If the payment is successfully confirmed, the field "orderstate" will contain the value "Approved" or PartialDelayed, the confirmation operation response_code is AS000. If the payment confirmation is not confirmed, the response_code will adopt the values AS100- AS998.
The field <slipno> is used only for processings: UCS, Raiffeisenbank, Multicard and Russian Standard. The values of this parameter in result requests are described in the table "Values of <slipno> parameter". If payment confirmation will not be sent (charge service was not called), the financial transaction is not sent to the processing and such transaction will not appear in the processing report for enterprise.An example of a result request in XML format which returned an error (wrong password):called), the financial transaction is not sent to the processing and such transaction will not appear in the processing report for enterprise.
An example of a result request in XML format which returned an error (wrong password):
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<!DOCTYPE result (View Source for full doctype...)>
<result firstcode="7" secondcode="102" count="0"></result> |
For description of the first and second codes of the automated interfaces refer to table "Error codes".
In SOAP format:
| Code Block | ||
|---|---|---|
| ||
<?xml version='1.0' encoding='utf-8' standalone='no'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/' SOAP-ENV:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
<SOAP-ENV:Body SOAP-ENV:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'>
<ASS-NS:MakeChargeResponse xmlns:ASS-NS='http://www.paysecure.ru/message/'>
<return xmlns:si='http://www.paysecure.ru/type/' xsi:type='si:SOAPStruct'>
<ordernumber xsi:type='xsd:string'>0001-01</ordernumber>
<responsecode xsi:type='xsd:string'>AS000</responsecode>
<recommendation xsi:type='xsd:string'></recommendation>
<message xsi:type='xsd:string'>Completed.</message>
<ordercomment xsi:type='xsd:string'>test payment</ordercomment>
<orderdate xsi:type='xsd:string'>01.01.2011 11:23:13</orderdate>
<amount xsi:type='xsd:string'>100.00</amount>
<currency xsi:type='xsd:string'>RUB</currency>
<meantypename xsi:type='xsd:string'>VISA</meantypename>
<meannumber xsi:type='xsd:string'>411111****1111</meannumber>
<lastname xsi:type='xsd:string'>Testov</lastname>
<firstname xsi:type='xsd:string'>Test</firstname>
<middlename xsi:type='xsd:string'>Testovich</middlename>
<issuebank xsi:type='xsd:string'>New Bank</issuebank>
<email xsi:type='xsd:string'>test@testpost.ru</email>
<bankcountry xsi:type='xsd:string'>Russia</bankcountry>
<rate xsi:type='xsd:string'>1</rate>
<approvalcode xsi:type='xsd:string'></approvalcode>
<meansubtype xsi:type='xsd:string'>Classic</meansubtype>
<cardholder xsi:type='xsd:string'>TEST</cardholder>
<cardexpirationdate xsi:type='xsd:string'>12/20</cardexpirationdate>
<ipaddress xsi:type='xsd:string'>11.23.11.23</ipaddress>
<protocoltypename xsi:type='xsd:string'></protocoltypename>
<testmode xsi:type='xsd:string'>1</testmode>
<customermessage xsi:type='xsd:string'>Completed.</customermessage>
<orderstate xsi:type='xsd:string'>Approved</orderstate>
<processingname xsi:type='xsd:string'>Name</processingname>
<operationtype xsi:type='xsd:string'>200</operationtype>
<billnumber xsi:type='xsd:string'>511111100000001.2</billnumber>
<orderamount xsi:type='xsd:string'>100.00</orderamount>
<ordercurrency xsi:type='xsd:string'>RUB</ordercurrency>
<slipno xsi:type='xsd:string'>111111</slipno>
<packetdate xsi:type='xsd:string'>01.01.2011 11:28:26</packetdate>
<signature xsi:type='xsd:string'></signature>
</return>
</ASS-NS:MakeChargeResponse></SOAP-ENV:Body> </SOAP-ENV:Envelope> |
| Warning | ||
|---|---|---|
| ||
The following root certificates have to be installed on the requester side in the Trusted Root Certification Authorities Store for correct work with WEB-services via secure communication over TLS:
Before to start, check the presence of these certificates in the trust store and add tit if necessary. |