ASI (Account Status Inquire) operations are used to implement initial operations such as COF or recurring payments. ASI operations require customer consent, are carried out with 3D-Secure authorization and have a zero amount.
So, using ASI operations as initial ones, it is possible to carry out a registration transaction - store a client's card without an additional verification payment.
When performing an ASI operation, the payment page will display the Account status inquiry heading, a zero payment amount, and a Continue button instead of the Pay button for the customer.
Payment page appearance for ASI operation (card linking)
Displaying a successful card linking result for the customer
Payment page appearance for ASI operation (subscription registration)
Displaying a successful subscription result to the customer
ASI operation for MIR cards with a zero amount is not performed. A corresponding warning is displayed on the payment page. After entering the MIR card number on the payment page, the order amount (ASI operation) will be changed to 1 BYN, and after the verification procedure is completed, such an order will be automatically canceled.
Payment page appearance for ASI operation (MIR card linking)
Displaying a successful MIR card linking result for the customer
By using MIR cards, web service responses will display two operations totaling 1BYN: one payment operations and one cancellation operations.
Implementation
The ASI operation can be implemented by making a request to the URL of one of the services:
- https://<SERVER-NAME>/pay/order.cfm;
- https://<SERVER-NAME>/pay/silentpay.cfm;
- https://<SERVER_NAME>/pay/payrequest.cfm
with the transfer of parameters corresponding to the linking payment for recurring payments or CIT/MIT COF payments, and also specify the payment amount OrderAmount = 0 and mandatory for ASI operations additional parameter BlockOrderType = 2.
To start use the ASI operations, please send a corresponding request to the customer service department at support@belassist.by.