Closed blanioo closed 3 years ago
Hi @blanioo ,
the actual behavior you described is caused of the fact that we redirect to the ideal page and at this moment we had to persist the order. When there is occurring any problem (i.e. because the customer clicks on the back button), we cancel the order. When the customer decides to check out again, we also persist a new order, and to prevent gaps in the ordernumber-range we do not delete the 'old' attempt. That behavior was an explicit requirement from many customers, to have the chance to comprehend what happened there.
Hopefully that helps you.
Greetings from Kiel Timo
Hi @T-Kuchel ,
Thanks for explanation, but I think I found one thing about this functionality - when use "back" button and after this "forward" it results that cancelled order and second pending/processing has the same TXID
Steps to reproduce:
In comparison to reproduction path from my first message where TXID are different for both cancelled and success order, in above reproduction path TXID are the same for both orders, is this correct behaviour in both cases?
Related to this issue I am also experiencing strange behaviour with Ideal Payments. I also get 2 Orders, which appears to be the expected behaviour as I read in the first answer.
But the Reference, that is passed by Payone, contains the first (canceled) Order-ID. This leads to issues in matching payments to orders. Since we have an approved Order without a Payment reference, but a payed order which has been canceled.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hi all, browser-button usage during redirect payments can be really tricky due to the magento internals @T-Kuchel outlined above. When a customer uses the back button during a redirect checkout, the initial order is canceled and a new, identical one is created. When the customer then uses the forward-button again, he or she actually uses the same iDeal session for the checkout, which is why there is no new txid and therefore no new reference for the txid.
We try to make this as transparent as possible in our order table in magento:
We tried to make the checkout as seamless as possible for the customers here but have to work around some of the inner workings of magento.
So all in all yes, the behavior you reported is expected, but not very pretty. We're open for suggestions though, so if you want to provide more feedback or want to talk through alternatives, feel free to open a new issue. I'm closing this since it's already stale.
Steps to reproduce:
Actual:
Expected: