Inquiry Message (Tran Type 22)

Note: The following description of the Inquiry process applies if SAF (Store and Forward) is disabled or POS SAF is enabled. If On-Device SAF is enabled, a modified process applies. See POS Inquiry with On-Device SAF Enabled for more information.

In normal cases, Simplify will respond to a POS request in a timely manner. If this does not occur (timeout), the POS will need to send an Inquiry message to Simplify requesting information from Fusebox about the transaction. An Inquiry message should contain all elements of the original 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).

• 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 re-sent by Simplify or through a back channel. All rules for Inquiry processing apply regardless of how the Inquiry message is re-sent.
• 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.

For more information, see the Fusebox Integration Guide under Transaction Inquiry (22).

Sample Message

Request

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

Response

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

0651,00003@;01001175950315 17501600000471705000000000 00419039807417117595