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.

The following terms are used in Elavon Gateway products and are included in Fusebox and Elavon software applications.

**AC** - Application Cryptogram. Cryptogram returned by the ICC in response to the Generate AC command.

**AAC** - Application Authentication Cryptogram. The type of AC that is generated by the chip when declining a transaction.

**AID** - Application Identifier. A unique identifier that tells you the card brand (ex: Amex, Discover, MasterCard, Visa, etc.) and the type of card within the brand (ex: Maestro vs. MasterCard Credit). Identifies the application as described in [ISO/IEC 7816-5](https://www.iso.org/standard/34259.html).

**Application File Locator (AFL):** Identifies the records available to the application and the reference to their location in files in the chip card’s memory.

**Application Interchange Profile (AIP):** Indicator of the capabilities of the chip card to support specific functions.

**ARPC** - Application Response Cryptogram. Cryptogram generated by the issuer during an online transaction authorization. It secures the response data integrity and is used by the chip to validate the issuer host authenticity.

**ARQC** - Application Request Cryptogram. A type of AC that requests an online transaction. It secures the request transaction data integrity and is used by the issuer to validate the chip authenticity.

**Application Transaction Counter (ATC):** A mechanism for tracking the transactions done using a specific account; used to prevent fraudulent use or cloning of a card or device.

**Authorization Process:** Authorization approves the use of a credit card, debit card, private label card, stored value card, or electronic check (e-check). 

- Authorization code is returned to the POS system and retained by the card association, card issuer, and transaction processor. 

- No money changes hands. 

- Authorization code must accompany the transaction when settled to prevent the merchant from being charged a higher processing fee. 

- Card issuer sets cardholder spending limit. The open-to-buy is the remaining credit limit on the cardholder account. 

**BAU** - Business as Usual. Refers to normal magstripe processing flow.

**Card Authentication Method (CAM):** Method used to verify that a card or device is genuinely the one issued to the consumer.

**Card Verification Code 3 (CVC3):** Value used in place of CVC1 in the discretionary data field of the Track 1 and 2 data for MasterCard PayPass transactions; usually a dynamic cryptogram generated by the card or device.

**Contactless Chip:** The RF chip found inside a card or device; when connected to an antenna, it permits card or device transactions without swiping the magnetic stripe.

**CVM** - Cardholder Verification Method. Strongest verification method supported by both the ICC chip and the EMV Kernel’s terminal capabilities configuration.

**Elavon Gateway applications:** Elavon Gateway applications enable your application to process transactions with any transaction processor for which the Elavon Gateway has written a third party interface. The Elavon software applications provide the communication and services technology and optional high-speed Payment Delivery Services (PDS) for a one-to-many link between your POS system and the transaction processors that the Elavon Gateway supports.

- SofTrans Interface Modules and their availability can be obtained from your Elavon Gateway Relationship Manager and differ on Fusebox. Additional certification requirements may exist for some TPPs.

**Elavon Gateway:** Defines the Elavon Gateway Message or the API fields in a specific way and requires that certain data elements be included in the Input Request. The POS or PMS can be used with most credit card transaction processors supported by our TPP Processor Interface.

**Fusebox:** The Fusebox UI or Batch Management User Interface (BMUI) is an online portal that is used to review, research, and process transactions after they have been sent to the Elavon Gateway. Cardholder data is protected behind a secure data center and firewall. 

**JNetSend:** A JAVA XML parser that accepts an XML message from the integrated POS or PMS, performs message translation, and then passes transactions to JNetServ.

**Merchant Bank:** Works with various transaction processors to process electronic payment transactions on their behalf. Some merchant banks contract with several transaction processors, allowing them to offer more services to their customers. Larger banks may do their own transaction processing.

**Online Content Management (OCM):** Core product distributed by Elavon and considered the client-facing Dispute Management response tool. Acquiring merchants access [Payments Insider](https://www.mypaymentsinsider.com/ui/#/us/en_US/welcome) and use the tool to view, manage (up to 2 years of data), and respond to their chargeback and retrieval activity. 
 
**On-Guard:** A type of encryption supported on Ingenico terminals only. Simplify using On-Guard can be operated as part of a PCI P2PE-validated solution. Validation is specifically performed through Safe-T Link with P2PE Protect. 

**PayPass Card:** A proximity device containing a PayPass chip and application that has the characteristics of the transaction bankcard. The card is issued by a traditional issuer and contains a contactless chip that uses radio frequency.

**Point-to-point encryption (P2PE):** Encrypts card data at the earliest point of entry, to protect the data as it travels across various systems and processing networks. 

- Protects card data from the time it enters the environment until it is received by Elavon. 
- Applies advanced encryption that conceals data before it travels through the POS system or network. 
- Format-preserving encryption, removes the need to make changes to the POS system software and message format. 
 
**Property Card (PCARD):** A premise-based Java application that provides a common interface between multiple POS or PMS merchant systems and the GCS Bank switch process. PCard deploys as a Windows service.

**Proximity Device:** A consumer device that can be read from a distance (within a specified range) without physical contact; PayPass cards and devices are proximity devices.

**SAFE-T Suite:** Secure and Flexible Encryption and Tokenization that combines encryption and tokenization technologies to protect cardholder data in use, in transit, and at rest.

- Secures transactions with encryption and removes card data from the merchant’s environment with tokenization, a process that eliminates fees, fines and costs associated with a breach. 
- Reduces costs associated with PCI compliance. 
- Protects your brand. 
- Removes the risk of storing card data while transferring it to the processor. 
- Allows you to focus on initiatives that contribute to revenue rather than securing cardholder data. 

**Safe-T Link:** Supports two different Verifone devices. These devices use Verifone’s encryption service, Verishield Total Protect (VTP). VTP only supports Verifone devices. It is analogous to OnGuard for Ingenico devices.

**Settlement:** Involves transactions that are presented for funding and the eventual electronic deposit into the merchant bank account. Common terms within the electronic industry include: settle, deposit, upload, and batching.

**Simplify:** Elavon’s PIN Pad-based terminal application is designed to process electronic payment transactions from a Point of Sale (POS) or a Property Management system (PMS). 

The Simplify application layer runs on Ingenico Telium II PIN Pads using Voltage encryption, and communicates with Elavon’s Fusebox host process. Refer to the :magic-link[Simplify Developer Guide]{id="simplify-overview"}.

**TC** - Transaction Cryptogram. Approval cryptogram generated by the ICC.

**TCP/IP Gateway:** A method of interfacing to our Elavon software applications. Instead of a direct system call, an IP Socket Call Interface is written. TCP/IP Gateway Client and Server are included in the Windows Elavon software applications distribution for ease of testing and integration. Integrators can implement directly to the server or use our client. 

**Token Vault:** Enables tokenization to replace actual card data with a randomly generate unique ID (token) to protect data in use and at rest. Tokenization eliminates the possibility of having real card data stolen because the data no longer exists in the merchant’s environment, while allowing the use of the token in place of the PAN for necessary business tasks. Replaces actual card data with a randomly-generated unique ID (token) sent in the response message. 

**Transaction Processor (TPP):** Receives transaction requests from a merchant and approves or declines requests based on parameters set up between the TPP and various financial institutions. 

TPPs act as intermediaries between the merchant and the various financial institutions. They allow your customer and the merchant to submit transactions for authorization and settlement to the transaction processor, who processes them for the various card issuers involved.

TPPs operate worldwide and use a variety of methods for communicating and defining requests, including ISDN, asynchronous dial, frame-relay, and ATM.

**TVR** - Terminal Verification Results. Status of the different terminal risk management and cardholder verification functions as seen from the terminal.

**Voltage:** Voltage SecureData Payments applications provide a complete Point-to-Point Encryption (P2PE) solution.

:::::notice{note}
The Voltage solution is available on Ingenico terminals only. The TEP2 is the only Voltage format supported at this time. TEP2 offers Format Preserving Encryption where the BIN and last 4 of the account number are preserved. Simplify is integrated with TEP2 encryption.
:::::


**Y Transponder:** Radio frequency devices that can be wirelessly transmit a unique ID code to nearby reader.

Glossary

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

Fusebox Overview

Getting Started

Transaction Flow

Transaction Sequencing

API Message Format

Settlements

Reconciliation

Transaction Types

Authorization Only (01)

Sale Transaction (02)

Prior-Authorized Sale (07)

Return (09)

Void Sale (11)

Batch Close (13)

Batch Create and Inquiry (14)

Void Return (17)

Transaction Inquiry (22)

Full Authorization Reversal (61)

Heartbeat (73)

Incremental Authorization (75)

Partial Authorization Reversal (76)

Concepts

Tokenization

Tokenization Introduction

Tokenization API Fields

Tokenization Scenarios

Example Transactions

Error Scenarios

Retail

Retail Scenarios

Retail API Fields

Retail Examples

Lodging

Lodging Transactions

Lodging API Fields

Lodging Examples

Credential on File Transactions

Best Practices

Software Conversions

Restaurant

Restaurant Transactions

Restaurant API Fields

Restaurant Examples

Restaurant Credential on File Transactions

Restaurant Receipts

MOTO and eCommerce

eCommerce Transactions

MOTO and eCommerce API Fields

Ecommerce Examples

Direct Marketing Examples

eCommerce Credential on File Transactions

EMV Transactions

Implementation Considerations

Certification

EMV API Fields

EMV Public Cap Keys, Parameters, and Reports

Sample Files

EMV Receipts

EMV Integration Samples

API Based Settlement

Settlement Transactions

API-Based Settlement API Fields

API-Based Settlement Examples

Check Payment

Check Transactions

Check API Fields

Check Payment Examples

DCC Transactions

DCC Transaction Flows

DCC API Fields

DCC Examples

DCC Receipt Requirements

DCC Certification Process

Gift and Stored Value Cards

Gift and Stored Value Card Transactions

Gift and Stored Value Card API Fields

Gift and Stored Value Card Examples

Online Debit Transactions

Online Debit API Fields

Online Debit Examples

Private Label Cards

Private Label Transactions

Private Label API Fields

Private Label Examples

Health Savings Account Cards

HSA Support

Fusebox and Simplify HSA Card Support

HSA Card API Fields

Puerto Rico

E4 Support

API Fields

EBT Transactions

IVU Transactions