Paytabs provides you with a collection of API endpoints which used to process all payments, regardless of if they are through either your own payment pages, the managed payment pages, or if you are using the hosted payment pages.
This article is dedicated to walking you through how to handle the direct payment response sent from PayTabs after the payment. Handling the response right will empower you to make sure to handle the user experience according to the payment status as well as and updating the order status in your database. It is worth mentioning that after payment, there are three types of responses you can expect:
- The response on the return page (clarified in this step)
- The callback (clarified in the next step)
- The IPN (clarified in the next step)
Below is the expected behavior of the above-mentioned responses while using the Managed Form integration type, as shown below:
To get the best out of this article, make sure you have a full understanding of the following solution articles:
Regarding the above-mentioned Managed Form workflow, there are two cases:
1. The card is 3DS supported
2. The card is NOT 3DS supported
The customer/cardholder will be redirected to the issuer 3DSecure page to authenticate the card. After the payment and ONLY if the return parameter has been set, the customer will be redirected to the return URL along with an HTTP POST response to the same URL with the brief transaction information.
To know more please check our The Return URL Response solution article.
- The return parameter MUST be set.
- The return URL MUST be HTTPS.
⌂ To get familiar with the whole process and the other steps, kindly navigate to our "The PT2 API Endpoints Integration Manual" solution article.
⇦ And to get familiar with the rest of the steps regarding the previuos step "Step 4 - Accepting the payment" kindly click here.
⇨ And to navigate to the next step in the integration process "Step 6 - Handle the post payment responses" kindly click here.