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:

  1. If account data is sent in Field 3 of the POS request, the Tender Type is required in Field 115 (Transaction Qualifier).

  2. If the POS wants Simplify to prompt for Manual Entry, send ‘K’ in Field 3.

  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.)

  4. 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".

  5. Fields 13 (date) and 14 (time) are required in all financial requests.

  6. 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.

  7. 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".

  8. If a Void Request needs to be re-sent, it should be sent without modification until a Host Response is received.

  9. 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.

  10. Elavon recommends sending API 5071 in all financial requests, using the value that reflects the actual transaction environment. See under Field 5071 (Card/Cardholder Present?) .

  11. The value in field 0007 (Transaction ID / Reference ID) is incremented by the POS for each new transaction.