Non-Financial Messages (Tran Type 36)
Transaction Type 36 is used for non-financial purposes.
The purpose of a Tran Type 36 message is indicated by the value in the first two bytes of Field 11 which define the Message Type.
Non-Financial Message Format
The generic format for Non-Financial messages (Transaction Type 36) is described below. The other pages under this heading provide the details of each Message Type.
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 the following: Positions 1-2 Message Type |
5001,xxx.. | Non-Financial Data. The format of this field depends on the value of message type |
Message Types
Currently defined Message Types (Field 11) are as follows:
Message Type | Use | Direction |
---|---|---|
01 | Signature Request | from POS to Simplify |
02 | Signature Response | from Simplify to POS |
03 | Demo Message (NOT USED) | NOT USED |
06 | Program/Parameter Version Inquiry Message | Request from POS to Simplify. Response from Simplify to POS |
07 | Initiate IngEstate Message | Request from POS to Simplify. Response from Simplify to POS |
10 | Scrolling Receipt Message | From POS to Simplify |
11 | Scrolling Receipt Stop Message | from POS to Simplify |
12 | Exit Reversal Mode Message | from POS to Simplify |
14 | Informational Prompt Message (see note below) | Request from POS to Simplify. Response from Simplify to POS |
51 | Status Message | from POS to Simplify |
Notes:
-
Additional bytes in Field 11 can be used, depending on the message type.
-
Due to its many uses, Message Type 14 (Informational Prompt Message) is documented separately.