Vantiv CVV and AVS Security Update

This release contains changes to payment transaction processing for clients using the Vantiv/Mercury payment method. This applies to the original standard Mercury Payment Systems implementation and to the more recent Vantiv HostedCheckout implementation.

To view your method of payment processing, click on the ADMIN tab and go to Payment Acceptance.

paymentacceptance.jpg

This update applies Mercury Payment Systems (ECommerce)Mercury Payment Systems Hosted (ECommerce)Mercury Payment Systems (Retail/Moto), and Mercury Payment Systems Hosted (Retail/Moto).

merc.jpg

We have enhanced security by validating Address Verification (AVS) and Card Security Codes (CVV/CVV2/CID). To put it more plainly, a user entering a credit card (manually keyed entry only) will also need to include the correct Zip Code (AVS) and the security code located on the back of the credit card (CVV, CVV2, CID). This helps prevent fraud and protects our merchants.

payment.jpg

In the event that a Zip Code (AVS) and Card Security Code (CVV/CVV2/CID) do not match what is on file with the card issuing bank, the transaction will not be approved.

This will generate one of the following error messages:



cvverror.jpg

This update also includes new CVV field length validation. A valid field length is based on card type:

  • American Express: valid CVV length is 4 numeric digits 
  • MasterCard: valid CVV length is 3 numeric digits 
  • Visa: valid CVV length is 3 numeric digits 
  • Discover: valid CVV length is 3 numeric digits

If the CVV is not a valid length as described above, the following pop-up warning message will display near the top of the screen:



This update helps to prevent fraud and ensures the security of transactions made through Vantiv/Mercury.

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.