If you wish to minimize your chargeback rate, if you wish to be able to fight chargebacks received, if you have a real interest in fighting fraud, if you want to minimize fraud costs and wish to see an improvement in your bottom line – it’s time you add VBV & MC SecureCode to your processing workflow…

Sounds like you forgot to report the CAVV.

For the rest of our readers:

CAVV = Cardholder Authentication Verification Value
ECI = Electronic Commerce Indicator
MPI = Merchant Plug-In

When implementing an MPI, the ECI and CAVV results must be captured and submitted with the transaction to the acquirer, for the merchant to benefit from VBV chargeback protection.

As funny as it may sound, we have implemented a VBV solution and were processing cards which were “Verified by Visa” (ECI=5).

We kept getting chargebacks and as we are not supposed to, we resubmitted those, yet resubmission was declined!

When we further investigated the issue, it turned out we failed to report the VBV and ECI result to our acquirer, and the transactions were processed without a VBV protection… Turns out that implementing the MPI by itself and getting the VBV page is not enough! Just so you know…

A merchant can surely try to balance the need to increase conversion, with the growing need to fight fraud, by selectively launching the 3-D Secure feature on pre-defined scenarios only.

Such scenarios can be easily configured, and will normally be related to the nature of products sold, total value of order made and billing address/shipping address conflicts.