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.

## Financial and non-financial messages

Message types sent between Simplify and the POS. can be classified as either financial or non-financial based on whether or not the message type has a financial impact. For most non-financial message types, the Transaction Type (Tran Type) sent in API 0001 = 36. These will be referred to as Non-Financial messages and are covered in the next section of this guide.

This section mostly covers financial messages sent between the POS and Simplify. To simplify the organization of this guide, non-financial messages other than Tran Type 36 are also covered here. This allows all EBT messages including inquiries to be grouped together, and likewise for all Gift Card messages.  Other non-financial messages discussed in this chapter are inquiry, DCC Inquiry, Token Request, Health, Cancel, Batch Close, Batch Inquiry.

Financial messages are normally processed online by means of a message exchange between Fusebox and Simplify. Some non-financial messages are also processed via Fusebox (e.g. Inquiry, Batch Close). Other non-financial message types are not sent to Fusebox (e.g. Cancel, Health and most Non-Financial messages). For additional information on message types sent to Fusebox, see the *Fusebox Integration Guide* under Transaction Types. 

All messages follow the Elavon Gateway (Fusebox) API where applicable. For a complete list of Gateway API fields, see the *Fusebox Integration Guide* :magic-link[API reference]{id="/products/fusebox/v1/api-reference"}.

## 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 API 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.	For API 0047, see the *Fusebox Integration Guide* :magic-link[POS data code]{id="/products/fusebox/v1/pos-data-code-md"}, including the rules for transaction requests that refer back to a previous transaction (e.g. Void, Prior Auth).

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 sample messages in this document are basic samples. The POS should be able to handle any additional API fields in the response as defined under Fusebox 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 Field 5071 in all financial requests, using the value that reflects the actual transaction environment.  See :magic-link[Simplify-Controlled Field Definitions]{id="simplify-controlled-field-definitions"}.

11.	The value in field 0007 (Transaction ID / Reference ID) is incremented by the POS for each new transaction.
 
12.	Simplify supports IVU (tax) fields (API 0070 through 0086).  These fields are treated as pass-through. (Currently supported for Puerto Rico only.)  

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

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

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

16. Simplify supports Surcharge on Sale or Auth credit transactions. Contact your Elavon representative for Surcharge requirements.

17. Simplify supports reading QR codes for Airline Vouchers. See :magic-link[Sale Message]{id="sale-message"} for details. Contact your Elavon representative for supported Transaction Types

## Note on Message Samples

Message samples given under Message Details do not include:

- Control characters. See further :magic-link[Message and Communications Protocols]{id="message-and-communications-protocols"}. 

- EMV fields. See further in :magic-link[EMV Tags and Other EMV-Related Fields]{id="emv-tags-and-other-emv-related-response-fields"} .

- Offline processing. Offline transactions can be processed by On-Device SAF (Simplify performs SAF) or POS SAF (Simplify provides support for SAF performed by the POS). 

.

Overview and Guidelines

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

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

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