Use the PaymentProcessCVV system option to choose if the CVV code is required or optional for credit card purchases.
Vantiv provides a response code for a credit card CVV number when a credit card authorization is attempted. Depending on the CVV response code, netFORUM determines if the CVV is a valid match. If the match is not valid, then netFORUM voids the authorization.
Vantiv provides five codes, and by default, netFORUM identifies two of those codes, M and N. You can use the CVVMatchResponseCodes Merchant Account Code to configure what netFORUM does in response to the three CVV response codes that are undefined.
This topic describes the five codes and how to configure netFORUM to respond to the three undefined codes according to your organization's business rules.
Caution! Vantiv returns these codes even if the credit card number is invalid. In that case, the CVV response code is irrelevant.
Response Code | Description | netFORUM's Response |
---|---|---|
M | Match. The CVV entered was a valid match for the credit card’s account. | successful authorization |
N | No Match. A CVV code was collected and sent to the gateway, but that the CVV code did not match. | declined authorization |
P | Not Processed. Most commonly this occurs when the CVV is not passed with the authorization. | configurable |
S | Should be present. The security code should be present but the cardholder has reported that it is not. | configurable |
U | Not Supported. This Verification service is unavailable or issuer does not support this service. | configurable |
Example: Your entered values might look like this: P;S;U