Never used it. I wont use any commerce type plugin for a CMS short of a bridge to a tried and tested commerce application. This is just a no brainer. A site is dealing with information related to others finances. Want end up buried or perhaps even behind bars when an entity such as Chase files suit or American Express on behalf of they and their customers?

Its just a plain no brainer. Just because a plugin or component or widget add's some really cool capabilities to a general purpose content management system does not mean that it should be used towards that purpose.

Before we dumped most Joomla work we'd been asked many times to add commerce into sites developed for others. We wont do it. They want do it. Go ahead. The liability is just WAY to dangerous at least here in the USA. Of course, it does depend on WHAT is exposed. But even at that litigating as a small business against these sized entities is brutal. I went rounds with Amex once (this when I'd worked with Haggle Online) and I pray it never happens again. They are absolutely METICULOUS at hammering away (their legal beagles) and will hit from any and/or all angles they can hammer from. For example, "Are you a programmer?" Yes. "Then is it not your job when protecting our clients information to ensure the security of their information". Yes. "Did you do that?". "We used a third party plugin for the commerce". "And where is that third parties representation in this proceeding?" "They have a disclaimer of usage in respect to any damages caused or losses due to their plugin". "And you were aware of this?" Yes. "So this firm will not ensure usage of their plugin in any respect from function to security but you felt it safe to use? Why?"

Or from the other end, "Are you a programmer". "No sir, I am a site developer." "What is the differentiation". "I create artwork and setup websites for clients using pre-existing software". "Are you an Internet security expert?" "No" "Yet you feel you are qualified to create public facing commerce sites for clients who are trusting that your work keeps their business and customers information secure?" "Ummm.... Well they signed off on our disclaimer of liability". "Your disclaimer does not void you of responsibility to us, a banking institution or our customers. We signed no such agreements. Your disclaimer is between you and your client. Not the forward facing public that had no indication that this website was constructed by someone who has no knowledge of Internet Security nor even how the software itself operates internally. Already in admittance to this court that you are in fact not qualified in any way shape or form to ensure the security of the forward facing public or banks involved in their finances".

This is just a NO BRAINER. Dont do it.

If you MUST setup eCommerce for a client use something that is WHAT IT DOES. Prestashop, Magento etc. If you need bridge them, bridge them and make sure in writing by an IT counselor that your disclaimers are sound as eCommerce is DIFFERENT than "Heres a blog".