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

These cookies and similar technologies gather information about your browsing habits. They remember that you've visited a website and share this information with other organisations, such as advertisers and platforms on which we advertise.
They do this in order to provide you with ads that are more relevant to you and your interests. Although these cookies and similar technologies can track your visits to other websites, they don't usually know who you are.
Without these cookies, online advertisements you encounter will be less relevant to you and your interests.


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.

## Message summary

All messages sent and received by the Simplify Pay@Table process have 39 as the Transaction Type (field 1) and use a Message Type (field 5100) to define the purpose of the message.

Simplify Pay@Table messages are organized much like Non-financial messages, which all have 36 as the Transaction Type (field 1) and use a Message Type (field 11 bytes 1-2) to define the purpose of the message.

Note: Messages sent and received by the Simplify Pay@Table process are referred to as Simplify Pay@Table messages.

The message sequence used during a Simplify Pay@Table transaction is as follows:

| | Pay@Table Message Type|Use	|Direction|
|---------|-----|-----|-----|
|Simplify Pay@Table Process (pre-pay)	|01	|Login Request/Response 	|Request from Simplify to POS Response from POS to Simplify|
|(continued) |02	|Get Check Info Request/Response (may be omitted)	|Request from Simplify to POS Response from POS to Simplify|
|(continued)|07|Check Detail Request/Response|Request from Simplify to POS Response from POS to Simplify|
|(continued)|05	|Make Payment Request/Response (response on decline only)	|Request from Simplify to POS Response from POS to Simplify|
|Simplify Payment Process	|N/A	|<ul><li>Receive financial request from POS</li><li>Obtain account data</li><li>Perform host messaging</li><li>Send financial response to POS.</li></ul>|Note: No Pay@Table-specific processing.| 
|Simplify Pay@Table Process (post-pay)	|06	|Print Receipt Request/Response	|Request from POS to Simplify Response from Simplify to POS|
|(continued) |04	|Logout/Disconnect Request/Response 	|Request from Simplify to POS Response from POS to Simplify|

The following pages provide information on Pay at Table (39-xx) message types, as follows:
- The role of the message type in the Pay at Table transaction flow is described. 
- The message format is defined, and illustrated with one or more sample messages.

The remainder of this page illustrates how these message types work together to process Pay at Table transactions.

## Message flow

Note: The following flow assumes that check data was not returned in the **Login Response**. If check data is present in this response (in fields 5114 up to 5212), the **Get Check Information Message** will not be used. Simplify will instead proceed directly to processing the returned check(s).

:::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/simplify/Patt1.png" alt="Pay at table pre-pay flow" max-width="" max-height=""}
::: 

:::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/simplify/Patt2.png" alt="Pay at table payment process flow" max-width="" max-height=""}
::: 

The flow in the above graphics can also be represented as follows: 

- **Pay@Table Process (pre-pay)**
 - Simplify sends Login Request to POS.
 - POS validates user, opens connection, and returns configuration data to Simplify in Login Response.
 - Server enters Table and/or Check number (depends on configuration).
 - Simplify sends entered data to POS in Get Check Information Request. 
 - POS returns check data for table or single check (depends on data received) to Simplify in Get Check Info Response.
 - Server Selects check (if > 1 returned), gets base tender amount (if partial pay enabled), and gets Tip (if enabled). Customer confirms amount.
 - Simplify sends transaction data to POS in Make Payment Request.

- **Payment Process** 
 - POS builds and sends financial request to Simplify.
 - Simplify obtains account data (including PIN if debit), and builds and sends request to Fusebox.
 - Fusebox obtains payment authorization from host (authorizer) and sends response to Simplify.
 - Simplify builds and sends financial response to POS. 
 - POS processes financial response (or goes to timeout processing; see details just below).

- **Payment Process for Timeout on Financial Request**
 (now or on back channel)
 - If no financial response or host timeout, POS sends Inquiry Request to Simplify, which sends request to Fusebox. Fusebox sends Inquiry Request to host.
 - Fusebox sends Inquiry Response to Simplify, which sends response to POS.
 - If POS times out or no host response, POS resends Inquiry Request or performs Stand-in processing.
 - If void needed, POS sends Void Request to Simplify, which sends to Fusebox. Fusebox obtains void authorization from host and sends Void Response to Simplify, which sends to POS. POS processes void.

- **Simplify Pay@Table Process (post-pay)** 
 - When done handling Simplify payment processing, POS sends receipt data to Simplify in Print Receipt Request.
 - Simplify prints receipts and sends Print Receipt Response to POS. 
 - Simplify sends Logout/Disconnect Request to POS to request logout/disconnect.
 - POS sends Logout/Disconnect Response, logs user out, and closes connection.

Message Summary and Flow

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

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

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