AbleCommerce Shopping Cart Software

Hi

Does anybody know if the implementation of the Protx gateway included in release 7.1 included support for 3D Secure transactions? I ask because I was under the impression that support was there, but can find no way to inidcate that a specific card type needs to check for enrolment in 3d secure, and when we tried the implementation against a test protx account with 3d enable on it, we got strange behaviour.

By strange, I mean scary: Able reported the transaction as complete and allowed the purchase (in this case a download) to proceed, but the transaction was not registered with protx i.e. free downloads for all

Many thanks

Tony

3D Secure is not supported by the Protx implementation in 7.1.
This is because of the way 3D secure works. It can not be incorporated in normal transaction sequence of payment gateway API.

As far as the transaction reported complete, please check your gateway settings in AC as well as in Protx server. Also if a transaction has been reported completed in AC there will be some reference information available in the transaction. Have a look at what the corresponding transactions in AC say.

sohaib wrote:3D Secure is not supported by the Protx implementation in 7.1.
This is because of the way 3D secure works. It can not be incorporated in normal transaction sequence of payment gateway API.

This is a pretty incredible answer - are you really saying "it doesn't work the way we want it to so we'll just ignore it"? I think you are going to have to change your views somewhat. 3D secure IS a pain no question, but you will have to implement it soon as it is not just a European thing - you guys in the States will get it soon. And believe me, having implemented 3d secure several times, it can be done. You only need to look at the tens of thousands of sites that implement it correctly so see that.

Protx have a very good SDK which includes a .NET/C# ASP.NEt implementatiuon of 3d secure. I offered you guys my own code which implements 3d secure for Protx when I knew you were building the Protx gateway. Yet you've decided you can't do it so the rest of the world is wrong. Wow.

I really feel stunned by this answer.

A product life-cycle is different from custom development. Implementing new features is rarely a challenge. Maintaining backward and forward compatibility is a bigger concern. When you have thousands of existing customers out there you have to be careful incorporating changes that can potentially cause upgrade issues. Customer specific requirements can always be met by custom implementations.
AC has a standardized framework for payment gateways. It needs to extend it to incorporate 3D secure authentication as well but it can not just base the framework on one particular gateway's 3D secure authentication process. It has to look at other gateways and standardize the process.
Just because Protx supports 3D secure does not mean the default implementation in AC7 will have the support. In the default implementation, (that will get shipped to hundreds of customers) we commit to a code that we can later on support in the future upgrades. A user can always have his custom implementation the does not have any future liabilities.