The BluePay Gateway has a CVV filter that can be set by the merchant. It is a list of CVV response codes to accept. If a CVV response code is received that is not on the list the transaction is voided and decline result is returned to Blesta. It is not mandatory that this filter be configured and by default no filter is set. With no filter all CVV response codes are accepted.
There are a few ways that the problem could be fixed. The simplest solution would be to remove the filter. This would solve the problem but also create a higher chance of fraud. The better solution would be to include a underscore "_" in the filter. Underscore is the CVV response code when no CVV was supplied for processing. By having the filter include the underscore and the response codes to accept the filter would be used when there was a CVV and bypassed when there isn't.
Just for reference here is a list of the possible CVV response codes.
_ = No Value Supplied
M = CVV2 Match
N = CVV2 did not match
P = CVV2 was not processed
S = CVV2 exists but was not input (Not possible on the BluePay Gateway)
U = Card issuer does not provide CVV2 service
X = No response from association
Mel Sleight
Integration Support
BluePay Processing, Inc.
