Simplify Introduction

On this page:

Simplify is Elavon’s PIN Pad-based application designed to process electronic payment transactions received from a Point of Sale (POS) or a Property Management System (PMS).

This document is a developer guide for customers interfacing their POS / PMS process to Simplify. It applies specifically to implementations that run Simplify on Ingenico PIN Pads using Voltage or On-Guard encryption, and send transactions to Elavon’s Fusebox host.

This document is reviewed for every application update and change to PCI P2PE requirements (at least annually) and updated as required.

See Usage for conventions used in this document.

Document Overview

This guide documents the Simplify API for POS/PMS (= POS below) developers interfacing with Ingenico devices.

Message Details
  • Financial and other messages that will be sent on by Simplify to Fusebox (the Elavon Gateway) follow the Fusebox API. Fusebox-controlled API fields are described briefly here, along with sample messages and field names; for detailed information see under Transaction Types in the Fusebox Integration Guide.

  • The start of Message Details provides generic Simplify-specific guidelines for handling financial messages.

  • Specific messages not sent on to Fusebox are described fully under Non-Financial Messages and its subsections, including detailed usage and message format as well as sample messages and field names.

Note concerning message samples given under Message Details:

  • Samples are for online transactions. Offline transactions are covered under POS SAF Processing (Simplify support for SAF performed by the POS) and On-Device SAF (SAF performed by Simplify).

  • Samples do not include EMV fields; see under EMV in this document and under EMV in the Fusebox Integration Guide for more information.

Additional messages, API fields and supported field values are documented in the following places:

Supported Hardware

Attended Devices


Simplify is supported for Version 25 and above on the following Tetra PIN Pads:

  • Lane 3000
  • Lane 5000
  • Lane 7000
  • Lane 8000
  • Link 2500
  • Move 5000


Simplify is currently available through Version 25 on the following Telium PIN Pads:

  • iPP320
  • iPP350
  • iSC250 and iSC250 Touch
  • iSC480 and iSC480 Touch
  • iSMP4
  • iWL252 (through build 88)
  • iWL258 (through build 88)

Unattended Devices

Simplify is currently available for Version 29 on the following Tetra Unattended device:

  • Self 4000

General Guidelines

POS development for Simplify should be based on the following set of principles:

  1. PCI DSS Compliance: The customer is responsible for securely deleting the encrypted account data and making it unrecoverable after authorization using a method that supports PCI DSS secure delete standards (PCI DSS 3.0 Requirement 3.2).

  2. The POS process should discard any message that does not correspond with the POS state.

  3. The POS process should compare the Transaction ID / Reference Number (field 7) in the request and response. If the response doesn’t match the request, the message should be discarded.

  4. If multiple POS workstations can be associated with a single PIN Pad, Simplify assumes that the POS process ensures there is only one outstanding transaction per PIN Pad. (This situation can occur under TCP/IP.)

  5. Simplify can return encrypted account data to allow Stand-in processing by the POS. See POS SAF Processing for more information.

  6. For support purposes, Elavon strongly recommends that the POS logs all messages received from and sent to Simplify.

  7. API fields in messages sent to the POS will not necessarily appear in order by field number. E.g. the following sequence of fields is possible:

    API Field #, ValueDescription
    0001,36Transaction Type
    5001,010003888Non-Financial Data
    0011,14123010000?V102.18B01803User Data
  8. For API fields that are defined as variable length, the POS must be able to handle data of varying lengths.

  9. Elavon uses HEM/IngEstate for terminal maintenance and updates. Any issue with HEM/IngEstate connectivity will require shipping back the terminal for updates. Elavon recommends testing the connection to HEM/IngEstate during pilot.

  10. Elavon uses Inquiry and Voids to recover from communication issues on Financial Messages. Please pay close attention when implementing Inquiry and Void logic.

  11. Fields 13 (date) and 14 (time) are required in all financial requests. Time must be sent in military (24 hour) format.

  12. To protect against EMV cards being left in the Simplify device, Simplify will not accept any message from the POS until the card is removed. An error message will be returned indicating that the card is still inserted.

  13. If no response is received for a financial request, or if you need to start over for any reason, the POS should send a Cancel before sending another financial request.

  14. The POS can activate Mifare tap by sending a request to Simplify with “M” or “m” in API 0003. For valid tap, Simplify will extract the UID, and send it to the POS in the response as token 300 in Field 5001 (no Fusebox message). See sample under Sale Message.

  15. API 5001 contains data in TLV (Tag-Length-Value) format. The data (Value) is preceded by a 3-digit Tag (Token) identifying the data type and a 3-digit Length field defining the number of bytes of data. Multiple tags are concatenated with no delimiter.