Discover essential steps to effectively manage timeout responses encountered during transaction creation and confirmation, ensuring smooth processing and minimizing disruptions in your API transactions.
Table of Contents
Encountering a timeout response during the creation or confirmation of transactions can pose challenges and disrupt the seamless flow of operations. Timeout errors can occur due to various reasons, such as network connectivity issues or system overload. However, there are steps you can take to effectively handle timeout transactions and ensure a smooth process.
To begin, check the status of the transaction by hitting the "Get Transaction by Reference ID" endpoint. If the state is "created," it indicates that the transaction has already been created in our system. In this case, reconfirm the transaction by hitting the “Confirm Transaction” endpoint, or clicking the Submit Transaction button in Jack Portal, to resume the process.
On the other hand, if the state is “submitted”, "confirmed," "completed," or "declined," it indicates that the transaction has already been processed by our system. In such cases, there is no need to reconfirm. Instead, update the transaction state in your system to reflect the outcome accurately. This step ensures synchronization between your system and ours, preventing any inconsistencies or discrepancies.
Related Articles
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article