mrsl
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] 3D AUTHHi,
The direct issue is unrelated to the 3D AUTH issue. It is about something else.
So will setting force secure to true fix this issue?
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] 3D AUTHI have also notice that the force secure checkout option is not ticked. Is this needed for SagePay?
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] 3D AUTHHi,
I am unaware of whether this worked previously as I have just taken over the site.
In the TEST environment I get the following debug email info:
Payment Gateway URL: https://test.sagepay.com/gateway/service/vspdirect-register.vsp
3D Secure Callback URL: https://test.sagepay.com/gateway/service/direct3dcallback.vsp
Payment Gateway Response:Array
(
[VendorTxCode] => d****************8
[Created] => 2014-02-12 12:28:16
[VPSProtocol] => 2.23
[Status] => NOTAUTHED
[StatusDetail] => 2000 : The Authorisation was Declined by the bank.
[VPSTxId] => {A************9}
[SecurityKey] => **********
[AVSCV2] => DATA NOT CHECKED
[AddressResult] => NOTPROVIDED
[PostCodeResult] => NOTPROVIDED
[CV2Result] => NOTPROVIDED
[3DSecureStatus] => NOTCHECKED
[result] => notauthed
)I have starred out the ids. Let me know if they are needed.
However, when i test it on LIVE, the transaction goes through as I stated in my original post, and the status detail in WooCommerce is stuck on Contacting bank for authorization. (Code: 2007 )
We have also spoken to SagePay and they have said that we need to ensure we are directing the customer to the acs url and are submitting md and pareq. They also said we should be using form integration rather than direct integration.