Inquiry Message (Tran Type 22)
In normal cases, Simplify will respond to a POS/PMS request in a timely manner. If this does not occur, the POS/PMS 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/PMS 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).
- If the POS/PMS 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/PMS after sending an Inquiry message are as follows:
- The POS/PMS 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/PMS should treat this response as a normal response to the original transaction.
- The POS/PMS 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/PMS 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/PMS will receive a host down response (Transaction Type = 22 and Field 1010 contains *SLR COMMUNICATIONS ERROR. or *SLR SWITCH TIMEOUT.) The POS/PMS must then re-send the Inquiry message until it receives a host response
- If the POS/PMS 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. Note: See also "Transaction Type Detail – Transaction Inquiry" in the Elavon Gateway Message Getting Started Guide.
Inquiry Message for a Sale Transaction
An example of an Inquiry message (from the POS process to the Simplify application) for a Sale Transaction is as follows:
| API Field #, Value | Description |
|---|---|
| 0001,22 | A value of 22 indicates an Inquiry message |
| 0002,125.98 | This must be the same value as Field 2 of the Sale Authorization Request |
| 0007,1025 | This must be the same number as Field 7 of the Sale Authorization Request |
| 0011,xxx.. | Field 11 is defined as User Data. See Appendix F for the use of this field |
| 0109,TERM1 | Terminal ID provided by Elavon. This must be the same number as Field 109 of the Sale Authorization Request |
| 8002,RETL01 | Location Name provided by Elavon. |
| 8006,TSTLAR | Chain Code provided by Elavon. |
Inquiry Response for a Sale Transaction
An example of an Inquiry Response message (from the Simplify application to the POS process) for a Sale Transaction is as follows:
| API Field #, Value | Description | |
|---|---|---|
| 0001,02 | Original transaction type (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 / Reference Number | |
| 0009,001 | Fusebox – Host Batch number | |
| 0011,xxx.. | Field 11 is defined as User Data. See Appendix F for the use of this field | |
| 0013,092815 | Transaction Date (current date) – MMDDYY | |
| 0014,151729 | Transaction Time (current time) – HHMMSS | |
| 0017,0.00 | Cash Back Amount | |
| 0030,1 | Fusebox – Online Indicator | |
| 0032,043014 | Fusebox – Authorization Transaction Date | |
| 0033,181733 | Fusebox – Authorization Transaction Time | |
| 0034,E | Fusebox – Authorization Characteristics Indicator | |
| 0035,D07D | Validation Code | |
| 0036,114120980253909 | Host Transaction Identifier (may need to appear on receipt) | |
| 0037,2 | Fusebox – Authorizer | |
| 0043,214872 | System Trace Audit Number | |
| 0049,G3 | Fusebox – Card Product Result Code | |
| 0052,3 | Transponder / Proximity Indicator (3 = contactless, 5 = swiped) | |
| 0109,TERM1 | Terminal ID provided by Elavon. | |
| 0110,205 | Cashier ID | |
| 0112,400 | Fusebox – Processor ID | |
| 0115,010 | Transaction Qualifier (010 = Credit) | |
| 0125,430181733 | Retrieval Reference Number (may need to appear on receipt) | |
| 0126,2 | Track Indicator (may need to appear on receipt | |
| 0129,1 | Fusebox – Compliance Data | |
| 0130,5.00 | Authorized Amount | |
| 0140,USD | Fusebox – Merchant Currency Trigraph | |
| 0632,5.00 | Account Balance | |
| 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 | |
| 5002,80378002 | Device Serial Number | |
| 5004,V1 | Encryption Provider ID | |
| 7007,1114281539351186 | Transaction Link Identifier. A unique identifier to link transactions | |
| 8002,RETL01 | Location Name provided by Elavon. | |
| 8006,TSTLAR | Chain Code provided by Elavon. |
See Stand-in Processing for examples of Inquiry Response messages containing 22 in Field 0001 (host timeout).