Direct Integration

In this method, an online store has its own payment page to collect card data natively through its web site.

Steps

1. A customer selects a product in the online store, and then clicksBuy.
2. The online store server receives a purchase request and opens a payment page.
3. The customer enters their card details on the online store payment page.
4. The online store server collects the card data.
5. Initiate payment. The online store server requests an order registration and initiates payment by sending theinstantPayment.doAPI call to the payment gateway. This request must contain theamountparameter (the payment amount in minor currency units) and thebackUrlparameter (the address to which the user will be redirected if the payment is successful inStep 10). It also passes the card data to the payment gateway.
6. If 3-D Secure is required (theacsUrlparameter is returned inStep 5), the payment gateway communicates with the Directory Server to reach the ACS. It returns all the data necessary for the ACS redirect to the online store. If 3-D Secure is not used, theSteps 7-9are omitted and the customer is redirected to the payment confirmation page (Step 10). Theredirectparameter is ignored in this case as the online store uses its own payment confirmation page.
7. The online store server requests simplified customer redirect to the ACS by sending theacsRedirect.doAPI call to the payment gateway. TheorderIdparameter (received inStep 5) is used in the request.

It is also possible to redirect a customer to ACS with a POST request (regular redirect). The description of this method can be foundhere.

1. The payment gateway redirects the customer to the ACS.
2. The cardholder confirms the order and the ACS redirects him or her to the payment gateway.
3. The customer returns to the online store page (to the URL specified during the order registration inStep 5) or closes the page.
4. The payment gateway sends an asynchronouscallback notificationto the online store server (if callback notifications are enabled).
5. (Optional) The online store sends thegetOrderStatusExtended.dorequest to the payment gateway to check the order status and make sure the order is really paid. The request contains theorderIdparameter received inStep 5. In response, the payment gateway returns the order status in theorderStatusparameter. Status2means a successful payment, status1means a successful pre-authorization fortwo-phase payments(the amount needs to be captured in this case). Additionally, theactionCodeparameter is returned - it contains the response code from the processing bank.