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.

Simplify supports an **Informational Prompt Message**. This is a flexible feature designed to allow merchants to display information for customers and get customer input using a variety of screen layouts. This message type does not affect the processing of financial transactions.

Availability of Informational Prompting functionality by device is as follows:

:::::notice{note}

 Maximum label length depends on font size. Maximum lengths shown below are for medium font size.
:::::


|Device	|Supported Messages	|Maximum Label Length	|
|-------|------------------|------|
|iPP320	|Tag 010 only|22	|
|iPP350	|Tag 010 only *|43	|
|iSC250	|All Tags except 031|52 | 
|iSC480	|All Tags except 031|62 | 
|iSMP4	|Tag 010 only|32 |
|Link 2500	|Tags 010, 031 only|22	|
|Lane 3000	|Tag 010, 031 only|29	|
|Lane 5000	|All Tags |35	| 
|Lane 7000	|All Tags |35	| 
|Lane 8000	|All Tags |35 | 
|Move 5000	|Tags 010, 030, 031 only **|22	|

\* Only supports one (lower) row of buttons.

** Non-P@TT Devices Only.

The POS controls this process by sending an **Informational Prompt Request** that defines the screen to be displayed. The PIN Pad must be in a Closed state to process this request. Exceptions: (1) If another **Informational Prompt Request** is sent when the PIN Pad is already displaying an Informational Prompt screen, the display for the second request will replace the first screen. (2) After sending an **Informational Prompt Response**, the PIN Pad will display a wait screen for a configurable interval before going to the Closed state. If a new **Informational Prompt Request** is sent during this interval, the PIN Pad will process the request.

Simplify returns the customer input in the **Informational Prompt Response**. Input includes the action button (virtual button) or hard key pressed. Depending on the type of **Informational Prompt Message** sent, input may also include entered text or a selected radio button, check boxes or slider position. Additional requests can be sent if further customer interaction is required.

:::::notice{important}

 For P2PE Systems: Informational Prompt messages *must not pass card data*. Doing so will defeat the purpose of P2PE, and result in increased need for PCI auditing.
:::::


## **Generic Non-Financial Message Format**

The **Informational Prompt Message** is a **Non-Financial** message type (Transaction Type 36) with a Message Type of 14. It is discussed separately in this section due to its many uses.

As described under "Message Details" in :magic-link[Non-Financial Messages]{id="non-financial-messages"}, all **Non-Financial** messages have the following generic format:

| API Field \# | Description |
|-----------------------|----------------------------------------------------------------------------------------------------------------------------------|
| 0001 | Transaction Type 36. Non-Financial message |
| 0011 | User Data. See :magic-link[Simplify-Controlled Field Definitions]{id="simplify-controlled-field-definitions"}. For Transaction Type 36, it will always include:<ul><li>Positions 1-2 Message Type</li></ul>|
| 5001 | Non-Financial Data. The format of this field depends on the value of Message Type. |

## **API 0011 and 5001 in Informational Prompt Messages** 

The remainder of this page provides information on API 0011 and 5001 specific to the **Informational Prompt Message**.

### **API 0011**

The format of API 0011 in the **Informational Prompt Message** (36-14) is modeled on that in the **Signature Request** and **Response Messages** (36-01, 36-02). Exception: the **Screen ID** subfield of API 0011 is not used. As shown in the following table, the Response echoes the Request except for the Timeout Value, which is replaced with the Completion Code, and VersionBuildInfo (response only).

| API 0011 Subfield | Length | Description |
|----------------------------------|----------|------------------------------------------------------------------------------------|
| Message Type | 2 | Always 14 |
| Sequence Number | 3 | Transaction identifier |
| Screen ID | 3 | Not used |
| Timeout Value/ Completion Code | 3 | <ul><li>Request: Screen timeout in seconds (000=No timeout)</li><li>Response: Completion Code (000 = Success)</li><li>See further :magic-link[Simplify-Controlled Field Definitions]{id="simplify-controlled-field-definitions"}.</li></ul>|
| VersionBuildInfo | Var | Response only: ‘?’ followed by Version and Build numbers |

### **API 5001**

In the **Informational Prompt Message**, API 5001 is used in the Request to define the screen that will be displayed and in the Response to return customer action/data entered. The generic structure of API 5001 is TTTLLLVVV..VV, broken down as follows:

| API 5001 Subfield | Length | Description |
|--------------|----------|-------------------------------------------------------------------------------------------------------------|
| TTT | 3 | Tag identifying screen to be displayed:<ul><li>010=Text with optional buttons</li><li>011: Static and Scrolling Text with Optional Buttons</li><li>012: Text and Graphics with Optional Buttons</li><li>013=Fast Graphics Download</li><li>020=Scrolling Text</li><li>030=Virtual Keyboard</li><li>031=Tactile Keypad</li><li>040=Radio Buttons</li><li>050=Check Boxes</li><li>060=Slider </li><li>070=Scrolling Text with Radio Buttons</li><li>071=Scrolling Text with Virtual Buttons</li><li>072=Scrolling Text with Configurable Buttons </li></ul>|
| LLL | 3 | Length of data (VVV…VV) Note that if the data is longer than 999 bytes, set LLL to 999. The application will process the additional data. |
| VVV…VV | var | Data |

The following pages provide detailed breakdowns of API 5001 and sample messages for each supported value of Tag.

Informational Prompting

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

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

Ingenico Download Configuration and Troubleshooting Guide 2.03.02x.121 Ver. 21-30