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

**0001 (Transaction Type)**
- Description: Required. Refer to the transaction matrix. 
- Length: 2 
- Data type: numeric

**0007 (Reference Number)**
- Description: Unique reference number to transaction. 
**Important**: Elavon does not recommend padding the Reference Number field (Field 0007) with leading zeros. Should you choose to do so, be sure to store the value in your system as a string instead of an integer. This will eliminate any potential discrepancies in how this field is presented in two-part transactions, and the chance of downgrades or fees is greatly reduced. 
- Length: 7 
- Data type: numeric

**0011 (User-Defined Field)**
- Description: Conditional. Required for SVS virtual cards only.  Value = VIRTUAL 
- Length: 80
- Data type: alphanumeric

**0017 (Cash Back)**
- Description: Conditional. Amount of cash back included in the amount field 0002. Required for SVS virtual cards only.  
- Length: 1 - 14
- Data type: cents

**0018 (Debit PIN Block)**
- Description: Conditional. Required for SVS virtual cards only. Value = 1234
- Length: 16
- Data type: alphanumeric
 
**0036 (Transaction Identifier)** 
- Description: Conditional. Contains the unique tracking number assigned by the credit card issuing bank. Third party processor interface specific.
- Length: 1 - 15
- Data type: alphanumeric

**0043 (System Trace Audit Number)**
- Description: Conditional. A host assigned reference number used for tracking purposes. When returned, must be printed on receipt.
- Length: 6
- Data type: numeric

**0060 (Unique Device ID)** 
- Description: Required. Must be stored and displayed and may be used for settlement. Used to identify the source lane or terminal through which a transaction is processed.
- Length: 1 - 8
- Data type: numeric

**0115 (Transaction Qualifier)**
- Description: Required. Identified type of account used. Gift and Stored Value Card = 050. Refer to the transaction matrix.
- Length: 3
- Data type: numeric

**0117 (Stored Value Function)** 
- Description: Required. Indicates stored value transaction function.
Valid values are: 
    - 1 = Activate 
    - 2 = Issue 
    - 3 = Reload 
    - 4 = Return
    - 5 = Redeem 
    - 6 = Redeem with cash back
    - 7 = Prior Auth 
- Length: 1
- Data type: numeric

**0128 (CPS Original Authorization Amount)** 
- Description: Conditional. Valid format: 0.00 – 99999.99
- Length: 1 - 14
- Data type: cents
 
**0130 (CPS Total Authorized Amount)**
- Description: Conditional. Approved amount. Valid format: 0.00 – 99999.99
- Length: 1 - 14
- Data type: cents

**0201 (Tip Amount)**
- Description: Conditional. Amount of tip.
Valid format: 0.00 – 9999.99. Third party processor interface specific.
- Length: 1 - 14
- Data type: cents

**0632 (Account Balance)**
- Description: Conditional. New account balance.
Valid format: 0.00 – 9999.99. Third party processor interface specific.
- Length: 1 - 14
- Data type: cents

**0645 (Previous Balance)**
- Description: Conditional. Previous balance on card. Third party processor interface specific.
- Length: 11
- Data type: numeric

**1035 (Total Number of Cards)**
- Description: Conditional. Total number of cards being issued at one time. Third party processor interface specific.
- Length: 2
- Data type: numeric

**1036 (Sequence Number of Card)** 
- Description: Conditional. Determines sequence numbers when multiple cards are issued. Third party processor interface specific.
- Length: 2
- Data type: numeric

## Additional card information


::page-heading-list{min-level=3 max-level=3 }


### Declines of approved cards

-   INACTIVE CARD - Doing any transaction other than Activate or Issue for a card that is not already active. 

-   INSUFF FUNDS - Redeeming more than available balance allows. 

-   CRD ALRDY ISSUED - Activate or Issue requested on a card that has already been issued. 
 
-   CRD NOT ISSUED - Card Reload transaction used on a card that has not been Issued or Activated.

-   CARD ALRDY USED - Reversal/Cancel transaction attempted on issue gift card after card has been redeemed. 

-   CARD FROZEN - Trying to lock the amount when a lock already exists. 

-   NO RECORDS FOUND - Previous transaction could not be found.

### Approvals

To get an approval, use any card number that is not defined in demo card scenarios. While most requests are approved, logic is performed based on the status and balance of a card which can result in the following declines.

### Account Balance and Open-to-Buy (24)

Transaction Type 24 (Account Balance and Open-to-Buy) is used to obtain the current account balance or open-to-buy amount for an association pre-paid gift card or stored value card. Pre-paid gift cards are not supported by all TPPs. If the TPP does not support this transaction type, a TRANSACTION NOT SUPPORTED error is returned from the application.

It is recommended that the POS application support this transaction type. Refer to the appropriate TPP interface guide(s) for additional information on how to determine if this transaction type is supported, and the requirements for the request and response messages.

### Gift and stored value card transaction matrix

**Transaction (Authorization Only)**
- Tran Type (API 0001) = 01
- Debit PIN Block\* (API 0018)   
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = N/A
- Tip Amount (API 0201)

**Tran Type (API 0001)** = Close Card 02
- Debit PIN Block\* (API 0018)  
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 3
- Tip Amount (API 0201)

**Tran Type (API 0001)** = Redemption 02
- Debit PIN Block\* (API 0018)  
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 5
- Tip Amount (API 0201)
 
**Tran Type (API 0001)** = Redemption Virtual 02
- Debit PIN Block\* (API 0018) = 1234
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 5
- Tip Amount (API 0201)

**Tran Type (API 0001)** = (Cash Back/Cash Out/Unload) 02
- Debit PIN Block\* (API 0018)  
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 6
- Tip Amount (API 0201)

**Tran Type (API 0001)** = Tip 02
- Debit PIN Block\* (API 0018)
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 5
- Tip Amount (API 0201) = $$$$$$.$$

**Tran Type (API 0001)** = IVR Authorized Redemption 07 
- Debit PIN Block\* (API 0018)  
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 7
- Tip Amount (API 0201) 

**Tran Type (API 0001)** = Prior Auth/Unlock 07
- Debit PIN Block\* (API 0018)  
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 7
- Tip Amount (API 0201)

**Tran Type (API 0001)** = Card Activation 09
- Debit PIN Block\* (API 0018) 
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 1
- Tip Amount (API 0201)

**Tran Type (API 0001)** = Card Activation 09
- Debit PIN Block\* (API 0018)  
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 1
- Tip Amount (API 0201) 

**Tran Type (API 0001)** = Issue Card 09
- Debit PIN Block\* (API 0018)  
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 1
- Tip Amount (API 0201) 

**Tran Type (API 0001)** = Issue Virtual Card 09
- Debit PIN Block\* (API 0018)  
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 2
- Tip Amount (API 0201)  

**Tran Type (API 0001)** = Reload/Recharge 09
- Debit PIN Block\* (API 0018)*  
- Transaction Qualifier (API0115) = 050
- Stored Value Function (API 0117) = 3
- Tip Amount (API 0201) 

**Tran Type (API 0001)** = Return 09
- Debit PIN Block\* (API 0018)  
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 4
- Tip Amount (API 0201)  

**Tran Type (API 0001)** = Void Redemption 11
- Debit PIN Block\* (API 0018) 
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 5
- Tip Amount (API 0201)  

**Tran Type (API 0001)** = Void Redemption 11
- Debit PIN Block\* (API 0018)  
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 5
- Tip Amount (API 0201)   

**Tran Type (API 0001)** = (Cash/Cash Back/Unload) 11
- Debit PIN Block\* (API 0018)  
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 6
- Tip Amount (API 0201)  
 
**Tran Type (API 0001)** = Void Prior Auth/Unlock/IVR Auth 11
- Debit PIN Block\* (API 0018) 
- Transaction Qualifier (API 0115) = 050
- Stored Value Function (API 0117) = 7
- Tip Amount (API 0201) 

**Tran Type (API 0001)** = Local Batch Close 13
- Debit PIN Block\* (API 0018) 
- Transaction Qualifier (API 0115) =  
- Stored Value Function (API 0117) = N/A
- Tip Amount (API 0201)

**Tran Type (API 0001)** = Local Batch Inquiry 14
- Debit PIN Block\* (API 0018)  
- Transaction Qualifier (API 0115)  
- Stored Value Function (API 0117) = N/A
- Tip Amount (API 0201)

**Tran Type (API 0001)** = Void Activation/Deactivate 17
- Debit PIN Block\* (API 0018)  
- Transaction Qualifier (API 0115) =  50
- Stored Value Function (API 0117) = 1
- Tip Amount (API 0201)

**Tran Type (API 0001)** = Void Card Issue 17
- Debit PIN Block\* (API 0018) 
- Transaction Qualifier (API 0115) =  50
- Stored Value Function (API 0117) = 2
- Tip Amount (API 0201)

**Tran Type (API 0001)** = Void Reload/Recharge 17
- Debit PIN Block\* (API 0018)  
- Transaction Qualifier (API 0115) =  50
- Stored Value Function (API 0117) = 3
- Tip Amount (API 0201) 

**Tran Type (API 0001)** = Void Return 17
- Debit PIN Block\* (API 0018) 
- Transaction Qualifier (API 0115) =  50
- Stored Value Function (API 0117) = 4
- Tip Amount (API 0201) 

**Tran Type (API 0001)** = Balance Inquiry 24
- Debit PIN Block\* (API 0018) 
- Transaction Qualifier (API 0115) =  50
- Stored Value Function (API 0117) = N/A
- Tip Amount (API 0201) 

:::::notice{note}
API field 0018 is used only in conjunction with virtual cards.
:::::


Gift card demo mode runs transactions that mimic gift card functionality. For example, any approved card can be redeemed until the amount issued is exhausted. All cards are reset automatically at midnight, Eastern (EST). 



Gift and stored value card API fields

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