Thread: Question about Protx 3D Secure Appearing

Looking at our failed transactions we often (90% of the time) see

C#/VB.NET Code:

StatusDetail=2007 : Please redirect your customer to the ACSURL, passing the MD and PaReq. 


This always happens with MC (Mastercard) or VISA (sometimes). This seems to be an issue with 3D Secure (They always pass the 3D Secure) and carrying on with the payment.

Is this a known ASPDOTNETSF issue? It does not seem normal for such a large number of people to revive this error on a daily bases.

Does anyone else get this issue?

Thanks in advance.

It's not something we've seen, no. If you check your failed transaction logs, what is the ACS url that is used when trying to send the transaction over?

MasterCard

C#/VB.NET Code:

ACSURL=https://www.securesuite.co.uk/santander/tdsecure/opt_in_dispatcher.jsp?partner=santander.visa&VAA=B 


and VISA

C#/VB.NET Code:

ACSURL=https://secure.barclaycard.co.uk/barclays/tdsecure/pa.jsp?partner=business.visa&VAA=B 


Also we always see this

C#/VB.NET Code:

VPSProtocol=2.22
Status=3DAUTH
StatusDetail=2007 : Please redirect your customer to the ACSURL, passing the MD and PaReq.
3DSecureStatus=OK 


3D Secure always OK.

Has this issue been resolved? I have another user currently facing this issue in 8.0.1.2

This was never solved. For some reason when the customer moves to 3D Secure it shows up as a failed transaction, this means we get a silly amount of false positives when it comes to true failed transactions.

It did not get in the way but is extremely annoying. We are still facing this problem on our 8.0.1.2 site and I am pretty sure 9.1 will have it too as the Protx (SagePayUK) code seems pretty much the same.

ASPDNSF creates payment request and sends to SagePay
SagePay validates and checks with the Bank
If the card is registered with 3DSecure a 3DAuth message is sent back to ASPDNSF Error Message Created Now
Now ASPDNSF shows the 3D Secure form
Customer enters details.
SagePay checks entered details if successful returns an 'OK' message to ASPDNSF
Order is created

This was a big issue when we tried to create a failed transaction program. In the end we had to do a check to see if the failed transaction order number was in the Orders table if so it was a false positive.