This document provides a list of predefined trigger values that can be used to test various transaction responses within Charge Anywhere.
Note: You get an Approved response for all other amounts besides the amount values listed below.
Transaction Response Trigger Values
These values simulate different transaction responses based on the amount entered.
| Amount | Response Description | AVS Response Code | AVS Response Description | CVV Response Description | Notes |
|---|---|---|---|---|---|
| 998.01 | Partial Authorization | – | – | – | – |
| 998.02 | Duplicate Approval | – | – | – | – |
| 998.03 | Decline | – | – | – | 99803, 200, 300, 400, 500, 600, 700, 1000, 1200 (Various decline scenarios) |
| 998.04 | Approved | A | Address match only | – | – |
| 998.12 | Approved | N | Neither Address nor Zip match | – | – |
| 998.20 | Approved | Y | Address and Zip match | – | – |
| 998.21 | Approved | Z | Zip only match | – | – |
| 998.22 | Approved | – | – | CVV Match | – |
| 998.23 | Approved | – | – | No CVV Match | – |
| 898.28 | Invalid Pin | – | – | – | – |
| 998.29 | Device not Configured | – | – | – | – |
| 998.30 | Invalid Merchant Account | – | – | – | – |
| 998.31 | Processor Unavailable | – | – | – | – |
| 998.32 | No Response from Server | – | – | – | – |
| 998.33 | Invalid Transaction Data | – | – | – | – |
| 998.34 | Server Busy | – | – | – | – |
| 998.35 | Merchant Account Deactivated | – | – | – | – |
| 998.36 | Transaction Not Supported | – | – | – | – |
| 998.37 | Invalid Amount | – | – | – | – |
| 998.38 | Invalid Processor Info | – | – | – | – |
| 998.39 | Batch Close in Progress | – | – | – | – |
| 998.40 | No Such Transaction | – | – | – | – |
| 998.41 | Declined AVS Mismatch | – | – | – | – |
| 998.42 | Declined CVV Mismatch | – | – | – | – |
| 998.43 | Nothing to Batch | – | – | – | – |
| 998.44 | Unspecified Error | – | – | – | – |
| 998.45 | Approved Duplicate | – | – | – | – |
Notes
- You get an Approved response for all other amounts besides the amount values listed above.
- The listed amounts can be used to trigger specific transaction responses during testing.
- If additional scenarios are needed, consult the Charge Anywhere support team.
Reference Usage: Whenever a testing transaction requires predefined values, refer to this document and use the corresponding amount to trigger the expected response.