Gateway Response Codes

On each transaction response, Fusebox returns a Gateway Response Code (API Field 1003) and Gateway Response Text (API Field 1010). The response code is to be evaluated by the integrated POS/PMS system to determine if a transaction was successful or not.

Field 1003 CodeField 1010 TextDescription
0000COMPLETETransaction was successful and approved on line (if applicable).
0005DUPLICATEThe transaction is a duplicate of a previously successful transaction based on the same account number, amount, reference number and locator values.
0016Final $ TOO LRGThe amount of the prior authorization is greater than the total authorized amount
0022EMPTY BATCHThere are no transactions for settlement within the batch.
0037CANNOT READThere is invalid data within the transaction that prevents it from being read and processed.
0041BAD ACCT NUMBERThe account number in API field 0003 is invalid
0043BAD TRAN AMOUNTThe amount value in API field 0002 is invalid
0044BAD AUTH AMTThe total authorized amount value in API field 0128 is invalid
0046BAD CARD INFOThe card number or track data in API field 0003 is invalid
0047BAD CARD TYPEThe card type or tender type of the account in API field 0003 is invalid for the merchant
0049BAD EXPIRATIONThe expiration date in API field 0004 is invalid.
0054BAD REF NBRThe reference number in API field 0007 is invalid.
0057INVALID TERM IDThe locator values in API fields 0109, 8003, or 8006 are incorrect or invalid.
0059BAD TRAN CODE
Processor Response Text (varies by TPP)
The transaction type in API field 0001 is invalid.
0060Processor Response text (Varies by TPP)The transaction was not approved by the Third Party Processor.
0067MISSING REQ FLDA required API field is missing for this transaction.
0088SWITCH TIMEOUTThe transaction sent to the Third Party Processor timed out waiting for a response.
0097INVALID DATAThere is invalid data within one or more API fields of this transaction.
0099ERROR CODE: ### = [Internal Error Text (Varies) ]The transaction was unsuccessful for while processing.
0100BAD_DCC_ELG_FLAGThe DCC Eligibility Flag in API field 0151 is invalid.
0166SWITCH DOWNThe Third Party Interface is unable to connect and process transactions to the host.
0173TRAN NOT ALLOWEDThe transaction type in API field 0001 is not supported for this merchant or allowed within the transaction life cycle.
0182HOST NOT FOUNDThe Third Party host is not available process transactions.
0244TOKEN NOT FOUNDThe token provided in API field 0003 was not found and could not be detokenized for processing.
0280VOLTAGE ERRORDecryption of the account data using Voltage failed.
0281Verifone ERRORDecryption of the account data using Verifone failed.
0282PROTEGRITY ERRORThe Tokenization/Detokenization of the account data using Protegrity failed.
0283SAFETY ERRORTokenization or Encryption processing failed.
0284VOLTAGE COMPLETEThe Voltage Encryption Initialization was successful.
0285Verifone COMPLETThe Verifone Encryption Initialization was successful.
0286CARD NOT ENCRYPTThe card/track data in API field 0003 is not encrypted when it is expected to be encrypted based on merchant setup.
0287BAD_DCC_RATEThe DCC Conversion Rate in API field 0150 is invalid.
0288BAD_DCC_EXPONENTThe DCC Conversion Rate Exponent in API field 0159 is invalid.
0289BAD_DCC_MARKUPThe DCC Markup Percentage in API field 0165 is invalid.
0290BAD_DCC_OPTIONThe DCC Eligibility Flag in API field 0151 is invalid.
0291BAD_DCC_POS_CAPThe DCC POS Capability in API field 0169 is invalid
0300BAD_CURRENCY_CDEThe DCC Currency Code in API field 0140 or 0142 is invalid.
0301BAD_DCC_AMTThe DCC Amount in API field 0144 is invalid.
0302ON GUARD ERRORDecryption of the account data using On Guard failed.