Informational Prompting

Simplify supports an Informational Prompt Message on the MX915 and MX925. This is a flexible feature designed to allow merchants to display information for customers and get customer input using a variety of screen layouts. This message type does not affect the processing of financial transactions.

The POS controls this process by sending an Informational Prompt Message that defines the screen to be displayed. The PIN Pad must be in a Closed state to process this request, with the following exceptions:

  • If another Informational Prompt Request is sent when the PIN Pad is already displaying an informational prompt screen, the display for the second request will replace the first screen.

  • After sending an Informational Prompt Response, the PIN Pad will display a wait screen for a configurable interval before going to the Closed state. If a new Informational Prompt Request is sent during this interval, the PIN Pad will process the request.

If the full display for an Informational Prompt message will not fit on the screen, you can view the remaining text and/or fields by scrolling with your finger. The screen will move in the opposite direction from your finger. Note: a scroll indicator will briefly display.

Elavon recommends that customers verify the format of all displayed text.

Simplify returns the customer input in the Informational Prompt Response. Input includes the action (virtual) button or hard key pressed, and depending on the type of Informational Prompt message sent, may also include entered text or a selected radio button, check boxes, or slider position. Additional requests can be sent if further customer interaction is required.

Informational Prompt Message Format

The Informational Prompt Message is a Non-Financial Message (Transaction Type 36) with a Message Type of 14. It is discussed separately in this chapter due to its many uses.

Non-Financial Message Format

As described under Message Details, Non-Financial Messages have the following generic format.

API Field #, Value Description
0001,36 Transaction Type 36; Non-Financial message
0011,xxx.. Field 11 is defined as User Data. See Appendix F for the use of this field.
For Transaction Type 36, it will always include Positions 1-2 Message Type.
5001,xxx.. Non-Financial Data.
The format of this field depends on the value of Message Type.

Fields 11 and 5001 in Informational Prompt Messages

The remainder of this page provides information on fields 11 and 5001 specific to the Informational Prompt Message.


The format of Field 11 in the Informational Prompt Message (36-14) is modeled that in the Signature Request and Response Messages (36-01, 36-02). Note that the Screen ID subfield of Field 11 in the Request is not used (always set to 001). The Response echoes the Request except: (1) the Timeout Value is replaced with the Completion Code, and (2) the end of the Response includes the Version / Build number.

Field 11 Subfield Length Description
Message Type 2 Always 14
Sequence Number 3 Transaction identifier
Screen ID 3 Not used (set to 001)
Timeout Value/ Completion Code 3 Request: Screen timeout in seconds (000=No timeout)
Response: Completion Code (000=Success)
See Appendix F for more information.
VersionBuildInfo Var Response only: "?" followed by Version and Build numbers

FIELD 5001

In the Informational Prompt Message, Field 5001 is used in the Request to define the screen that will be displayed and in the Response to return customer action/data entered. The generic structure of Field 5001 is TTTLLLVVV..VV, broken down as follows.

Field 5001 Subfield Length Description
TTT 3 Tag identifying screen to be displayed>
010=Text with optional buttons
020=Scrolling text
030=Virtual keyboard
040=Radio buttons
050=Check boxes
070=Scrolling text with radio buttons
071= Scrolling text with virtual buttons
LLL 3 Length of data (VVV…VV)
Note: If data is longer than 999 bytes, set LLL to 999. The application will process the additional data.
VVV…VV var Data

The pages that follow provide detailed breakdowns of Field 5001 and sample messages for each supported value of Tag.

Note: The following samples use FS to represent a 1 byte field separator.