I have enabled 3D Secure using the SagePay control panel. Unfortunately the uCommerce SagePay service has been coded to overide my settings and never to use 3D Secure (why?). I have downloaded the original SagePay code from SagePay-3.0.zip.
This behaviour is set by line 86 in SagePayPaymentMethodService.cs:
dict.Add("Apply3DSecure","2");
All I need to do is change the 2 to 0, 2 tells SagePay never to use 3D Secure.
After reading 'Integrating uCommerce with a Payment Provider' I setup a Visual Studio Class Library project using the 4 downloaded files and added references to uCommerce.dll and uCommerce.Infrastructure.dll but I'm getting 30 error messages.
Can anyone tell me the simplest way to change this setting, my Merchant Bank has made 3D Secure compulsory and I need to sort this out ASAP. I would have thought this is something you should be able to do using the uCommerce interface or by editing a config file.
Enabling SagePay 3D Secure
I have enabled 3D Secure using the SagePay control panel. Unfortunately the uCommerce SagePay service has been coded to overide my settings and never to use 3D Secure (why?). I have downloaded the original SagePay code from SagePay-3.0.zip.
This behaviour is set by line 86 in SagePayPaymentMethodService.cs:
All I need to do is change the 2 to 0, 2 tells SagePay never to use 3D Secure.
After reading 'Integrating uCommerce with a Payment Provider' I setup a Visual Studio Class Library project using the 4 downloaded files and added references to uCommerce.dll and uCommerce.Infrastructure.dll but I'm getting 30 error messages.
Can anyone tell me the simplest way to change this setting, my Merchant Bank has made 3D Secure compulsory and I need to sort this out ASAP. I would have thought this is something you should be able to do using the uCommerce interface or by editing a config file.
Thanks.
I am using:
Umbraco v6.1.1 (Assembly version: 1.0.4902.15214)
uCommerce 6.0.2.14122
Hi Jarema,
if you write to me at
msk at ucommerce dot net
i can provide the source code for that payment provider for you to use.
Then it's a matter of configuring the paymentprovider as described in the article.
is working on a reply...