Quote:
|
Originally Posted by cflsystems
What you actually want is for XC NOT to create an order until that order has been completed - either paid for, failed, denied,...
I want that too
|
What Steve said...
Bullfrog, are you using the iFrame xpayments interface? I had nothing but problems with it and went back to "default", and although I still see some "not finished", the majority of my customers are checking out successfully. XC 4.5.4, Altered Cart CheckoutOne (NOT using x-cart checkout pages) and XP 1.0.5 (not iFrame).
The other big annoyance as bullfrog said, if a customer gets to payment, then realizes they forgot something... BUTT UGLY for the customer and error messages sent to order dept. Fail.
As Steve said. I believe this is a fundamental design defect in X-Payments -- SURELY the engineers can find a way to not send an order to the cart until after the transaction is processed (failed)?
Let's keep this discussion open?