When I create a purchaseorder in my developer environment and pass it to my payment provider, then I have the order status 1 (basket) when I receive the callback from the payment provider (DIBS)
When I do the same on our webserver, then I have order status 2 (new order) when I receive the callback from (DIBS)
Just to be sure. Are you 100% sure that DIBS can reach your development machine? When a callback comes from DIBS it turns the basket into a PurchaseOrder. So to me it sounds like DIBS is not reaching your development machine.
If DIBS can't reach your development machine with callback it still send the customer to a receipt page because DIBS uses a retry strategy.
Now I understand - the status is supposed to be changed when returned from DIBS? I thought that I was supposed to change the order status on the callback and therefore, I wrongfully took the development environment as the correct approach.
You're welcome. When the user is redirected back to the receipt page uCommerce by default doesn't change the basket to a purchase order.
When you authorizing the payment at DIBS it behind the scene calls a handler in uCommerce and when the callback is succeed the customer is redirected to the receipt page.
Though I know in newer versions of the DIBS API it does the callback async but I don't think it has been implemented yet.
Order status difference
Hi
I have a strange problem.
When I create a purchaseorder in my developer environment and pass it to my payment provider, then I have the order status 1 (basket) when I receive the callback from the payment provider (DIBS)
When I do the same on our webserver, then I have order status 2 (new order) when I receive the callback from (DIBS)
This is how I retrieve the purchase order:
PurchaseOrder purchaseOrder = PurchaseOrder.All().FirstOrDefault(x => x.OrderGuid.ToString() == OrderGuid);
If I use a custom payment method on the webserver, then the order status is 1 (basket) as expected.
It is the same code, config files and database - does anybody have a clue ???
I am running Umbraco 7.1.8 and uCommerce 6.4.4.14301
Hi René,
Just to be sure. Are you 100% sure that DIBS can reach your development machine? When a callback comes from DIBS it turns the basket into a PurchaseOrder. So to me it sounds like DIBS is not reaching your development machine.
If DIBS can't reach your development machine with callback it still send the customer to a receipt page because DIBS uses a retry strategy.
Best regards Martin
Hi Martin
Now I understand - the status is supposed to be changed when returned from DIBS? I thought that I was supposed to change the order status on the callback and therefore, I wrongfully took the development environment as the correct approach.
Thank you for the explanation
Best regards
René
Hi Rene,
You're welcome. When the user is redirected back to the receipt page uCommerce by default doesn't change the basket to a purchase order.
When you authorizing the payment at DIBS it behind the scene calls a handler in uCommerce and when the callback is succeed the customer is redirected to the receipt page.
Though I know in newer versions of the DIBS API it does the callback async but I don't think it has been implemented yet.
Best regards
Martin
EDIT: You can read more about the payment flow here': http://docs.ucommerce.net/ucommerce/v6.6/payment-providers/integrating-hosted-payment-pages.html
is working on a reply...