I was wondering how I would use "Vereified by Visa" and "MasterCard SecureCode" with my stores.

Has anyone used these features before? How hard is it to configure?

Thx

William-

The last time it was discussed...

http://forums.monstersmallbusiness.com/ind...showtopic=15122

basically said "not yet". Although I haven't been vocal in any of the other threads about it, I should point out a few things that were missed...

In most implementations of VBV or MCSC, the password step is placed AFTER the customer submits their order. Therefore, even if the customer can't remember their password, cancels the window - whatever... the order is still completed (albeit without the extra authentication by VBV or MCSC)... therefore, if integrated correctly, it would have ZERO effect on checkout completion...

Most merchant account providers that are supporting these authentication methods are charging extra for them ($0.05-$0.10 per transaction)... however, the actual (interchange) rates for transactions done via VBV or MCSC are lower, so your processing costs could go down (along with enhanced protection against chargebacks.)

I'd love to see implement this - but it's a big project to do (as the integration requires quite a bit of coding)... so don't expect a miracle any time soon.

Thanks for the fast Response, maybe we can get something I have read a ton of great things about this product from Visa and MasterCard but have not seen really anyone using it other than big stores.

I'm sure all of us would love to have this feature. A credit card company can issue a chargeback to online merchants "card not present" transactions unless they show a MO/TO code such as 5 or 6 in their system meaning the merchant is a VBV or MCSC participant, in which case they have no chargeback rights whatsoever for "fraud mail/phone order" or "cardholder does not recognize transaction" reason codes. The great thing about this is that cardholders that are non-participants of VBV and/or MCSC can still place orders on the website and we as merchants would still have no fraud liability. It shifts the liability back to the bank, who has to either eat the loss or do additional investigating to make sure their cardmember isn't just forgetting they ordered something or doesn't recognize the name of the store because they let their kid use their credit card and now doesn't know where the $300 charge from XYZ.Com on their statement came from.


When I was working for a major credit card company there were lots of big stores such as Tiger Direct, Wal-Mart, Nordstrom.com or 1-800-Flowers.com that we could not touch with chargebacks and obviously they have such a large volume that there's no way every customer of theirs is a VBV or MCSC participant that has a password. They would lose a ton of business if it was a requirement. I know my gateway supports VBV and MCSC but I believe Commerce has to also support it so it looks like we just got to wait until they throw us a bone.

Yes - I did forget to mention that in my post... whether the customer has set a password previously or not, ALL transactions are covered. So, while most customers would never even see the VBV and MCSC window, you'd gain protection from quite a few chargebacks on all sales.