3D Secure Rejecting Payments from world pay

Hi!

We recently started using foxycart but haven't actually got through to a 'real' transaction yet.

Using SagePay we have completed our test transactions and refunds. Now we have gone live, and we recently activated the 3D Secure system. The receipt page of foxycart now says:

REJECTED 4026 :
3D-Authentication failed. This vendor's rules require a successful 3D-Authentication.

I emailed Sage Pay who at first said this meant that the 3D Secure password was being put in wrong, but they have since said:

As discussed, please check with Foxycart whether they are submitting the TermURL which is the callback page that is sent via the 3D Secure password page (ACSURL) to inform the bank how and where to send the customer back to once the customer has confirmed their password (PaRes).

The Direct protocol can be viewed via http://www.sagepay.com/help/userguides/590.

The step by step process is explained within http://www.sagepay.com/help/faq/direct_step_by_step for Direct integrations.


Foxy cart throws an error which I can view

PaRes= eNrNWNmS4kiy/ZWynkemWzugNjLNIrQDEtoX3rShXQIkJKGvvwIyq7Pr1h2rnqerNIyQE+.... [deleted about a million things here as they are probably my card details... ]
GET Values: ThisAction=3dsecure_checkout fcsid=bfqfjvcg5lo0lmj29d87kh3jm7
URL: https://garlicwoodfarm.foxycart.com/checkout.php
Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.77 Safari/535.7
Referer: https://www.securesuite.co.uk/rbs/tdsecure/pa.jsp
IP: 93.96.247.35, United Kingdom

Can anyone help me?

Thanks,
David
Comments
  • lukeluke FoxyCart Team
    Hey David, thanks for posting. We got your support email and have created a ticket to explore this issue further. We'll post back as soon as we have more information.
  • lukeluke FoxyCart Team
    You may also want to try upgrading to 0.7.2 and see if that fixes this issue.
  • Have upgraded but now the CV2 code has disappeared... how can I get it back? Thanks!
  • CV2 Number came back, and I can happily say that updating from 0.7.1 to 0.7.2 has fixed the 3D Secure issue. Thanks for your help!

    David
Sign In or Register to comment.