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 |
---|---|
0002 | Transaction Amount |
0007 | Transaction ID / Reference Number |
0109 | Terminal ID |
8002 | Location Name |
8006 | Chain Code |
Sample Inquiry Request
An example of an Inquiry Request message (from the POS to Simplify) is as follows:
API Field #, Value | Description |
---|---|
0001,22 | Transaction Type. |
0002,125.98 | Transaction Amount. Must match the financial request. |
0007,1025 | Transaction ID / Reference Number. Must match the financial request. |
0011,xxx.. | User Data. See Simplify-Controlled Field Definitions for the use of this field |
0013,092818 | Transaction Date (current date) – MMDDYY |
0014,131559 | Transaction Time (current time) – HHMMSS |
0109,TERM1 | Terminal ID. Must match the financial request. |
1008,ID: | Set to ID: to request that an account token be returned by Fusebox. |
8002,RETL01 | Location Name. Must match the financial request. |
8006,TSTLAR | Chain 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 #, Value | Description |
---|---|
0001,02 | Original transaction type (entire response = original host response) |
0002,5.00 | Transaction Amount |
0003,ID:4546705467010002 | Account Token (returned by Fusebox) |
0004,1221 | Expiration Date MMYY |
0006,CVI758 | Authorization Code (returned by Fusebox) |
0007,558 | Transaction ID / Reference Number |
0009,001 | Fusebox – Host Batch number |
0011,xxx.. | User Data. See Simplify-Controlled Field Definitions for the use of this field |
0013,092818 | Transaction Date (current date) – MMDDYY |
0014,131608 | Transaction Time (current time) – HHMMSS |
0017,0.00 | Cash Back Amount |
0030,1 | Fusebox – Online Indicator |
0032,092818 | Fusebox – Authorization Transaction Date |
0033,181633 | Fusebox – Authorization Transaction Time |
0035,D07D | Validation Code |
0036,114120980253909 | Host Transaction Identifier |
0037,2 | Fusebox – Authorizer |
0043,214872 | System Trace Audit Number |
0047,M;1;1;1;0;1;5;1;1;3;3;C;0;4 | POS Data Code |
0052,5 | Transponder / Proximity Indicator (0 = contact; 2 = contactless; 5 = swiped) |
0054,05 | POS Entry Mode |
0055,9 | PIN Capabilities |
0057,0 | ICC Chip Condition Code |
0062,201 | Service Code |
0109,TERM1 | Terminal ID |
0110,205 | Cashier ID |
0112,400 | Fusebox – Processor ID |
0115,010 | Transaction Qualifier (010 = credit; 030 = debit) |
0125,430181733 | Retrieval Reference Number (may need to appear on receipt) |
0126,2 | Track Indicator (may need to appear on receipt) |
0130,5.00 | Authorized Amount |
0140,USD | Fusebox – Merchant Currency |
0651, [see value below] | Reversal data (for reversal, if needed) |
0738,0 | Recurring Compliance Data |
1000,VI | Card Type |
1001,VISA | Card Name |
1003,0000 | Gateway Response Code |
1004,APPROVAL | Host Response Message |
1005,0010600008014593613999 | Merchant Number |
1008,************0002 | Masked Account Number (may need to appear on receipt) |
1009,AA | Host Response Code |
1010,COMPLETE | Gateway Response Message |
1012,1784 | Gateway Batch Number |
1339,00 | EMV Response Code |
5002,169018710 | Device Serial Number |
5004,V1 | Encryption Provider ID |
5010,L27.0.2 | EMV Kernel Version |
7007,1114281539351186 | Transaction Link Identifier (a unique identifier to link transactions) |
8002,RETL01 | Location Name |
8006,TSTLAR | Chain Code |
0651,00005A;010002312402212201000000062
005900000610025028453905222023124