Testing Security Code No-Match Filtering
Complete this test only if you are planning on using the FraudSight Security Code No-Match Filtering Feature. To test the Security Code No-Match feature:
-
Submit authorization transactions using the values provided in Supplied Data Elements of Table 2-18.
-
Verify that your response values match those shown in Key Response Elements section of Table 2-18.
After you complete this test, go to the next test.
TABLE 2-18 Security Code No-Match Filtering Test Data
|
orderId |
Supplied Data Elements |
Key Response Elements |
||
|---|---|---|---|---|
|
Element |
Value |
Element |
Value |
|
|
securityCodeFilter1 |
<amount> <orderSource> <name> <addressLine1> <city> <state> <zip> <country> <type> <number> <expDate> <cardValidationNum> |
9100 ecommerce John Doe 10 Main St. San Jose CA 95032 US MC 5112002200000008 1121 123 |
<response> <message>
<avsResult> <cardValidationResult>
|
358 Restricted by Vantiv due to security code mismatch. 14 N
|
|
securityCodeFilter2 |
<amount> <orderSource> <name> <addressLine1> <city> <state> <zip> <country> <type> <number> <expDate> <cardValidationNum> <international> |
9100 ecommerce Jane Doe 10 Main St. San Jose CA 95032 US MC 5112000200000002 1121 123 false |
<response> <message>
<avsResult> <cardValidationResult>
|
358 Restricted by Vantiv due to security code mismatch. 20 N
|