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.

## Cardholder Present

1. The PMS/POS sends a request transaction with the transaction amount, the transaction type (i.e., authorization, sale, refund, etc.) and other required data to the Payment Application.

2. The Payment Application receives and parses the inbound message.

3. The Payment Application interacts with the cardholder to get the full transaction amount (i.e., get TIP and cashback amounts and total amount approval).

4. The Payment Application interfaces to the PIN Pad and cardholder to get the card account data.

5. If Visa or MasterCard account and DCC is enabled, the following steps should be performed:

    a.  Send Fusebox the Eligibility and Rate Inquiry message (transaction type 46).

    b.  If the card is not DCC eligible, the payment application will continue as they do today with one minor change, setting DCC fields 151 and 169 appropriately (see API samples).

    c.  If the card is DCC eligible, the payment application should interact with the cardholder to see if they want to opt-in to DCC. If they say ‘no’, the payment application performs the normal authorization in the base currency only setting DCC fields 151 and 169. If they say ‘yes’, the payment application will update the transaction with DCC data and continue the card processing flow, (see API samples).

6. The Payment Application continues with the remainder of the EMV/magstripe processing as they do today. When all data is captured, the Payment Application sends the completed Elavon Gateway API transaction request message to Fusebox for processing.

7. Fusebox processes the inbound request message and sends/receives the message with the merchants’ TPP host and returns the response to the Payment Application.

8. The Payment Application completes the transaction processing with the PIN Pad’s and returns the completed transaction message to the POS.

9. The POS prints the receipt showing the cardholder opted in to DCC and the DCC data elements.


::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/fusebox/crdhldrprsnt.png"   alt="transaction flow for cardholder present"}


## Cardholder Not Present

This scenario might occur if a cardholder has already opted-in to use their country currency rate and the merchant has it on record (e.g., recurring billing) or to be used for a lodging incremental transaction where the cardholder has already opted-in.

1. The PMS/POS sends a DCC Eligibility and Rate Inquiry message (transaction type 46) to Fusebox with the card’s token.

2. If the card is DCC eligible, the DCC converted amount and other data will be returned to the payment application.

3. The PMS/POS can use the converted amount and DCC data returned to the eligibility message to send the financial message on to Fusebox, as they would today (see API samples).

4. Fusebox processes the inbound request message and sends/receives the message with the merchants’ TPP host and returns the response to the PMS/POS.


::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/fusebox/crdhldrntprsnt.png"   alt="transaction flow for cardholder not present"}



DCC Transaction Flows

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

Receipt Example