One of the debugging processes that we advise our customers when debugging an issue is to have you enable your plugin’s debug mode. make the transaction again and provide us the debug log as seen from our support article.
You might look through its contents and notice the following error: “cURL error 28 : Operation timed out…” as seen from the screenshot below.
What does this error mean?
When a transaction is processed, your payment provider (e.g. ePDQ, Lloyds, Authipay) needs to make a request/talk/communicate to/from the server where your website is hosted to tell them that the transaction is OK or to process the payment. However, due to some possible configurations on your server, the request to/from your payment provider may be blocked or rejected.
What are the next steps that you can take?
For the case above, the request is being possibly blocked because of the following:
- your PHP version is outdated.
- your memory server limits are not enough.
- your hosting provider may have a firewall/security that blocks the specific request.
To resolve these issues, you’ll have to reach out to your hosting provider so that they can diagnose the issue from their end and make necessary adjustments.