Hi there, I've created support in BV Commerce for the Beanstream gateway (Beanstream is a Canadian gateway). The thing that I wasn't too certain about is, how to properly integrate into the BV Commerce system.

I wound up searching all of the code for an existing gateway supported in Beanstream. I then created my credit card gateway class, compiled into a DLL and deployed to the $/bin/ directory. I found that all gateways are registered in $/App_Code/TaskLoader.vb. So I added support for mine in $/App_Code/TaskLoader.Custom.vb, and then I copied my Edit form to $/BVModules/CreditCardGateways/Beanstream/*.

All in all, it seems to be working for payments, returns, and voids.

Was this the best practice / most efficient process within the BV Commerce system that I followed? Or is there some sort of pluggable design that I should be using to bundle my gateways? If anyone has bundled stuff like this for others in the past to deploy into their shopping solutions, are there tips you have to make the process easier for those users to deploy your modules into the BV Commerce product?

Some CMS' have a pluggable architecture that makes it easy to distribute new functionality. Some take the approach of uploading new modules of functionality through their CMS administration tool, such as Joomla or DNN. I wasn't sure if I had missed anything like that.

Thanks
Shan

You're on the right track. Distribute DLL and your editor controls. There is no other bundle or plugin model to distribute for BV 5.