Skip to main content

Callback Troubleshooting

Declined Response​

Open your callback page and check your code carefully. Ensure that every variable is collected from the POST and that it is then passed to the Nochex server through a query to "https://secure.nochex.com/callback/callback.aspx"

Using PHP, the easiest way to get the post variables and then turn them into a query ready to be sent to the Nochex server is: $postvars = http_build_query($_POST);

For more instructions and examples see our guide.

Also you can download some Callback examples to help you, and come in different programming languages:

No Message Received​

Firstly make sure you have put the correct URL into the callback URL field either on the Payments Page Setup or through a post to Nochex.

Make sure you have Callback enabled by contacting us.

  • Check your code carefully to ensure the right email address / merchant ID is being used.
  • Check your firewall settings aren't blocking the HTTP POST messages from Nochex.
  • Create a mail function that emails you soon as the code should have been called, that way you can see if the code is being called then you know that there is something in your code that needs changing.

Order details not coming through​

If your order details have not come through and this only happens intermittently we have now added functionality that resets Callback to get the details sent through. Just follow the instructions below to reset Callback in turn sending the order details through:

  • Login to your Nochex account
  • At the control panel click Transaction History
  • Click on the symbol under the Callback column for a particular transaction to show a popup
  • You will see more information on the transaction, and press the Reset Callback button
  • The status should turn from ongoing to passed when APC has been resent, Note: this may take a couple of minutes
  • You should now get the order details showing for that transaction

Still having issues with your callback?​

Please raise a support ticket containing details of the problem, error messages / logs, and print screens (If applicable).