Based on your requirements there are 2 types of callbacks for transactions we can provide you with. To activate any of these we would require your server URL where we would post the status of a transaction.
Why is a callback required and how does it work?
There may be situations where a payment is successful but the user is not redirected back to the your website due to browser or internet connectivity issues. In this case, the customer is charged, you can set a URL to post request of successful transaction so that your servers can process the transaction in this condition.
Server to Server (S2S)
What is S2S?
- S2S are callbacks that posts real-time response to your server
- This usually works if you have problems with transactions showing up as failed. This means that the transaction is not complete. Here, the customer will see a failed transaction.
How does it work?
- S2S acts as a substitute for Status Query (Transaction Status) API implementation (for Success/Failure response); thereby reducing the turnaround for the customers.
- S2S callback does not cater to pending to success/failure cases.
How are pending/ failure cases handled?
- For pending to success/failure cases, you will need to use Status Query API
- Activating S2S callback will only give pending response in real-time to merchant’s server
- That means on your server the status will not immediately change
PEON/IPN
What is PEON/ IPN?
This allows you to see the changing status of a transaction. This feature will helps with instances of change in transaction status.
How does this work?
- Wherever a transaction shows as pending/ complete to your customer but does not show up on your server the server will be notified when the status changes to success/ failure.
- In the case of a pending transaction in our system; an auto refund will not be initiated because we do not know if the you are going to service the transaction or not
How are pending cases required to be handled?
- In such an integration, you will be required to refund manually
