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

For online debit, performing the Sale and Return transactions causes Fusebox to send data immediately to the host for processing.  Depending on the processor and the method that they use to capture online debit transactions (Host vs. Terminal Capture), these transactions may or may not need to be settled.

**Transaction Type Sale (Type 02)**
  - Attempts to authorize the transaction and, if approved, will decrease the cardholder’s available balance.
  - The customer must enter a PIN for the transaction to be processed. 
  - Also, the Transaction Qualifier (Field 0115) must be included in the input request with a value of 030 (debit). 
  - This is the primary transaction used for online debit card purchases.  
  - Merchants are required to support this transaction. 

 **Transaction Type Return (Type 09)** 
  - Generates a refund on a customer’s debit card. To indicate the transaction is an Online Debit Return, the Transaction Qualifier (API Field 0115) must be included in the input request with a value of 030 (debit).
  - While your application should be able to support this transaction type, not all merchants (through their processing agreements) or processors will support it. Refer to your TPP to ensure that the merchant’s processor supports this transaction type. |

**Transaction Type Inquiry (Type 2)**
  - Use this to make inquires about the status of a transaction in the Fusebox database. This is used when an error occurs that prevents your POS application from receiving or processing the Output Response data, typically after a POS timeout.  
  - Fusebox searches its database for the Reference Number (Field 0007), Account Number (Field 0003), and Transaction Amount (Field 0002) provided in the original Input Request. If the record is found, a duplicate of the original response is returned.

:::notice{note}
Elavon requires that your POS application support the Transaction Inquiry (22) transaction.
:::



## System configuration 

Fusebox requires that the Debit Working Key (Field 1007) be passed in all Debit Sale (Tran Type 02) and Debit Return (Tran Type 09) input requests.

**Working Key Exchange (Tran Type 77)**

- Transaction requests between the POS PIN pad and the processor requesting a new working key.  Specific to FDMS/TeleMoney sets 73 and 101.

- If a new working key is requested, the new key should be stored in the POS application, used in the calculation of the PIN block and presented in API Field 1007 for all subsequent debit transactions.

## General guidelines

Your POS application must be able to identify how the transaction is to be processed. If the customer selects the online debit payment type option, the following requirements must be met:

- The debit card must be swiped and Track II data presented.
- No manual entries are permitted.
- The customer enters their PIN and a PIN block must be calculated and passed in an API.
- Open BIN ranges apply.
- No standard card validation (MOD‐10 checking) or card length routines apply.
- A unique terminal is called for each PIN pad/POS entry point (if applicable).

Merchants in the restaurant, lodging, auto rental, and direct market/MOTO industries typically use a two‐part transaction to authorize a card for an estimated cost of services to complete the transaction once the actual charge amount is known.

Most processors only support Sale (debit the cardholder’s account) and Return (credit the cardholder’s account) transactions. Pre‐authorizations, completions (prior‐auths), and voids are not supported.

Online debit transactions affect the cardholder’s account in real-time and cannot be used to “verify” funds are available.

## Settlement and reconciliation

The merchant/end user will not receive their settlement funding unless a settlement record is submitted to the transaction processor. Typically, the funding timeframe is no more than three (3) calendar days from the day the transactions were settled (transmitted to the processor for settlement). 

In addition, POS online debit transactions may have to be settled under a separate merchant and/or terminal ID issued by the POS online debit processor than what might be used for other electronic tenders (Visa, MasterCard, American Express, etc.). 

If you are settling based on criteria such as MKey or Card Type, transactions may need to be modified slightly for the new card type (Debit) or additional MKeys.

:::notice{note}
We strongly recommend that your application requires some type of pre‐settlement process.
:::

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

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