This section provides details on message types sent between Simplify and the POS. These messages follow the Elavon Gateway API as specified in the Fusebox Integration Guide. The section covers both Financial Messages and Non-Financial Messages (Tran Type 36). For additional information on Financial Messages, see the Fusebox industry guides (available via the above link).
- Message samples do not include control characters. See under Message and Communications Protocols for details.
- Message samples in this chapter do not include EMV fields. See EMV for details.
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 API 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.)
If a transaction refers back to a previous transaction (e.g. Void, Prior Auth), the request for the later transaction follows the Fusebox Integration Guide, including the rules for POS Data Code given under “API Reference” > “API Field 0047 - POS Data Code”.
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 messages in this document are basic samples. The POS should be able to handle any additional API fields in the response as defined in Fusebox (Elavon Gateway) documentation, including fields defined in the Fusebox Integration Guide under “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.
Simplify supports IVU (tax) fields (API 0070 through 0086). These fields are treated as pass-through. (Currently supported for Puerto Rico only.)
Simplify supports Cash tender (API 0115 = 085) for Transaction Types 02, 09, 11, 17, 61. Messages with this tender type are treated as pass-through. (Currently supported for Puerto Rico only.)
Simplify supports PINless Debit. If enabled and a Debit AID Sale or Auth transaction does not exceed a configured maximum amount, a PINless eligibility request will be sent to the host. If the host approves eligibility, the transaction will use PINless Debit. API 1021 in the financial response contains the result (Y/N) from the eligibility response.
The time remaining till a PCI reboot (in seconds) is sent in all financial response messages (API 5001 Tag 400). If the time is less than 5 minutes, the transaction will be declined with a communications error.
Simplify supports Surcharge on Sale or Auth credit transactions. Contact your Elavon representative for Surcharge requirements.
Simplify supports reading QR codes for airline vouchers on Sale and Auth transactions.