Closed (duplicate)
Project:
Drupal Commerce 3D Secure Support
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
17 Oct 2011 at 14:13 UTC
Updated:
11 Jul 2012 at 20:46 UTC
Comments
Comment #1
kingandyLooks like the order status is what's at fault - the module needs to update the order status to the next stage of the Checkout, or Commerce will simply redirect the browser from checkout/%/complete to checkout/%/[current_state]...
Comment #2
kingandyLooking at the module, it seems that it will move the order onto the next step if it doesn't find an "extra_authorisation" element in the order's data array. I can't find anywhere in the code that this gets unset, and nowhere that otherwise updates the cart status.
I have however noticed that the sagepay_direct module includes a "3D Secure Callback" (commerce_sagepay_direct/3d_secure_callback/%). If this is intended to be called by the remote server, this could be the root of my problem - our server is not yet live to the internet. On the other hand, as I say, I can't see anything in that callback that explicitly moves the order away from the checkout_3d_secure state.
I'm going to mark this as "postponed" until the domain goes live and we have the chance to test properly.
Comment #3
kingandyComment #4
craigbailey commentedI'm having the same issue on a live system. I've debugged the module the best I can and can't seem to find a solution. It seems like it gets to commerce_3d_secure_clear_iframe fine, but on the redirect it just doesn't work and brings the iframe back up.
It's also worth nothing that the payment appears in SagePay, so it seems like they are authorizing fine. It just doesn't redirect to the correct pages after. It also does not create the order in Drupal Commerce.
Can we re-open this issue? It's vital for the e-commerce store I'm working on which is why I'm spending so much time trying to resolve it. I've tried it on a couple of sites now with the same result each time.
Comment #5
kevster commentedLooks like we have the same problem - any card that needs to go through 3D secure the order status gets stuck on checkout > 3D secure authentication. The order does go through sagepay correctly and the customer gets charged but they dont get moved on from the 3D secure screen.
Not sure if a rule is needed to move them on to the next status? Ive switched this off for now...
Happy to test this once its been updated..
Thx - Kevin
Comment #6
ikos commentedThanks Kevin,
I am going to set up a test system this week and see if I can move this and the Direct module to a stable release.
kind regards
Richard
Comment #7
axel pressbutton commentedHi Richard,
We're also having the same issue where any test card (Netbanx) that requires 3D Secure authentication repeatedly returns the 3D Secure form on submission.
The order status is changed to "Checkout: 3D Secure Authentication" and the basket emptied.
Comment #8
kevster commentedHi Richard - that would be great, let me know if you need any testing done, we can put some live testing through.
Thx - Kevin
Comment #9
ikos commentedHi,
I finally found some time to dig into this issue and have located the route cause is in the SagePay Direct implementation of the call back not this module.
I will cross post the issue to the queue over there and mark this as a duplicate.
See: http://drupal.org/node/1679828