Testing the Prepaid Filtering Feature
Complete this test only if you are planning on using the FraudSight Prepaid Filtering Feature and are using schema version 8.3 or above.
To test the Prepaid Filtering feature:
-
Submit authorization transactions using the values provided in Supplied Data Elements of Table 2-16.
-
Verify that your response values match those shown in the Key Response Elements section of Table 2-16.
-
After you complete this test, go to the next test.
TABLE 2-16 Prepaid Filtering Test Data
|
orderId |
Supplied Data Elements |
Key Response Elements |
||
|---|---|---|---|---|
|
Element |
Value |
Element |
Value |
|
|
filterPrepaidMC |
<amount> <orderSource> <name> <addressLine1> <city> <state> <zip> <country> <email> <phone> <type> <number> <expDate> <prepaid> |
9100 recurring John Doe 10 Main St. San Jose CA 95032 US jdoe@phoenixProcessing.com 7812701111 MC 5500000958501839 1121 true |
<response> <message> <avsResult>
|
309 Restricted Card - Prepaid Card Filtering Service 34
|
|
filterPrepaidVI |
<amount> <orderSource> <name> <addressLine1> <city> <state> <zip> <country> <email> <phone> <type> <number> <expDate> <prepaid> |
9100 recurring John Doe 10 Main St. San Jose CA 95032 US jdoe@phoenixProcessing.com 7812701111 VI 4650002010001478 1121 true |
<response> <message> <authCode> <avsResult>
|
309 Restricted Card - Prepaid Card Filtering Service none 34
|