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.

**On Guard** 

On-Guard encryption is supported on Ingenico terminals only. Simplify using On-Guard can be operated as part of a PCI P2PE-validated solution (Safe-T Link with P2PE Protect).

**Voltage** 

Elavon’s Fusebox platform supports the Voltage SecureData Payments applications to enable our customers to implement a complete solution for P2PE using:
- Voltage SecureData Payments POS Software Development Kit (SDK)
- Voltage SecureData Payments Host Software Development Kit (SDK)
- Voltage SecureData Management Console
- Voltage Key Management Server (operating as an HSM or Hardware Security Module)
- Voltage SecureData Simple API

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. 

See the :magic-link[Simplify Developer Guide]{id="/products/simplify/v1/overview"} for more information. 

## Point to Point Encryption in the Elavon Gateway Message 

Point-to-Point Encryption in the Elavon Gateway Message is supported with Ingenico On-Guard or Voltage, and Verifone VeriShield Total Protection. 


## Elavon Gateway Message API Fields used in P2PE 

The following Elavon Gateway Message API fields are utilized in P2PE:

**0003 (Account Number)**
- Description: The account number field will be left blank when sending transactions to Simplify unless a manual transaction entry is desired on the encrypting device. 
 - To prompt for manual entry on Simplify, pass 3, K (with K for manually keyed). 
 - For Bring Your Own Device, encrypted track data must be presented as delimited base64 or plain ASCII. 
 - The combined length of the two ciphers plus sentinels will not exceed 255 Bytes in length. The required format is: 0003,%[Track 1 cipher]?;[Track II cipher]?
 - The sentinels are a requirement to maintain track identification. Regardless of format, extraneous sentinels or delimiters will be discarded post decryption. In those cases the sentinels are supplied (format preserving), then the POS need not add them. - Simplify can be configured to support SAF (Store and Forward} processing for timed-out (offline) transactions, using one of the following methods:
 - 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 resubmits the transaction (through Simplify or directly to Fusebox) for host approval.
 - On-Device SAF (version 28 and above) – Simplify performs Stand-in and SAF processing.
- Size: 1 - 128 
- Data Type: A/N
- Simplify, Voltage or POS: Simplify or POS

:::::notice{note}
For POS SAF, the response from Simplify will provide encrypted track or account number, which can be stored locally in the POS until the transaction is resubmitted to Fusebox. The customer is responsible for making this data unrecoverable after completion of the authorization process.
:::::


**0004 (Expiration Date)**
- Description:
- Valid Values: 
 - The expiration date field will be left blank when sending transactions to Simplify.
 - The expiration date is returned in the response and must be stored in the POS for future transactions. 
 - A valid expiration date is required to submit a new transaction (with the exception of a return, where the return can be processed to an expired card).
 - Verifone VSP special processing. 
 - With Verifone the expiration date is modified when the card data is encrypted. 
 - For Classic Key, 32 years is added to the expiration date. For Derived Key, 44 years is added to the expiration date. 
 - For Bring Your Own Device with Verifone VSP, note that the expiration date from the device will not match the card expiration date. 
- Size: Date, 4, MMYY
- Data Type: N
- Simplify, Voltage or POS: Simplify and POS

**0050 (CVV2 or CVC20 or CID)**
- Description: 
- Valid Values: 
 - Voltage Only
 - If a card is manually entered at the terminal, the CVV2 or CVC2 or CID will be encrypted before being passed to Fusebox. This encrypted value may be up to 10 characters long and alphanumeric.
 - For Bring Your Own Device integration with Voltage
 - The POS may need to pass this information from the device directly to Fusebox. 
- Size: 3 - 10
- Data Type: A/N 
- Simplify, Voltage or POS: Simplify, Voltage or POS 
 
**1008 (Masked Account Number Token Request field)**
- Description: 
 - Although tokenization is not required for P2 PE, it is required for two-part or complex lifecycle transactions (lodging and fine dining). 
 - One part (sale) transactions are strongly recommended to use tokens. Without a token in the POS, there is no value to present to Fusebox on future transactions (void or return). 
- Size: 1 - 21
- Data Type: A/N
- Simplify, Voltage or POS: POS

**5002 (Device Serial Number)**
- Description:
 - In Bring Your Own Device integration with Voltage, the POS will need to send the serial number from the device.
 - In Store and Forward processing, the serial number of the original device must be passed with the original Chain Code, Location, Terminal ID, and encrypted data from the original transaction.
- Size: 1 - 20
- Data Type: A/N
- Simplify, Voltage or POS: Simplify, Voltage or POS

**5004 (Encryption Provider ID)**
- Description: 
 - a) S1 = Verifone Classic Key (not available for new implementations)
 - b) V1 = Verifone Derived Key
 - A site boarded for P2PE will error if the encryption provider ID is not supplied or if the data is not properly encrypted when processed to the Chain Code, Location, Terminal ID, and serial number.
 - Size: 1 - 20 
 - Data Type: A/N 
 - Simplify, Voltage or POS: POS
 - Encryption Provider ID
 - G2 = Voltage type TEP2
 - G3 = Voltage type TEP3 

:::::notice{note}
A site boarded for P2PE will error if the encryption provider ID is not supplied or if the data is not properly encrypted when processed to the Chain Code, Location, Terminal ID, and serial number.
Only TEP2 and OG = On-Guard are supported
:::::


**5004 (Error)**
- Description: 
 - IF A TERMINAL’S tc_e2e_device_type (FROM THE TERMINAL CONTROL RECORD) IS LOADED WITH A VALUE AND THE TERMINAL REQUEST MESSAGE DID NOT CONTAIN A MATCHING VALUE IN gwa_e2e_device_type (API FIELD 5004)
* “ OR “ A CARD TOKEN (API FIELD 0003), WE REJECT THE MESSAGE WITH 
 - API_1003_TERM_RESP_CODE = 0286 
 - API_1010_TERM_RESP_TEXT = CARD NOT ENCRYPT 
 - API_1004_HOST_RESP_TEXT = CARD NOT ENCRYPT 
- Size: 1 - 20
- Data Type: A/N 
- Simplify, Voltage or POS: Voltage or POS

**5005 (Encryption Transaction Block)**
- Description:
- Valid Values: 
 - This is a Voltage value supplied by the terminal as the ETB with all encrypted transactions and used to decrypt the account number supplied in API Field 3. The data will be in Base 64 format of up to 512 bytes of data. 
 - In a Bring Your Own Device integration with Voltage, the POS will need to send the Encryption Transaction Block from the device. 
- Size: 1 - 512
- Data Type: A/N 
- Simplify, Voltage or POS: Simplify, Voltage or POS

Point to Point Encryption

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

Fusebox Overview

Getting Started

Transaction Flow

API Message Format

Transaction Sequencing

Reconciliation

Settlements

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