An option has been added to PrismWeb for the Shift4 Iframe to allow card verification and address verification at the time the order is placed on your website. Your store can manage options to verify as well as the level of verification in PrismWeb Manager.
...
To use the card verification option you will need to choose the options for what type of verification you would like to use on your website. If using the AVS (Address Verification Service), you will need to also set the sensitivity level for the verification. To set these options, in PrismWeb Manager, navigate to Setup > Site Options > Payment Processors.
Setting Credit Card Verification Level
In the Card Verification section of the Payment Processors page, select from the drop down the level of verification for your website. The drop down options are:
Off – No card verification will be done at the time the order is placed
Verify Without AVS Check – The credit card will be checked to verify it is an active card. It will also verify the card number, expiration date, and security code are accurate.
Verify with AVS Check – The credit card will be checked to verify it is an active card. It will also verify the card number, expiration date, and security code are accurate. The name and address are also verified based on the AVS Sensitivity level selected.
Setting AVS Sensitivity Level
When the Card Verification option is set to Verify with AVS Check, the AVS Sensitivity section will need to be set. The default sensitivity level is Medium. If you would like to adjust this option, in the AVS Sensitivity section of the Payment Processors page, select the radial button next to the option you would like to use for your website. The options are:
...
Processes and Error Messages
Card Verification Process
The credit card verification process creates a $0 transaction that immediately gets voided. During this process two things happen. First it is determined whether or not the bank will allow the transaction based on the card number, expiration date, and security code that the user entered. Second, if the bank allows the transaction, a security check is done to verify that the security code entered is correct. If you turn on AVS, a third step is added.
...
This section is to document and inform about any issues that may be encountered with card verification and AVS.
Error Messages Shoppers May See
“Card verification failed (<Description from Step 1 Table>). Please try again or use a different form of payment.”
This error is a result of the transaction not getting approved by the bank. Check Step 1 table for a better idea of why it failed by looking up the message in the error’s parenthesis.
...
“Card verification failed (<Value from Step 3 Table>). Please make sure the billing name, address, and zip code match what is listed in your card's bank.“
This error means the bank approved the transaction and security code validation passed but there was a problem with the user’s billing info (name, address, or zip). Use the letter in the error’s parenthesis to get more details of why it failed from Step 3 table.
Problems and Solutions
P. Payment Processor is Moneris and all transactions are getting declined, even cards that are known to be good.
S. Contact Moneris and make sure the setting “Status Enquiry” is enabled.
P. Stores using Shift4 and Elavon are getting declines on all VISA transactions.
S. Go to Site Options>Payment Processors and make sure Security Code Exception is checked. There are four lines of code regarding the CVV information on the card that are not being sent back to PrismWeb, which causes the card to decline. Checking this box allows PrismWeb to allow the card to process as long as all other information is correct, and this will allow the orders to be accepted on the web. If there does wind up being as issue with the CVV, the transaction will be declined in PrismCore when it is being processed as the four lines of code do flow through to PrismCore when the order is processed.
...