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

API‐based settlement supports pre‐settlement reconciliation and settlement by using two transaction types: 
 

**Batch Inquiry (Type 14)** 
 - Confirms the transaction count and amount for a specified Terminal ID, Location Name, or Chain Code.

**Batch Close(Type 13)** 
 - Sends transaction details to the Third Party Processor TPP or host for funding. **Note:** Auto Close is the most commonly integrated settlement method, which does not require using this transaction type to manually initiate.


A batch can be settled by group of transactions using the following criteria:
- Terminal ID (Field 0109)
- Location Name (Field 8002)
- Chain Code (Field 8006)

 
## Settlement process

1. **Pre‐settlement reconciliation:** Elavon recommends that you use the Batch Inquiry request to confirm the transaction count and amount totals. Fusebox can then use the Batch Close request to transmit the batch to the TPP or host. 
See :magic-link[Reconciliation]{id="reconciliation"} for detail.

2. **Settlement (Batch Close):** During a Batch Close, you may direct Fusebox to settle a batch. The system then sends the batch to the third‐party processor. A successful response (value returned in field 1003 = 0000) message does not indicate that transactions were funded properly or completely. The only way to confirm settlement funding is through your bank deposit information. 

3. **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 event. 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 Batch Close.
- These steps will reduce duplicate settlements and other potential problems involving the transfer of funds.
 

### Failed settlement
A value other than **0000** in Field 1003 indicates an incomplete settlement attempt. If the settlement failed, you should clear the indicator only by a successful manual settlement or an override from an appropriate authority.
 
You should only attempt API‐based settlement once per business or transaction date for a batch. Further attempts to deposit a failed batch should be initiated from the Fusebox Batch Management User Interface (BMUI).
Contact your transaction processor help desk if you receive any error response messages or communication errors during settlement. This will confirm whether the processor accepted a full or partial transmission.
 

### Additional guidelines
If a settlement was unsuccessful, contact your transaction processor before resubmitting it. Your application should not settle a batch of transactions more than once to avoid creating duplicate charges on cardholder accounts.
Resettlement procedures must be performed manually using the Fusebox BMUI. Once a settlement process has failed, API‐based settlement for that batch is no longer an option.

 

## Value Added Reseller (VARs) responsibilities
VARs that implement API‐based settlement into their applications must supply both training and written documentation for each installation that uses this functionality prior to the merchant initiating the settlement process for the first time.

The merchant must be informed on how to identify settlement failures and be properly trained in the areas of problem identification, escalation, and resolution. This is important when related to reconciliation, settlement, and re‐settlement issues.

Settlement transactions

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

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)

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

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