Developer forum

Forum » Ecommerce - Standard features » DIBS - error on callback

DIBS - error on callback

Espen Strømsnes
Espen Strømsnes
Reply

The last couple of days we have some orders that have been downgraded from order to cart after DIBS payment has been done with the following error:

An error with the message 'Called State ok, but order is not set complete - this should have happened in the callback.' occurred. See the error log for details. (OrderID:ORDER10141 Total:599, orderline total:NOK 599,00; Orderlines:1 - Products:1, Discounts:0, Taxes:0, BOM:0.)

In the DIBS admin interface the payment looks ok, and according to the end-user he was redirected back to the webshop when he was done at the DIBS page. He said that he was redirected back to the cart page.This seems reasonable since the order has been downgraded to a cart in the process (due to the error).

Why is this happening, and what can we do to avoid this?

DW version: 8.8.1.18

 

Regards,

Espen


Replies

 
Nicolai Pedersen
Reply

Hi Espen

Hard to tell what happens. You could take a look at the log files in files/System/log/ecom.

Also note that a solution this old, could run into problems with TLS 1.0 and 1.1 which is currently being deprecated by the payment gateways. So if you do not upgrade, callbacks could go back to a TLS 1.0 protocol which DIBS may not support anymore.

So what does the DIBS admin interface says about the callbacks?

BR Nicolai

 
Espen Strømsnes
Espen Strømsnes
Reply

The logs do not reveal anything more details than the error I posted.

See attached screenshot from 2 DIBS payments. ORDER10141 is the one that failed, ORDER10168 is ok. The callback has finished and the order is marked as OrderComplete. 

Regarding TLS, could this fallback happen to just some of the transactions?  The interesting part is that some of the payment callback succeeded, some didn't.

Espen

 

 

 

dibs.png
 
Kristian Kirkholt Dynamicweb Employee
Kristian Kirkholt
Reply

Hi Espen

Could you post this to Dynamicweb Support. (Support@dynamicweb.dk)  

Anyway I think that this problem is resolved in a later version

Kind Regards
Dynamicweb Support
Kristian Kirkholt

 

You must be logged in to post in the forum