NETS payments - confirmation issue

Hi,

we are using NETS/DIBS Easy payments in DW 9 and it works well most of the time when user follows regular journey.
But from time to time we have orders stuck in Draft in DW but they are completed in NETS.

It looks like user is not redirected back to DW or they are not waiting for the redirect to happen.
Our expectation is that in cases like this we should rely on NETS webhooks - is that correct assumption?

This is example logs:

11 Jun 2025 20:55:58

Order After StartCheckout. Order price: 3635; IsProcessingCheckout: True (IsCart:True, UserID/name/secondaryid:0//0, Complete:False), (IP:xxx, Url:/Default.aspx?ID=1844), Thread:231, HashCode:30956283)

12 Jun 2025 19:43:04

Order Cart has an orderID or IsCart=false: ORDER3032 and is being reloaded 6724 (IsCart:True, UserID/name/secondaryid:0//0, Complete:False), (IP:xxx, Url:/Default.aspx?ID=1840), Thread:40, HashCode:63939012)

So looks like we are missing Order RedirectToCheckoutHandler callback started...

NETS has convirmed that webhooks were triggered
How we should proceed with investigation?

Hi Dawid

Which version of DW9 are you using?

If you do not see the callback started message, the request from Nets to Dynamicweb probably never hits the DW application. We need to find out why. Can be all kind of things on the network path.

In the NETS portal you can usually view a history of webhook deliveries – look for HTTP status codes other than 200 OK or any error messages. You might need to get that information from NETS as their admin historically did not carry that information - but they have it. It would be great to see that the webhook to the callback was made, what the response code was and what was in the response body of that callback. That could give an indication on what could be wrong.

BR Nicolai

Developer forum

NETS payments - confirmation issue

Replies