Inquiry Message (Tran Type 22)

In normal cases, Simplify will respond to a POS request in a timely manner. If this does not occur, the POS will need to send an Inquiry message to Simplify requesting information from Fusebox about the transaction.

  • Inquiry processing is required for the following situations:
    • No response to a financial request.
    • Field 1010 in the financial response contains one of the following:
      • *SLR STAND-IN.
      • *SLR COMMUNICATIONS ERROR.
  • After sending an Inquiry message, Elavon highly recommends that the POS wait for a response and continue processing based on the response. The Inquiry message should be resent until it receives one of the following:
    • Fusebox approval for the original transaction
    • Fusebox decline for the original transaction
    • Fusebox no record response (Field 1010 = NO RECORDS FOUND).

important

If the POS stops sending Inquiry messages for a transaction before receiving a Fusebox response, the transaction will need to be reconciled manually.

  • The possible outcomes at the POS after sending an Inquiry message are as follows:
    • The POS receives a normal transaction response. (Transaction Type = original). This response indicates that the Inquiry message and the original transaction were both processed online by Fusebox. The POS should treat this response as a normal response to the original transaction.
    • The POS receives a no record response. (Transaction Type =22 and Field 1010 contains NO RECORDS FOUND). This response indicates that the original request was NOT processed by Fusebox. The POS can proceed in accordance with corporate policy. E.g. a Void Request can be sent for the transaction.
    • If the Inquiry message times out at the host, the POS will receive a host down response (Transaction Type = 22 and Field 1010 contains *SLR COMMUNICATIONS ERROR. or *SLR SWITCH TIMEOUT.) The POS must then re-send the Inquiry message until it receives a host response
    • If the POS times out before receiving an Inquiry Response, it must re-send the Inquiry message until it receives a host response.
  • The Inquiry message can be resent by Simplify or through a back channel. All rules for Inquiry processing apply regardless of how the Inquiry message is resent.
  • The Inquiry message can be sent any time before the Gateway Batch Close.

The following table shows a sample of fields in the Inquiry message that may need to match fields in the original transaction. See the Fusebox Integration Guide under “Transaction Types” > “Transaction Inquiry (22)” for more information.

API Field #Description
0002Transaction Amount
0007Transaction ID / Reference Number
0109Terminal ID
8002Location Name
8006Chain Code

Sample Inquiry Request

An example of an Inquiry Request message (from the POS to Simplify) is as follows:

API Field #, ValueDescription
0001,22Transaction Type.
0002,125.98Transaction Amount. Must match the financial request.
0007,1025Transaction ID / Reference Number. Must match the financial request.
0011,xxx..User Data. See Simplify-Controlled Field Definitions for the use of this field
0013,092818Transaction Date (current date) – MMDDYY
0014,131559Transaction Time (current time) – HHMMSS
0109,TERM1Terminal ID. Must match the financial request.
1008,ID:Set to ID: to request that an account token be returned by Fusebox.
8002,RETL01Location Name. Must match the financial request.
8006,TSTLARChain Code. Must match the financial request.

Sample Inquiry Response

An example of an Inquiry Response message (from Simplify to the POS) for a Sale transaction is as follows:

API Field #, ValueDescription
0001,02Original transaction type (entire response = original host response)
0002,5.00Transaction Amount
0003,ID:4546705467010002Account Token (returned by Fusebox)
0004,1221Expiration Date MMYY
0006,CVI758Authorization Code (returned by Fusebox)
0007,558Transaction ID / Reference Number
0009,001Fusebox – Host Batch number
0011,xxx..User Data. See Simplify-Controlled Field Definitions for the use of this field
0013,092818Transaction Date (current date) – MMDDYY
0014,131608Transaction Time (current time) – HHMMSS
0017,0.00Cash Back Amount
0030,1Fusebox – Online Indicator
0032,092818Fusebox – Authorization Transaction Date
0033,181633Fusebox – Authorization Transaction Time
0035,D07DValidation Code
0036,114120980253909Host Transaction Identifier
0037,2Fusebox – Authorizer
0043,214872System Trace Audit Number
0047,M;1;1;1;0;1;5;1;1;3;3;C;0;4POS Data Code
0052,5Transponder / Proximity Indicator (0 = contact; 2 = contactless; 5 = swiped)
0054,05POS Entry Mode
0055,9PIN Capabilities
0057,0ICC Chip Condition Code
0062,201Service Code
0109,TERM1Terminal ID
0110,205Cashier ID
0112,400Fusebox – Processor ID
0115,010Transaction Qualifier (010 = credit; 030 = debit)
0125,430181733Retrieval Reference Number (may need to appear on receipt)
0126,2Track Indicator (may need to appear on receipt)
0130,5.00Authorized Amount
0140,USDFusebox – Merchant Currency
0651, [see value below]Reversal data (for reversal, if needed)
0738,0Recurring Compliance Data
1000,VICard Type
1001,VISACard Name
1003,0000Gateway Response Code
1004,APPROVALHost Response Message
1005,0010600008014593613999Merchant Number
1008,************0002Masked Account Number (may need to appear on receipt)
1009,AAHost Response Code
1010,COMPLETEGateway Response Message
1012,1784Gateway Batch Number
1339,00EMV Response Code
5002,169018710Device Serial Number
5004,V1Encryption Provider ID
5010,L27.0.2EMV Kernel Version
7007,1114281539351186Transaction Link Identifier (a unique identifier to link transactions)
8002,RETL01Location Name
8006,TSTLARChain Code

0651,00005A;010002312402212201000000062
005900000610025028453905222023124