1. Overview
This document outlines the valid transaction types, response codes, and other values a merchant can expect when processing transactions. It also provides a detailed explanation of transaction reversals.
This guide covers:
- Transaction Types: A list of all supported operations (e.g.,
Sale 1,AuthOnly 6). - Response Codes: The complete list of codes returned by the gateway (e.g.,
000– Approved,FE5– Invalid Response). - Security & Verification Responses: All possible results for AVS (Address Validation) and CVV (Card Verification Value) checks.
- Transaction Reversals: A detailed explanation of why an already-approved transaction might be automatically voided by the gateway.
2. Valid Transaction Types
| Description | Field | Value |
| Sale | Sale | 1 |
| Void | Void | 2 |
| Return | Return | 3 |
| Capture | Force | 4 |
| Authorize | AuthOnly | 6 |
| Address Validation | AVSOnly | 9 |
| Inquiry | Inquiry | 10 |
| Reversal | Reversal | 11 |
| Close Batch | CloseBatch | 12 |
| Incremental Authorization | Incremental_Auth | 13 |
| Balance Inquiry | Balance_Inquiry | 14 |
| Cash Advance | CashAdvance | 18 |
| Activate | Activate | 21 |
| Add Value | AddValue | 22 |
| Deactivate | Deactivate | 23 |
| Unload | Unload | 24 |
Note: You need to use the Transaction Type Description (e.g., “Sale”, “Void”) in the transaction request.
3. Valid Recurring Frequencies
| Description | Value |
| Daily | 0 |
| Weekly | 1 |
| Bi-Weekly | 2 |
| Monthly | 3 |
| Yearly | 4 |
4. Valid Response Codes
This table includes the full response text, the internal constant (from the original document), and the code value.
| Response Text | Response Constant | Value |
| APPROVED | APPROVED | 000 |
| CARD DOES NOT EXIST | CARD_DOESNOT_EXIST (GIFT) | 001 |
| CARD NOT ACTIVE | CARD_NOT_ACTIVE (GIFT) | 002 |
| CARD EXPIRED EXCEEDS NUM OF USAGE | CARD_EXPIRED_EXCEEDS_NUM_OF_USAGE (GIFT) | 003 |
| CARD EXPIRED PAST DATE | CARD_EXPIRED_PAST_DATE (GIFT) | 004 |
| DECLINED BALANCE EQ ZERO | DECLINED_BALANCE_EQ_ZERO (GIFT) | 005 |
| DECLINED INSUFFICIENT FUNDS | DECLINED_INSUFFICIENT_FUNDS (GIFT) | 006 |
| TRANS NOT SUPPORTED | TRANS_NOT_SUPPORTED (GIFT) | 007 |
| CARD NOT SUPPORTED | CARD_NOT_SUPPORTED (GIFT) | 008 |
| INVALID CVV | INVALID_CVV (GIFT) | 009 |
| INVALID CARD STATE | INVALID_CARD_STATE (GIFT) | 00A |
| SERVICE NOT ALLOWED | SERVICE_NOT_ALLOWED | 00B |
| CARD_ALREADY_ACTIVE | CARD_ALREADY_ACTIVE | 00C |
| TOKEN EXPIRED | TOKEN_EXPIRED | 00D |
| TOKEN CARD EXPIRED | TOKEN_CARD_EXPIRED | 00E |
| PARTIAL APPROVAL | APPROVED_PARTIAL | 010 |
| DUPLICATE APPROVAL | APPROVED_DUPE | 094 |
| Device Not Configured. | DEVICE_NOT_CONFIGURED | FE0 |
| Invalid Merchant Account. | INVALID_MERCHANT_ACCOUNT | FE1 |
| Out Of Sequence. | OUT_OF_SEQUENCE | FE2 |
| Processor Unavailable. | PROCESSOR_UNAVAILABLE | FE3 |
| No Response From Server | NO_RESPONSE_FROM_SERVER | FE4 |
| Invalid Response. | INVALID_RESPONSE | FE5 |
| Invalid Transaction Data. | INVALID_TRANSACTION_DATA | FE6 |
| Server Busy. Please Try Later | SERVER_BUSY | FE7 |
| Merchant Account Deactive | MERCHANT_ACCOUNT_DEACTIVE | FE8 |
| Transaction Not Supported | TRANSACTION_NOT_SUPPORTED | FE9 |
| Invalid Amount | INVALID_AMOUNT | FEA |
| Invalid Processor Info | INVALID_PROCESSOR_INFO | FEB |
| Batch Close In Progress | BATCH_CLOSE_IN_PROGRESS | FEC |
| No such Transaction | NO_SUCH_TRANSACTION | FED |
| Declined – AVS Mismatch | AVS_MISMATCH | FEE |
| Declined – CVV Mismatch | CVV_MISMATCH | FEF |
| Nothing To Batch | NOTHING_TO_BATCH | FFA |
| Transaction Blocked | TRANSACTION_BLOCKED | FFB |
| Transaction Reversed | TRANSACTION_REVERSED | FFC |
| Transaction Reversed/Not Approved for Full Amount | PARTIAL_AUTH_NOT_SUPPORTED | FFD |
| Processor Error* | PROCESSOR_ERROR | FFE |
| Unspecified Error. | UNSPECIFIED_ERROR | FFF |
* Note on PROCESSOR_ERROR: This specific text (“Processor Error”) is generally not used. The text returned directly from the Processor is used instead.
5. Valid AVS Responses
| Description | AVS Result |
| Address Matches, Zip does not match | A |
| Street address match, Postal code in wrong format. (International issuer). | B |
| Street address and postal code in wrong formats. | C |
| Street address and postal code match (international issuer) | D |
| Error. AVS not allowed. | E |
| Non AVS Participant. | G |
| Address information not verified by international issuer. | I |
| Street Address and Postal code match (international issuer). | M |
| Address and Zip do not match. | N |
| No Response sent. | O |
| Postal codes match, Street address not verified due to incompatible formats. | P |
| Retry. System unavailable. | R |
| Service not supported. | S |
| Unavailable. | U |
| Nine digit zip matches, Address does not match. | W |
| Address and nine digit Zip match. | X |
| Address and five digit Zip match. | Y |
| Five digit Zip matches, Address does not match. | Z |
6. Valid Card Verification Value Indicators (CVVI)
| Description | CVVI Value |
| Deliberately Bypassed | 0 |
| Value is Present | 1 |
| Value is on Card but is Illegible | 2 |
| Cardholder states that the card has no CVV imprint | 9 |
7. Valid CVV Responses
| Description | CVV2 Result |
| Match | M |
| No Match | N |
| Not Processed | P |
| Should have been supplied | S |
| Issuer unable to process request | U |
8. Valid Recurring Responses
| Description | CVV2 Result |
| Success | 1 |
| Failure | 0 |
Note: A non-existing response is equivalent to a value of 0
9. Understanding Transaction Reversals
A transaction may be reversed for several reasons. A reversal voids a transaction after it was approved but before it has settled. When a transaction is reversed, it will be marked with one of the following reasons to explain why the reversal occurred:
- TOR – App/SDK Generated: The transaction timed out on the application or SDK.
- CardDecline – App/SDK Generated: The card’s chip was rejected by the processor.
- MerchantInitiated: The merchant manually sent a request to reverse the transaction.
- AVS_Mismatch – Gateway Generated: The transaction was approved by the processor, but it failed the Address Verification Service (AVS) check. The gateway was configured to automatically reverse transactions that fail this check.
- CVV_Mismatch – Gateway Generated: The transaction was approved by the processor, but it failed the Card Verification Value (CVV) check. The gateway was configured to automatically reverse transactions that fail this check.
- Partial_Auth – Gateway Generated: The gateway was configured to automatically reverse transactions that are only partially approved by the processor.
- SwipeFeeDeclined – Gateway Generated: This reversal occurs when the fee splitting service is enabled and the separate fee transaction is declined. The gateway then reverses the original sale.