This section provides details on message types sent between Simplify and the POS. This covers financial messages (message types which can have a financial impact) and various types of non-financial messages (no direct financial impact).
Financial messages are normally processed online by means of a message exchange between Fusebox and Simplify. Some non-financial messages are also processed via Fusebox (e.g. Inquiry, Batch Close). For additional information on these message types, see the Fusebox Integration Guide, especially under Transaction Types.
Other non-financial message types are not sent to Fusebox (e.g. Cancel, Health messages). Many of these message types are grouped together under Transaction Type 36 and referred to as Non-Financial Messages. The last part of this chapter defines the API for Simplify Non-Financial Messages.
All messages follow the Elavon Gateway (Fusebox) API where applicable. For a complete list of Gateway API fields, see the Fusebox Integration Guide under API Reference.
Note: Message samples given under Message Details do not include:
Control characters. See further under Message and Communications Protocols.
EMV fields. See further under EMV.
Offline and SAF processing. For samples of such processing, see under POS SAF Processing (Simplify support for SAF performed by the POS) and On-Device SAF (SAF performed by Simplify).
Guidelines for Handling Financial Messages
Messages built for Simplify and the handling of messages received from Simplify should be based on the following set of principles:
If account data is sent in Field 3 of the POS request, the Tender Type is required in Field 115 (Transaction Qualifier).
If the POS wants Simplify to prompt for Manual Entry, send ‘K’ in Field 3.
If the data in Field 2 (Amount) or any other amount field does not include a decimal point, the decimal point will be assumed. (E.g., a value of 2000 in this field will be read as 20.00.)
For API 0047, see the Fusebox Integration Guide under POS Data Code, including the rules for transaction types that refer back to a previous transaction (e.g. Void, Prior Auth).
Fields 13 (date) and 14 (time) are required in all financial requests.
Elavon recommends not padding Field 7 (Transaction ID / Reference Number) with leading zeros. Elavon recommends presenting this field in the same manner in all messages.
The sample messages in this document are basic samples. The POS should be able to handle any additional API fields in the response as defined under Fusebox API Reference.
If a Void Request needs to be re-sent, it should be sent without modification until a Host Response is received.
If a voice auth transaction is sent to Simplify without an account number or a token in field 3, Simplify will prompt for account data. The operator verifies that the account data for which voice auth was obtained matches that entered at the PIN Pad.
Elavon recommends sending Field 5071 in all financial requests, using the value that reflects the actual transaction environment. See under Simplify-Controlled Field Definitions.
The value in field 0007 (Transaction ID / Reference ID) is incremented by the POS for each new transaction.