Note: Use the PaymentProcessCVV system option to choose if the CVV code is required or optional for credit card purchases.
Sage 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.
Sage provides six codes, and by default, netFORUM identifies two of those codes. You can use the CVVMatchResponseCodes Merchant Account Code to configure what netFORUM does in response to the four CVV response codes that are undefined.
This topic describes the six codes and how to configure netFORUM to respond to the four undefined codes according to your organization's business rules.
Below are the codes that Sage could return in response to a CVV entry:
Caution! Sage 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 | The CVV entered was a valid match for the credit card’s account. | successful authorization |
N | 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 | Service not supported | configurable |
U | Unavailable. This is not a common response. It tends to happen if the bank is not certified to validate CVV. This could happen for certain international credit cards. | configurable |
X | No Response | configurable |
Example: Your entered values might look like this: P;S;X