Developer forum

Forum » Ecommerce - Standard features » Delayed checkout responses do not complete the order

Delayed checkout responses do not complete the order

Peter Leleulya
Reply

I have a question about order handling.

We use the Ogone (Ingenico Payment Provider) checkouthandler.
In some cases we see a transaction status 9 (succesful payment) with an order in dynamicweb ecommerce, while the order itself is not completed.

When I look at the logging for that order in dynamicweb I can assume the user closed the browser after finishing his payment, because there is no log entry like (I removed the actual values):
Order Redirecting to https://{mydomain}/Default.aspx?ID={id}&CompletedOrderId={orderid}&CompletedOrderSecret={secret}

In the payment provider logging I see a succesful after sales post to the checkout handler (I removed the actual values):
OFFLINE POSTSALE: url=https://{mydomain}/Admin/Public/Gateways/CheckoutHandler/Ogone/OgoneFormCallBack.aspx/ parameters = orderID={orderid}&currency=EUR&amount={amount}&PM=iDEAL&ACCEPTANCE={acceptance}&STATUS=9&CARDNO={cardno}&ED=&CN={name}&TRXDATE={date}&PAYID={payid}&PAYIDSUB=0&NCERROR=0&BRAND=iDEAL&IP={ip}&SHASIGN={sha}/ method = POS

It is my assumption that when an after sale post, even when it is hours later and the customer is no longer on the website, is done the checkouthandler interprets the post and in case of a succesful payment (in our case: status 9) completes the order and triggers the checkoutdoneorderiscompleteobserver ?!?!

Because it looks like the order transaction status has been updated to the value 9, but the order has not been completed and the observer was never triggered.
Therefore functionality triggered by the observer was never fired.

Is there a flaw in our way of implementing?
Turning on extensive ecom logging is not an option I'm afraid, it seems to freeze the entire application ...

This is a problem which is ongoing since the website launch at the beginning of this month and is a big problem for our customer.
Any help will be very appreciated!!


Replies

 
Peter Leleulya
Reply

This issue can be removed/ignored.
Seemed to be a combination of configuration in the payment provider environment and bad coding (code was depending on non-existing content)

 

You must be logged in to post in the forum