2009

Transaction Responses
Card Security Code Result Codes
A
44 Payflow Link User’s Guide
FIGURE A.1 Credit card security code locations
Card Security Code Results
If you submit the transaction request parameter for card security code (that is, the CVV2
parameter), the cardholder’s bank returns a Yes/No/ response in the CVV2MATCH response
parameter, as per the table below.
Card security code results vary depending on your processing platform, as described in the
table below.
TABLE A.5 CVV2MATCH response values
CVV2MATCH Value Description
Y The submitted value matches the data on file for the card.
N The submitted value does not match the data on file for the card.
X The cardholder’s bank does not support this service.
TABLE A.6 Card security code results
Processing Platform Results
American Express Phoenix
Global Payments – East
Global Payments – Central
Merchant e-Solutions
Nova
Vital
Card security code mismatches may cause a non-approved result
(RESULT = 112 or 114) in some cases. In other cases, the
transaction may be approved despite the card security code
mismatch.
The match or mismatch information is indicated in the
CVV2MATCH value.
FDMS Nashville
FDMS South
Paymentech New Hampshire
Paymentech Tampa
Transactions that have card security code mismatches can come
back as an approved transaction (RESULT = 0).
The match or mismatch information is indicated in the
CVV2MATCH value.
As with AVS, if the Authorization was successful, you must make
a decision based on the CVV2MATCH value whether or not to
proceed with the order.