Most probably this error happened because either there's an error in the URL syntax or your firewall blocking the requests sent from ClickPay, in this article you will know how to test this to make sure whether it's an issue from ClickPay side or not.



Reason #1: Not a secured (HTTPS) URL



This means that your provided URL is not secured (HTTPS) (This is for the returns URL only), which in this case ClickPay send this request as a GET one, not a POST one, that's mean it will be with an empty payload.



Just please provide a URL that implies the criteria clarified in the "What is the Return URL vs the Callback URL?" solution article, and a POST request with the details will be posted to your provided endpoint.



Reason #2: The URL contains a port number



This means that your provided URL contains a port number which is for security reasons ClickPay drops any request pointed to any URL with port numbers.



Just please provide a URL that implies the criteria clarified in the "What is the Return URL vs the Callback URL?" solution article, and a POST request with the details will be posted to your provided endpoint.


Reason #3: Invalid/Unreachable provided URL



This means that your provided URL either is not valid or can not be reached from us due to your firewall (or it's not a public one). In this case, ClickPay will not be able to post you the post-payment details as normal.



Just please provide a URL that implies the criteria clarified in the "What is the Return URL vs the Callback URL?" solution article, and a POST request with the details will be posted to your provided endpoint.


Reason #4: Suspecting that this is an issue from ClickPay?



If you are suspecting that this issue is from ClickPay, here are some steps you should do first to investigate the issue whether it is from your side or ours, you will need a middle parameter to solve this question.


So consider it as an equation from 2 variables as follow



ClickPay --------------------------> Your Side



you will need a middle layer to check whether the response has been sent from ClickPay at it or not.



ClickPay ------------>(Middle Layer)-------------- Your Side



If the request reaches this layer, that's mean that the request is dropped at your side for any reason, if not that's mean the request didn't have been sent from our side at all, and in this case, you will need to contact us at (support@clickpay.sa)



To simulate this scenario, please follow the below steps:


  1. Navigate to the following site (https://webhook.site) to generate a public server that can be considered a middle layer.
  2. Copy the URL it gives you, which will be available for around 7 days, then you need to create a new one.


  3. Use this copied URL instead of yours (return/callback) in the request payload.

  4. Proceed with a test payment as usual and check your webhook.site browser tab after.
  5. You should receive a request with the same cartId you sent on the request, on your webhook.site link as shown below
  6. That's mean that ClickPay is sending the data from her side successfully, and you have to check your endpoint or your firewall.


If you don't receive any request after the payment from your side, please contact us at (support@clickpay.sa) providing us with the request payload and a screenshot from your webhook.site page, along with the country your business operated from