Elavon downloads and stores cookies on your device when you visit our website. We use these cookies to better understand and improve your browsing experience by identifying most visited pages, personalising content, and measuring site performance.

Essential cookies enable core functionality such as page navigation and access to secure areas. The website cannot function properly without these cookies; they can only be disabled by changing your browser preferences.

Performance cookies help us to improve our website by collecting and reporting information on its usage (for example, which of our pages are most frequently visited).

Cookie Settings

Elavon Financial Services DAC. Registered in Ireland – Number 418442.
Registered Office: Block F1, Cherrywood Business Park, Dublin 18, D18 W2X7, Ireland.
Elavon Financial Services DAC, trading as Elavon Merchant Services, is regulated by the Central Bank of Ireland.
 
Elavon Financial Services DAC. Registered in Ireland with Companies Registration Office. The liability of the member is limited. United Kingdom branch registered in England and Wales under the number BR022122.
Elavon Financial Services DAC, trading as Elavon Merchant Services, is a credit institution authorised and regulated by the Central Bank of Ireland.  Authorised by the Prudential Regulation Authority.  Subject to regulation by the Financial Conduct Authority and limited regulation by the Prudential Regulation Authority.  Details about the extent of our regulation by the Prudential Regulation Authority are available from us on request.

HEM and IngEstate are Ingenico Terminal Management Systems. Elavon maintains an HEM/IngEstate server to update Simplify PIN pads. This section explains how PIN Pads are maintained.

## Signed Sensitive Files

For purposes of security, sensitive Simplify files are signed. Unsigned sensitive files, or files signed with a different certificate, will not be accepted by the PIN Pad. If this occurs, a signing error message will be displayed after the file is loaded to the PIN Pad. The merchant will then need to contact Elavon.

## Initiating HEM/IngEstate

HEM and IngEstate are Ingenico PIN Pad management systems. Simplify is currently transitioning from the use of IngEstate to HEM.

The HEM/IngEstate update process can be initiated manually on the PIN Pad, by command from the POS (see the *Ingenico Simplify Developer Guide* under :magic-link[Initiate HEM/IngEstate Message]{id="initiate-hem-or-ingestate-message-tran-type-3607"} for details), or scheduled by Elavon. Once initiated, the process proceeds automatically. When the update process is complete, the PIN Pad will reboot.

The HEM/IngEstate update process can be initiated manually from the **Elavon Sub Menu**. As described under :magic-link[Accessing the Elavon Main Menu]{id="c3s1-accessing-the-elavon-main-menu"}, this menu can be accessed during the PIN pad boot up sequence. (See :magic-link[Navigation and Data Entry on Ingenico PIN Pads]{id="navigation-and-data-entry"} for device-specific details.)


::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/simplify/image35.jpeg" alt="Elavon Sub Menu"}


Select **Initiate HEM/IngEstate** from the Elavon Sub Menu to initiate the HEM/IngEstate update process.

## Viewing Simplify Load Information (0 Screen)

Information on the Simplify load present in the PIN pad is displayed during boot up and by keying 0 when the PIN pad is in a closed state. (To lengthen the display, press the + or -- key.) For additional fields, scroll down. This information may be requested by Elavon for troubleshooting purposes. The PIN pad will return to the usual closed screen after several seconds.

### Sample Field Values

The fields on this screen will vary by implementation. The following list contains a sample of the available fields:
- Serial: 07225277
- TMS ID: 88802013
- Version: N-OG-2.03.12821 - 2812
- SREV: 20
- Package: 2.28.28
- IP Eth: xxx.xxx.x.44
- Merchant: Test01
- Comm Option: Use Others
- POS-SIM: TCPIP - Non-SSL – 6000 
- SIM-Host: TCPIP
- SIM-HEM: TCPIP
- Comm: (ETH Wifi BT capable)
- 01/05/22 - 11:22:50
- Release: 2.03.028.121
- EMVCert: 2.26
- EmvKernel: 0901
- ParmVer: 2.28.2
- TndrVer: 2.28.2
- EMVParm: EMVPARM-E4-2-->
- CAKeys: QA-1.0
- ClessParm: CLESSEMV-E4-1-V2.3
- TSA Serial: DENVER03757500
- SDK Ver: 11.20.2.PatchG(b45)
- RKI:
- Device: Lane 5000 PCIv4 PCIv5
- memTMSID: 88802013
- Flash Memory: 503332
- Flash Free Code: 386555
- Flash Free Data: 386555
- RAM Memory: 518270
- RAM Memory Free: 410492
- PosIP Acpt Active
- CurrIP: xxx.xxx.x.226
- Graphic Prof:
- Tracing: ON

### Field Descriptions

The above fields provide the following information:

| Field |Description |
|---------|---------|
|Serial: |Device L3 Serial Number|
|TMS ID: |TMS Identifier|
|Version: |Simplify load level information in two parts:<ul><li>Official PCI solution/version/build designation</li><li>User-friendly version/build information.</li></ul>Format is S–PP-X.YY.AAAAA-AAAAA, where:<ul><li>S = first part of prefix, indicates whether Simplify is operating as part of a PCI P2PE-validated solution. (V = validated or N = non-validated). **Note:** This value depends on additional software used in the solution (besides Simplify). Specifically, this value indicates whether the most recent transaction processed by Fusebox came back validated or not.</li><li>PP = second part of prefix, indicates encryption type. (OG = On-Guard or G2 = Voltage)</li><li>X.YY.AAAAA = Official Simplify version and build information **Note:** For purposes of documenting Simplify PCI P2PE compliance, PCI is not concerned with the version/build (AAAAA). The designation currently used to document that Simplify is operating as part of a validated solution is V-OG-2.03.AAAAA.</li><li>AAAAA – User-friendly version and build information:<ul><li>AA = Simplify “Version”</li><li>AAA = build</li></ul>E.g. 28121 = “Version 28” build 121.</li></ul>For more information, see the *Simplify Ingenico Developer Guide* under :magic-link[Versioning]{id="versioning"}.|
|SREV: |Sublevel of build|
|Package: |ID of package used to build current load|
|IP Eth: |Partially masked IP address of PIN Pad **|
|Merchant: |Customer for whom load was built|
|Comm Option:	|Indicates whether or not Bluetooth to Base is used for POS communications| 
|POS-SIM:	|Communications type and port used between Simplify and POS |
|SIM-Host: 	|Communications type used between Simplify and host|
|SIM-HEM:	|Communications type used between Simplify and HEM|
|Comm:	|Communication capabilities|
|(Date/Time)|Current date/time|
|Release: |ID of base code tied to the current release. For more information, see the *Simplify Ingenico Developer Guide* under :magic-link[Versioning]{id="versioning"}.|
|EMVCert: |EMV version|
|EmvKernel:|EMV Kernel version|
|ParmVer: |parm version|
|TndrVer: |tenderdef version|
|EMVParm: |EMVParm version|
|CAKeys: |EMV Keys version|
|ClessParm:|ClessEMV (or ClessMSD) version|
|TSA Serial:|Device L4 Serial Number |
|SDK Ver: | SDK version |
|RKI:|Status of last Remote Key Injection file download|
|Device:|PIN Pad model(s). Includes PCI v3, v4 and/or v5.|
|memTMSID:	|default TMSID |
|Flash Memory:|Total Flash memory in PIN Pad |
|Flash Free Code:|Unused Flash code space|
|Flash Free Data:|Unused Flash data space|
|RAM Memory: |Total RAM memory in PIN Pad|
|RAM Memory Free:|Unused RAM memory|
|PosIP Acpt |Status of Simplify-POS IP connection |
|CurrIP:	|Partially masked IP address of POS connected to PIN Pad|
|Graphic Prof:	|Graphics Profile active in PIN Pad|
|Tracing ON	|Debug logging (ON/OFF)|

:::::notice{note }

** **IP Eth**: initially displays the partially masked IP Address of the PIN Pad (as shown above). An optional feature is available allowing this field to display the unmasked address. If this feature is present, pressing Enter at the load information screen will display a login screen. After logging in on this screen (special password required), the load information screen will be redisplayed with the IP Address unmasked. Please contact your Elavon representative if you want to implement this feature. 
:::::


## Remote Key Injection

Simplify supports Remote Key Injection (RKI). This section documents how to determine the outcome of an attempted key injection. For more information on RKI, consult your Elavon representative.

When the PIN Pad restarts after an attempted key injection, RKI messages will be displayed during the bootup sequence. The first RKI message will always be as follows:

::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/simplify/image60.png" alt="RKI Processing screen" max-width="" max-height=""}

This message will be followed by a second RKI message indicating the outcome of the attempted injection. There are three possible scenarios:
- If the RKI file downloaded to the PIN Pad is invalid, the following error message will be displayed:
 
::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/simplify/image63.png" alt="Load Error 205 IPPK0 screen"}

- If the RKI file is valid, but the serial number in the file does not match that in the PIN Pad, an error message will be displayed showing the L4 serial number of the PIN Pad. E.g.: 
 
::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/simplify/image62.png" alt="No RKI Maintenance Found screen with Device Serial Number"}

- If the key injection is successful, the following message will be displayed: 
 
::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/simplify/success.png" alt="Successful Load IPPK0 screen"}

 
## Exiting Reversal Mode

The host approval will need to be reversed when either of the following situations occur:
- An EMV transaction is approved by the host and declined by the chip.
- The customer removes their card from the chip reader before the transaction is completed.

If a reversal is needed, Simplify will go into reversal mode to force the reversal. It does this by sending a reversal (Tran Type 11) to the host, and resending the reversal (if necessary), until a response is received. While this is taking place, any other transactions that are
sent to the PIN pad will be processed offline.

The PIN pad can be rebooted and commanded to exit reversal mode from the **Elavon Main Menu**, as follows:

1. Reboot the PIN pad. When a rectangle appears in the lower right corner of the screen, press the **Enter** (green) key to display the **ELAVON SUB MENU**.

2. Select **Elavon Main Menu** and login to display this menu.

3. Scroll down and select **REMOVE EMV REVERSAL** (only present if currently in reversal mode).

4. Select **RESTART** to reboot the PIN pad.

If Simplify is forced out of reversal mode, the data required to request the reversal is sent to the POS in a **Void Sale Response** (11) message, after which the PIN pad returns to normal processing mode.

:::::notice{important } 
Forcing Simplify to exit reversal mode is an exception procedure that should only be used when necessary. If Simplify is forced out of reversal mode, the merchant will be responsible for ensuring that the transaction is reversed by the host, using the data in the **Void Transaction Response**. Elavon strongly recommends allowing Simplify to reverse all host-approved transactions that are declined by the chip.
:::::

## TLS 1.2 Cipher Groups

The following TLS 1.2 cipher groups (suites) are supported for Simplify build 121:

- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)
- TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028)
- TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024)
- TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d)
- TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d)
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)
- TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027)
- TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023)
- TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c)
- TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c)
- TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff)

Terminal Maintenance

Alliance Offers

Data as a Service

Invitation to Apply

Accounts

Bank Holidays

Card Activation

Card Controls

Commercial Credit Cards

Credit Card Account Details

Credit Card Accounts Overview

Credit Card Alerts

Credit Card Application Status

Credit Card APRs

Credit Card Disputes - Coming Soon

Credit Card Payments

Credit Card Qualified Offers

Credit Card Statements

Credit Card Transactions

Data Sharing for Marketing Purposes

Digital Wallets

Make a Payment - Coming Soon

Rewards Accelerator

Rewards Automatic Redemption

Rewards: Balance Summary

Rewards Redemption - Coming Soon

Rewards Redemption Accounts

Rewards Redemptions

Rewards Transactions Earned and Redeemed

Travel Notifications

User Profile

3DSecure2

Avvance

CheckoutJs

Commerce SDK

Converge

Disputes Management

Dynamic Currency Conversion

eBoarding

Elavon Cloud Payments Interface

Elavon Payment Gateway

Fusebox

Hosted Payment Page

In Person Payments on Opayo

Leads

Lightbox payment modal

Online Payments on Opayo

Opayo

Opayo Direct

Opayo Forms

Opayo Reporting API

Opayo Server

Opayo Shared API

Payment Method Gateway

Payments Core 365

Simplify

viaconex

XML API

Access Online Transactions

Account Transfers

Account Validation

ACH Originations

Bank Information

Card as a Service

Card as a Service API

Check Payables

Core Banking API

Corporate Account Information

Corporate Credit Cards

Corporate Onboarding

Corporate Statements

Custody

Data Toolbox

Data Toolbox - Accounts

Data Toolbox - Documents

Data Toolbox - Transactions

Disbursements via Zelle®

U.S. Bank Flexible Capital Platform

Freight Payment Customer Profiles

Freight Payment Transactions

Instant Payments

Investment Accounting

Money Movement API

PaySmart

Payee Choice

Payee Token+

Personal Loans

Positive Pay

Push to Card

Receivables

Reference API

RTP® - Real-Time Payments

Tokenized Payments

Treasury Builder

U.S. Bank FBO Account

Virtual Account Reporting

Virtual Card Payments

Voyager Accounts

Voyager Cards

Voyager Drivers

Voyager Transactions

Voyager Vehicles

Wire Transfers

Simplify Overview

Ingenico Developer Guide 2.03.02x.121 Ver. 21-30

Simplify Introduction

Supported Hardware

General Guidelines

Message and Communications Protocols

Versioning

Financial Messages

Overview and Guidelines

Sale Message (Tran Type 02)

Auth Only Message (Tran Type 01)

Prior Auth Sale Message (Tran Type 07)

Incremental Authorization Message (Tran Type 75)

Full Authorization Reversal Message (Tran Type 61)

Partial Authorization Reversal Message (Tran Type 76)

Return Message (Tran Type 09)

Void Return Message (Tran Type 17)

Void Sale Message (Tran Type 11)

EBT Messages (Tran Types 02, 09, 11, 17, 24)

Gift Card Messages (Tran Types 01, 02, 07, 09, 11, 17, 24)

Inquiry Message (Tran Type 22)

 DCC Inquiry Message (Tran Type 46)

Token Request Message (Tran Type 37)

Cancel Message (Tran Type 80)

Health Message (Tran Type 73)

Batch Close Message (Tran Type 13)

Batch Inquiry Message (Tran Type 14)

Non-Financial Messages

Non-Financial Messages (Tran Type 36)

Signature Message (Tran Types 36-01, 36-02)

Version Number Inquiry Message (Tran Type 36-06) 

Initiate HEM/IngEstate Message (Tran Type 36-07)

Scrolling Receipt Request Message (Tran Type 36-10)

Scrolling Receipt Stop Message (Tran Type 36-11)

Exit Reversal Mode Message (Tran Type 36-12)

Informational Prompting Message (Tran Type 36-14)

System Command Message (Tran Type 36-15)

Allow Pre-Tendering Message (Tran Type 36-40)

Print Request Message (Tran Type 36-45)

Status Message (Tran Type 36-51)

POS SAF Processing

Offline Transaction Processing

Stand-In Response

Store and Forward Transactions 

EMV Considerations

EMV Tags and other EMV-related Response Fields

EMV Offline Situations

ICC (Chip) Declines and Simplify Reversal Mode

Pay-At-Table

Transaction Flow

Pay-At-Table API Fields

Messaging

Pay-At-Table Message Overview

Login Message (Tran Type 39-01)

Get Check Info Message (Tran Type 39-02)

Controlling screen flow after check selection

Check Detail Message (Tran Type 39-07)

Make Payment Message (Tran Type 39-05)

Print Receipt Message (Tran Type 39-06)

Simplify Payment Process

Logout/Disconnect Message (Tran Type 39-04)

Recovery

Informational Prompting

General information for all tags

Generic messaging

Tag 010 - Text with Optional Buttons

Tag 011 - Static and Scrolling Text with Optional Buttons

Tag 012 - Text and Graphics with Optional Buttons

Tag 013 - Fast Graphics Download

Tag 014 - Text and Camera Image

Tag 020 - Scrolling Text 

Tag 030 - Virtual Keyboard

Tag 031 - Tactile Keypad

Tag 040 - Radio Buttons 

Tag 050 - Check Boxes

Tag 060 - Slider Message

Tag 070 - Scrolling Text with Radio Buttons

Tag 071 - Scrolling Text with Virtual Buttons

Tag 072 - Scrolling Text with Configurable Buttons

Dynamic Currency Conversion (DCC)

P2PE

Auto Signature

Pre-Tendering

Simplify-Generated Messages

On-Device SAF

Supported Functionality

On-Device SAF Transaction Lifecycle

POS Inquiry with On-Device SAF Enabled

Simplify-Generated Messages for On-Device SAF

SAF Sample Messages

Simplify-Controlled Field Definitions

Developer Guide Release Notes