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

Fusebox accrues batches with all transactions sent from a POS or entered using a virtual terminal at the Site ID level using Terminal ID, Location Name and Chain Code data. POS transactions and virtual terminal transactions are placed into separate batch types to be processed separately. A batch can be configured by either Auto Close or Force Close. If a batch remains open for 7 days, it will automatically close in Fusebox. 

### Auto Close
- **Important**: This method of settlement is the most common implementation for merchants.
- In this configuration, Fusebox automatically closes existing batches for transactions grouped by Site ID, at a specified time each day. 
- Settlements are aggregated into multi-merchant batches to transmit to the TPP on the following business day. 

### Force Close
- If configured to Force Close, you must log in and settle manually using the Fusebox Batch Management User Interface (BMUI).
- A batch can be closed by initiating a Force Close transaction from a POS by sending an API batch close message to Fusebox. See :magic-link[API Based Settlement]{id="settlement-transactions"}.

:::::notice{note}
When a site is set to Auto Close, the first transaction performed after the Auto Close time will be the last transaction of that batch. Once a batch is closed, the POS/PMS will not be able to void a transaction.
:::::


## Batch processing stages
A batch goes through several different stages before the deposit is complete:
- **No Batch**: No transactions have been performed since the last batch was closed.
- **Open**: Batch is open and still accepting new transactions.
- **Settled**: Batch pre-processing is still in progress by the Elavon Gateway or the merchant is configured for a two-part batch close and release from web (POS Release by Web = yes).
- **Suspend**: The Elavon Gateway has discovered an issue with the batch and will resolve it shortly or will contact the POS integrator or merchant to determine what needs to happen to resolve the issue.
- **Confirmed**: The batch has been confirmed. This does not mean that the funds have been deposited into the merchant bank account. It does mean the TPP has the information and will start that process. 
 
## Duplicate transaction scanning
Settlements are subject to duplicate checking during the settlement process. Duplicate Transaction Scanning is a system configuration option that uses the Site ID mapped from the Chain Code, Location, PAN, Reference Number, and Terminal ID to compare values. Duplicates will not be presented to the processor for funding, placed into a batch indicating suspense status ("suspend" above) and will be processed as an exemption item. 


:::::notice{note}
Fusebox does not automatically generate user settlement reports. Reports are created manually through the Batch Management User Interface (BMUI) or the Fusebox Reporting User Interface.
:::::

## Post-settlement best practices:
- Confirm settlement results as soon as possible, preferably before the next day of business. Resolve any settlement errors before the next scheduled batch close. Merchants may incur penalty fees if they do not perform settlement within the number of days set by the card associations.
- Clearly report and confirm the status of the previous settlement daily.
- Reconcile the actual amounts deposited in the account with the reports generated during the settlement.
- **Note:** These steps will identify duplicates and other potential problems involving the transfer of funds.

## Fusebox UI settlement
To settle from the FBUI, log in to the user interface and ensure the amounts about to be settled have been reconciled in the previous steps. For step-by-step information, please refer to the Fusebox User Interface guides or request from your Elavon account representative.


### Virtual terminal batches
Transactions that have been entered via the Fusebox UI are added to a virtual batch and aggregated in a separate total and batch settlement process. POS batch transactions that are updated through BMUI are not included in a virtual batch. Settings for batch type, close time, and release by web are the same by default, unless otherwise specified by at installation. 

Virtual terminal batches can be configured as auto close or force close. If a virtual terminal batch is set to force close, and the API batch close process is not utilized to close it, the batch must be closed manually with the BMUI.

### POS Release by Web flag Yes/No
In the Fusebox UI settings, the POS Release by Web flag can be set to process automatically or require additional steps in the settlement process (either Auto Close or Force Close).
Flag settings:
**If set to Yes:** Log in to the Fusebox application UI and release the batch from a pending status to a settled status. 
**If set to No:** Closed batches are immediately queued for the next Fusebox settlement processing job.

Settlements

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

Fusebox overview

Getting started

Transaction flow

Transaction sequencing

API message format

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)

Token Request (37)

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