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.

These are cookies that support site functionality that is visible or advantageous to you or your experience of the site, they enable websites to remember choices and provide a more personalized experience.   Functional cookies help to provide services that you request, such as language preference or layout.

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

U.S. Bank Europe DAC. Registered in Ireland – Number 418442..  Registered Office: Block F1, Cherrywood Business Park, Dublin 18, D18 W2X7, Ireland.
U.S. Bank Europe DAC, trading as Elavon Merchant Services, is regulated by the Central Bank of Ireland.
 
U.S. Bank Europe 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.
U.S. Bank Europe 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.

Most popular solutions

Additional solutions

Fusebox integration & options

Optional platform features

Documentation

North America

Europe

Regions

Simplify can be configured to support SAF (Store and Forward) processing for timed-out (offline) transactions. Depending on configuration, SAF processing will be performed by either the POS or Simplify:

- POS SAF – Simplify sends a response that allows the transaction to be locally approved or declined by the POS (Stand-in process). If approved, the POS forwards (i.e. resubmits) the transaction (through Simplify or directly to Fusebox) for host approval. Described below.

- On-Device SAF (version 28 and above) – Simplify performs Stand-in and other SAF processing. See :magic-link[On-Device SAF]{id="/products/simplify/v1/stand-in-and-online-response-differences"} .

A transaction is considered to have timed out when either of the following occurs: 

- The Fusebox response indicates that the Fusebox request to the authorizer timed out.

- Simplify times out before receiving a Fusebox response. 

:::::notice{note}

The Simplify timeout interval for a request to Fusebox is defined individually for each request from the POS in the first 3 bytes of Field 11.
:::::

:::::notice{important}

PCI DSS Compliance: For POS SAF only, the response for a timed out transaction contains encrypted customer data. The customer is responsible for making this data unrecoverable after completion of the authorization process (PCI DSS 3.0 Requirement 3.2).
:::::

For timed-out EMV transactions, Simplify can be configured to return EMV tags in the response. The POS can include these tags in the resubmitted transaction. Resubmission of EMV Stand-In transactions without EMV tags can cause declines from some issuers. See the *Fusebox Integration Guide* :magic-link[EMV API Fields]{id="/products/fusebox/v1/emv-api-fields"} for more information on EMV tags. 

SAF support is configured independently for each tender type and applies to the following transaction types:

- Sale
- Auth
- Refund

If Simplify times out waiting for a Fusebox response to one of these three financial transaction types, the outcome at the POS process will depend on whether SAF is enabled. 

- **For SAF Enabled** - Simplify can be configured to validate transactions for SAF eligibility.
 - If not eligible, the transaction will be declined with a communications error (same as SAF not enabled).
 - If SAF is enabled and the transaction passes validation (if enabled), the POS process will receive a Stand-in response (Field 1010 = “\*SLR STAND-IN.”) containing encrypted account data. This data allows the POS to resubmit locally approved transactions for host approval.
 
 “\*SLR STAND-IN.” is also returned when *Simplify* performs Stand-in on a transaction (On-Device SAF). However for On-Device SAF, *no PCI-sensitive data is returned.*

- **For Stand-in Not Enabled** - If Stand-in/SAF is not enabled, Simplify will decline the transaction with a communications error (Field 1010 contains "\*SLR COMMUNICATIONS ERROR." or "\*SLR SWITCH TIMEOUT.").

In either case, :magic-link[Inquiry Message]{id="inquiry-message"} processing must be performed.

## Stand-In and Online Response Differences

The main differences between a **Stand-in Response** and an **Online Response** occur in the following fields:

| Field \# | Field Name | Usage|
|------------|----------------------------|------|
| 3 | Account Data | <ul><li>**Online** - Token for the account number (from the Fusebox response)</li><li>**Stand-in** - If a token is used for authorization, the token is returned. Otherwise, this field contains the encrypted version of the account number.</li></ul>|
| 4 | Expiration Date | <ul><li>**Stand-in** - If the card was keyed, contains encrypted Expiration Date.</li></ul>|
| 6 | Authorization Code | <ul><li>**Online** - Approval code returned by Fusebox.</li><li>**Stand-in** - "SN:" followed by the Serial Number of the PIN Pad.</li></ul>|
| 1003 | Gateway Response Code | <ul><li>**Stand-in** - “0000”</li></ul>|
| 1010 | Gateway Response Message | <ul><li>**Stand-in** - “\*SLR STAND-IN.”</li></ul>|
| 1379 | EMV Receipt Field List | EMV Receipt data available for printing.<ul><li>**Online** - From Fusebox, for use on declines (see the *Fusebox Integration Guide* :magic-link[EMV Receipts]{id="/products/fusebox/v1/emv-receipts"} for more information).</li><li>**Stand-in** - From Simplify (same format as online).</li></ul>|

:::::notice{note}

A value of "\*SLR STAND-IN." in field 1010 *does not mean that Simplify has performed stand-in*; it indicates that Simplify did not receive a Host Response before timing out. The POS performs Stand-in by deciding whether or not to approve the transaction locally.
:::::

Offline Transaction Processing

Alliance Offers

Data as a Service

Invitation to Apply

Accounts

Bank Holidays

Card Activation

Card Controls

Challenge-Widget

Commercial Credit Cards

Commercial Statements

Credit Card Account Details

Credit Card Accounts Overview

Credit Card Alerts

Credit Card Application Status

Credit Card APRs

Credit Card Balance Transfers

Credit Card Disputes

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

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

Card as a Service API

Core Banking API

Money Movement API

Reference API

Access Online Transactions

Account Transfers

Account Validation

ACH Originations

Bank Information

Card as a Service

Check Payables

Corporate Account Information

Corporate Account Information 3LO

Corporate Credit Cards

Corporate Onboarding

Corporate Statements

Custody

Data Toolbox

Data Toolbox - Accounts

Data Toolbox - Documents

Data Toolbox - Transactions

Debit Card Phone Number Lookup

Disbursements via Zelle®

U.S. Bank Flexible Capital Platform

Freight Payment Customer Profiles

Freight Payment Transactions

Incoming Webhooks

Instant Payments

Investment Accounting

PaySmart

Payee Choice

Payee Token+

Personal Loans

Positive Pay

Push to Card

Receivables

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. 25-31

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

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

Print Receipt Request and Response (Tran Type 39-06)

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