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.

Each new Payment Service Provider (PSP) solution must be fully certified and approved with Elavon prior to working in a production environment. The certification process ensures that all DCC solutions meet the requirements by both Elavon and the card brands.

The certification process includes the following:

1. The PSP must confirm what method of DCC they are developing (either Host based or Device Conversion using the DCC BIN File method). 
2. The PSP must provide high-level overview of their solution which outlines its core architecture. 
3. The PSP must confirm how many of the 83 currencies offered will be supported on the POI Solution. Elavon’s expectation is that all currencies should be supported. 
4. The PSP must outline how the Account Range BIN file will be implemented and maintained (*only if they are using the device-based method*); confirming if the file is held centrally or locally at the POI solution. The process for updating the file must be demonstrated and validated during the certification. 
 - It should be possible to determine the BIN file that is currently in use at the POI. This should be available via a function on the POI solution or by printing a debug / configuration receipt. 
5. An error message should be implemented on the POI solution if the solution is activated for DCC processing but no BIN file is present, to inform the merchant that DCC cannot take place until a valid BIN file is loaded. 
6. The PSP must outline how the exchange rates will be implemented and maintained, confirming if the file is held centrally or locally at the POI solution. The process for updating the exchange rates must be demonstrated and validated during the certification. 
7. The PSP must demonstrate that the conversion process adheres to the requirements set out for rounding and truncation 
8. Physical copies of test transaction receipts (sale/refund/pre-auth and completion) must be supplied to Elavon for validation. These will be assessed based on the receipt requirements as outlined 
9. Details of the POI user interface must be provided, demonstrating that the solution adheres to the choice, transparency and disclosure requirements outlined 
10. Elavon will provide a test script that will contain a full list of transactions that must be completed. Once the test script is completed, Elavon will validate the following items:
 - The exchange rate request message is in the correct format. 
 - The full list of transactions completed adhere to the correct format as outlined in the Authorization protocol specification. 
 - The POI solution can determine the valid currency of the card based on the 6th, 7th, 8th and 9th, and up to 12th digit of the Card PAN. 
 - The DCC transactions processed used the correct conversion rate. 
 - The DCC transactions processed reflect the correct applied mark-up. 
 - The rounding and truncation of the amount is correct. 
 - The currency exponents allocated for 0, 2, and 3 decimal place currency is correct. 
 - The settlement / data capture file provided for all transactions match the original transactions completed at Authorization. 
 - Full details contained on the transaction receipts to ensure that they match the test criteria provided. 
 - Ability to provide a Quotation report that adheres to the requirements outlined. 
 - Ability to provide an exchange rate report that adheres to the requirements. 
11. The PSP must advise us that multiple Merchant IDs can be setup and maintained with exchange rates that have different mark-up percentages applied. 
12. The PSP must advise us that DCC can be configured at a terminal level, e.g. the ability to enable and disable the DCC functionality on the POI Solution.

DCC Certification Process

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

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