Below are all the possible NMI gateway response codes that you will receive when trying to process a transaction. These are returned directly from NMI in response to transaction processing, and are not Admoji errors. If you receive any one of these errors and cannot understand why, you must contact your merchant processor for more information and a possible solution.
Transaction Result Code Table:
| Error Code | Error Response | Description |
|---|---|---|
| 100 | Transaction was approved. | |
| 200 | Transaction was declined by processor. | The customer's bank is unwilling to accept the transaction. The reasons for this response can vary – the customer will need to contact their bank for more details. |
| 201 | Do not honor. | The customer's bank is unwilling to accept the transaction. The customer will need to contact their bank for more details regarding this decline. |
| 202 | Insufficient funds. | The account did not have sufficient funds to cover the transaction amount at the time of the transaction. |
| 203 | Over limit. | The attempted transaction exceeds the withdrawal limit of the account. The customer will need to contact their bank to change the account limits or use a different payment method. |
| 204 | Transaction not allowed. | The customer's bank is declining the transaction for unspecified reasons, possibly due to an issue with the card itself. They will need to contact their bank or use a different payment method. |
| 220 | Incorrect payment information. | |
| 221 | No such card issuer. | This decline code could indicate that the submitted card number does not correlate to an existing card-issuing bank or that there is a connectivity error with the issuer. The customer will need to contact their bank for more information. |
| 222 | No card number on file with issuer. | The submitted card number is not on file with the card-issuing bank. The customer will need to contact their bank. |
| 223 | Expired card. | The card is expired. The customer will need to use a different payment method. |
| 224 | Invalid expiration date. | The customer entered an invalid payment method or made a typo in their card expiration date. Have the customer correct their payment information and attempt the transaction again – if the decline persists, they will need to contact their bank. |
| 225 | Invalid card security code. | The customer entered in an invalid security code or made a typo in their card information. Have the customer attempt the transaction again – if the decline persists, the customer will need to contact their bank. |
| 226 | Invalid PIN. | Can mean Invalid PIN or missing PIN. Some cards can be set to always require a PIN. |
| 240 | Call issuer for further information. | |
| 250 | Pick up card. | The customer's card has been reported as lost or stolen by the cardholder and the card-issuing bank has requested that merchants keep the card and call the number on the back to report it. As an online merchant, you don't have the physical card and can't complete this request – obtain a different payment method from the customer. |
| 251 | Lost card. | The card used has likely been reported as lost. The customer will need to contact their bank for more information. |
| 252 | Stolen card. | The card used has likely been reported as stolen. The customer will need to contact their bank for more information. |
| 253 | Fraudulent card. | The customer's bank suspects fraud – they will need to contact their bank for more information. |
| 260 | Declined with further instructions available. (See response text) | |
| 261 | Declined-Stop all recurring payments. | |
| 262 | Declined-Stop this recurring program. | |
| 263 | Declined-Update cardholder data available. | The submitted card has expired or been reported lost and a new card has been issued. Reach out to your customer to obtain updated card information. |
| 264 | Declined-Retry in a few days. | |
| 300 | Transaction was rejected by gateway. | |
| 400 | Transaction error returned by processor. | |
| 410 | Invalid merchant configuration. | |
| 411 | Merchant account is inactive. | |
| 420 | Communication error. | |
| 421 | Communication error with issuer. | |
| 430 | Duplicate transaction at processor. | |
| 440 | Processor format error. | |
| 441 | Invalid transaction information. | |
| 460 | Processor feature not available. | |
| 461 | Unsupported card type. |
CVV Response Codes:
| Code | Description |
|---|---|
| M | CVV2/CVC2 match |
| N | CVV2/CVC2 no match |
| P | Not processed |
| S | Merchant has indicated that CVV2/CVC2 is not present on card |
| U | Issuer is not certified and/or has not provided Visa encryption keys |
AVS Response Codes:
| Code | Description |
|---|---|
| X | Exact match, 9-character numeric ZIP |
| Y | Exact match, 5-character numeric ZIP |
| D | Exact match, 5-character numeric ZIP |
| M | Exact match, 5-character numeric ZIP |
| 2 | Exact match, 5-character numeric ZIP, customer name |
| 6 | Exact match, 5-character numeric ZIP, customer name |
| A | Address match only |
| B | Address match only |
| 3 | Address, customer name match only |
| 7 | Address, customer name match only |
| W | 9-character numeric ZIP match only |
| Z | 5-character ZIP match only |
| P | 5-character ZIP match only |
| L | 5-character ZIP match only |
| 1 | 5-character ZIP, customer name match only |
| 5 | 5-character ZIP, customer name match only |
| N | No address or ZIP match only |
| C | No address or ZIP match only |
| 4 | No address or ZIP or customer name match only |
| 8 | No address or ZIP or customer name match only |
| U | Address unavailable |
| G | Non-U.S. issuer does not participate |
| I | Non-U.S. issuer does not participate |
| R | Issuer system unavailable |
| E | Not a mail/phone order |
| S | Service not supported |
| 0 | AVS not available |
| O | AVS not available |
| B | AVS not available |
Note: These response codes are specific to NMI Gateway
and
are returned directly from the payment processor. If you encounter any
of
these errors and need clarification, contact your merchant processor
for
detailed information about the specific transaction and possible solutions.
Tip: Understanding these response codes will help you better
communicate with your customers about transaction issues and provide appropriate
guidance for resolving payment problems.