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

Tokens are designed to eliminate or limit the POS/PMS application’s need to store sensitive cardholder data. Tokenization allows a POS/PMS to store a value other than the Primary Account Number (PAN) for a processed card to be reused.


## Overview
Elavon has built a new Enterprise tokenization solution and database which uses Voltage as a provider. The Enterprise token solution allows merchants to convert from one type of token to another type. New merchants will be setup to use this system from the start, while existing merchants must be re-boarded to use. Merchants POS/PMS systems must indicate the token type they are providing and the token type they request to be returned. Fusebox will return the token value along with the token type, the POS/PMS systems will store this information for use on future transactions. 

## Token types
Fusebox supports the following token providers: 

**Voltage** - This provider is available with the preferred token solution in the Fusebox Gateway. Two formats can be selected: Numeric or Alpha/Numeric. This is the recommended provider that all customers are advised to use moving forward. 
**Merchant Link** - This is an external tokenization provider that can be used through the Fusebox Gateway. and this token type may be used in conjunction with the other providers. This provider is limited for use and is restricted to certain merchants, check with your account representative for availability information.
**Protegrity** - Protegrity is legacy token provider that has been removed from Fusebox. In the event a Protegrity token is sent to Fusebox, merchants can create a new Voltage or Merchant Link token to be returned.


### General token integration requirements 
- Merchant POS/PMS applications will send the PAN or track data with the card account number to be tokenized in API field 0003 in the API request message sent to Fusebox.
- Merchant POS/PMS applications must send API field 1008 with a value of “ID:” indicating a token is being requested in the API request message sent to Fusebox.
- Merchant POS/PMS applications must retain the token value in API Field 0003 of the API response message returned from Fusebox. 


:::notice{important} 
**Additional requirements** 
- Merchant POS/PMS applications must retain the token type provided value in API field 5027 of the API response message returned from Fusebox and store this value with the associated token. If API fields 5026 and 5027 are not provided, Fusebox will make a default selection of Voltage Numeric (VN) token type requested.
- Merchant POS/PMS applications must integrate to send API fields 5026 and 5027 indicate the token format that is being provided and requested in the API request message sent to Fusebox.
:::

### Examples 
- Token returned from Fusebox in API field 0003: **0003,ID:5964588594601773**
 - Merchant POS/PMS applications must provide the token value on subsequent transactions in field 0003 of their API request messages sent to Fusebox. 
 - This is required for subsequent transactions either within the same transaction life cycle or to start a new transaction life cycle. 
 
- Token sent to Fusebox in API field 0003: **0003,ID:5964588594601773** 
 - On subsequent transactions, the token value may change in the API response message from Fusebox. Merchant PMS/POS must update their token database and store this new token value (replacing the old token value) for use on future transactions.

Tokenization introduction

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