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

Batch Create and Inquiry (Type 14) returns the net total amount and count for the requested batch (or subset) of transactions contained within the current batch.

### Batch Close (13) or Batch Inquiry (14) selection criteria
To process either a Close Batch (13) or Batch Inquiry (14) transaction, use the criteria below to determine which data values to utilize. The API field or combination of fields determines the type of transactions to close or inquiry.

:::::notice{note}
This method can only used with Force Close batch type.
:::::

**8006 (Chain Code)** - Send only this field to close or inquiry transactions processed by an entire chain group tied to a specific code.
 
**8002 (Location)** - Used to close or inquiry transactions run at a specified location, such as a single store or hotel operating under a unique location name.
 - Send fields 8002 (Location) and 8006 (Chain Code)

- **Terminal ID** - Used to close or inquiry transactions processed by a specified terminal.
Required fields: 
 - 0109 (Terminal ID) 
 - 8002 (Location) 
 - 8006 (Chain Code)
 


### Credit, Debit, Private Label and Electronic Check totals transactions

**Net Amount** 
Based on the level selected above, the same net amount is returned for approved monetary transactions in the following fields: 

- 1013 (Local Batch Net Amount) 
- 1016 (Host Net) 
- 1018 (Funded Net) 

**Net Count**
Based on the level selected above, the same net count is returned for approved monetary transactions in the following fields: 

- 1014 (Local Count) 
- 1017 (Host Count)
- 1019 (Funded Count)



### Batch Create and Inquiry API Fields

**0001 (Transaction Type)** 
 - Description: Tran Type 14 Batch Inquiry.
 - Length: 2
 - Data Type: Numeric 
 
**0109 (Terminal ID)**
 - Description: Terminal ID. *Optional. If inquiring for the entire Chain Code or Location leave blank.
 - Length: 1 - 8
 - Data Type: Numeric 

**0140 (Merchant Currency Code)** 
 - Description: ISO alpha currency code of the Merchant.
 - Length - 3
 - Data Type: Alphanumeric 
 
**1003 (Gateway Response Code)**
 - Description: Elavon Gateway Response Code indicating success of transaction.
 - Length: 1-4
 - Data Type: Numeric
 
**1004 (Host Response Message)** 
 - Description: May contain an Elavon Gateway application error message or a message from a partner application or TPP.
 - Length: 1-80
 - Data Type: Numeric

**1010 (Gateway Response Message)** 
 - Description: Elavon Gateway text response message corresponding to error code returned in API field 1003.
 - Length: 1-80 
 - Data Type: Alphanumeric
 
**1012 (Gateway Batch Number)** 
 - Description: A global number generated to represent a batch of transactions. The batch may contain many different TPPs, each uploaded under a different host batch number.
 - Length: 1-8
 - Data Type: Numeric
 
**1013 (Local Batch Net Amount)** 
 - Description: Net amount of transactions captured in the Fusebox batch file. This field will contain a leading “-” sign if net amount is negative.
 - Length: 1-20
 - Data Type: Character
 
**1014 (Local Batch Tran Count)** 
 - Description: Total count of transactions captured in the Fusebox batch file.
 - Length: 1-9
 - Data Type: Numeric
 
**1016 (Host Batch Net Amount)** 
 - Description: For host capture processors capable of returning this information. Net amount of transactions captured in the host batch file. This field will contain a leading “-” sign if net amount is negative. 
 - Length: 1-20
 - Data Type: Character
 
**1017 (Host Batch Tran Amount)** 
 - Description: For host capture processors capable of returning this information. Total count of transactions captured in the host batch file.
 - Length: 1-9
 - Data Type: Numeric
 
**1018 (Funded Batch Amount)** 
 - Description: The amount of the batch that will be funded if all transactions are accepted.
 - Length: 1-20
 - Data Type: Character
 
**1019 (Funded Batch Count)** 
 - Description: For host capture processors capable of returning this information. Net amount of transactions captured in the host batch file. This field will contain a leading “-” sign if net amount is negative.
 - Length: 1-9
 - Data Type: Numeric

**7007 (Transaction Link Identifier)** 
 - Description: This field is the unique identifier to a transaction in Fusebox.
 - Length: 21
 - Data Type: Numeric

**8002 (Location)** 
 - Description: Location name passed in the transaction. *Optional. If inquiring for the entire Chain Code leave blank.
 - Length: 16
 - Data Type: Alphanumeric
 
**8006 (Chain Code)** 
 - Description: Chain Code passed in the transaction. Required. *Optional field based on the level at which you are choosing to settle, Chain Code, Location or Terminal ID.
 - Length: 6
 - Data Type: Alphanumeric

Batch Create and Inquiry (14)

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)

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