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

This page details the API fields for eCommerce, 3DS pass thru and direct marketing transactions. The following requirements and fields must be considered when submitting an MOTO and eCommerce transaction and should only be populated if they apply to your implementation. eCommerce transactions include all direct marketing fields.

## eCommerce 

:::::notice{note}
In fields required for 3D Secure transactions where the ECI is 5 and the site is a participating merchant in the MasterCard or Visa card authentication process, the authentication response needs to be presented at the time of authorization and settlement. 
:::::

### Fields 0712 (Charge Description) and 0190 (eCommerce Indicator (ECI)

:::::notice{important}
MOTO and eCommerce indicator fields are required for direct marketing integrations.
:::::

Fields 0712 and 0190 are required on all direct marking transactions and must contain the same value.
- If the transaction is MOTO, set the appropriate value in field 0712.
- If the transaction is eCommerce, set the appropriate value in field 0190.
- Once the appropriate value is placed into 0712 or 0190, set the same value in the other field.  

**Examples**

- MOTO single transaction
0712 = 1
0190 = 1

- Channel encrypted eCommerce transaction
0712 = 7
0190 = 7
 
## Tabulated data fields

Tabulated data is a field type that supports multiple values in a single field. The data separator in a tabulated field is a semi-colon (;).

A field must be enabled with tabulated data before it can have multiple values included. If the TPP interface module supports tabulated data, the module must be added to the *TableizedSupport (a section of the admproc.txt file).

Direct marketing tabulated fields are 0720, 0721, 0722, 0735 and 0736.

:::::notice{note}
While not all values are listed as supported in both fields 712 and 190, Fusebox will accept these values in both fields and use them properly in the TPP Interfaces.
:::::


## Key API fields

**0190 (eCommerce Indicator - EC)**  
- Description: This value must be presented in any eCommerce transaction. For returns, the value must be the same as the value of the original sale. 
- Valid values:  
    -  5 = 3-D Secure Compliant 
    -  6 = Non-Authenticated 3-D Secure  
    -  7 = Channel Encrypted 
- Length: 1
- Data type: alphanumeric

**0191 (Electronic Goods Indicator)**
-   Valid values: 
    -   D = Digital Goods  
    -   P = Physical Goods 
- Length: 1
- Data type: alphanumeric

**0197 (eCommerce Checkout Merchant URL/Reverse Domain Name)**
- Description: This field contains the URL or Reverse Domain name used for the check out process of an eCommerce transaction (including internet, 3-D Secure, digital secure remote payments, in-app).
- Valid values: Variable; Provided by the merchant
- Length: 1 - 111
- Data type: alphanumeric

**0198 (eCommerce Registered User Indicator)** 
- Valid Values: 
    -   Y = Yes, the cardholder has a registered profile with login credentials on the merchant's website. 
    -   N = No, the cardholder does not have registered profile with login credentials on the merchant's website, may only shop as a guest.
- Length: 1
- Data type: alphanumeric

**0199 (eCommerce Registered User Profile Change Date)**
- Description: Date of the last change to a registered user's profile on a merchant's website.
- Valid value: Format: DDMMYYYY Example: 31122021 
- Length: 8
- Data type: numeric

## 3DS pass thru 

:::::notice{note}
Fusebox is not a service provider for 3DS.
:::::


**0192 (Program Protocol\*)**
- Description: Used to indicate the type of 3D Secure protocol used. 
- Valid values:
    - Blank - Not a 3D secure transaction 
    - 1 - 3D secure transaction, version 1.0 
    - 2 - 3D secure transaction, version 2.0
- Length: 1
- Data type: numeric

**0193 (Direct Server Transaction ID\*)**
- Description: Required version for 3-D secure version 2.0 (API Field 0192 = 2). This data is generated by the directory server during the authentication transaction and passed back to the merchant with the authentication results. 
- Allowed values: Variable
- Length: 1 - 36
- Data type: alphanumeric

**0194 (CAVV/UCAF/Tran Stain\*)**
- Description: Used for a 3-D, SPA, or SET transaction. This field contains a unique value calculated by applying a secure algorithm to the XID. 

**Note**: The merchant's website communicates directly with Visa to get the 3D Secure verification response value. This communication does not occur through Fusebox. The 3D Secure verification response value that the merchant gets directly from Visa is sent to Fusebox in API field 0194.

- Length: 1 - 40
- Data type: alphanumeric - Base 256 Flat ASCII HEX

**0196 (CAVV Response\*)**
- Description: Used in a 3DS transaction. 
- Valid Values:
    -   Blank = CAVV not validated 
    -   0 = CAVV not validated due to erroneous data submitted 
    -   1 = CAVV failed 
    -   2 = CAVV passed 
    -   3 = CAVV validation could not be performed (issuer attempt incomplete) 
    -   4 = CAVV validation could not be performed (issuer system error)
- Length: 1  
- Data type: numeric 


## Direct marketing 

**0054 (POS Entry Mode)**
- Description: 01 - Manual/Key Entry
- Length: 2  
- Data type: numeric 

**0711 (Shipping Date)**
- Description: Date the merchandise was shipped to the customer. 
- Format: MMDDYY
- Length: 6 
- Data type: date 

**0712 (Charge Description)**
- Description: Identifies the type of direct marketing charge.
- Valid values:
    -   1 = Single transaction mail/telephone order  
    -   2 = Recurring mail order transaction  
    -   3 = Mail order installment payment
- Length: 1 
- Data type: numeric 

**0713 (Clearing Sequence Count)**
- Description: Contains the total number of payments or installments to be made on this account.
- Length: 2 
- Data type: numeric 

**0714 (Clearing Sequence Number)**
- Description: Contains the sequence number of the payment or installment associated with the charge. 
- Valid value: The value should be between 1 and the clearing sequence count (API field 0713).
- Length: 2
- Data type: numeric 

**0715 (Order Number)** 
- Description: Contains the purchase order or invoice number associated with this charge. May be the same as contents of reference number (API field 0007).
- Length: 10
- Data type: alphanumeric 

**0716 (Ship to ZIP)**
- Description: Ship code where the merchandise is to be delivered.
- Length: 5 - 9
- Data type: alphanumeric 

**0717 (Item 1 Text)**
- Description: Description of charges. This field is required along with API field 0720.
- Length: 40
- Data type: alphanumeric

**0718 (Item 2 Text)**
- Description: Description of charges. Required if there is an Item Code 2 (API field 0721).
- Length: 40
- Data type: alphanumeric

**0719 (Item 3 Text)**
- Description: Description of charges. Required if there is an Item Code 3 (API field 0722).
- Length: 40
- Data type: alphanumeric

**0720 (Item Code 1)**
- Description: 
    -   SubField 1: Item code describing type of product purchased (max size 4, type N)
    -   SubField 2: Item quantity (max size 3, type N)   
    -   SubField 3: Item amount (max size 14, type C)  
    -   Format: NNNN;NNN;NNNNNNNNNNN.NN  
- Valid examples: 
    -   720,23;1;13.42 (This example includes all subfields, item code, quantity, amt.) 
    -   720,2;2.35 (This example is quantity + amt only.)  
    -   720,453 (This example is item code only. This is an example of legacy use.) 
- Length: 4 - 23
- Data type: numeric

**0721 (Item Code 2)** 
- Description: Item code describing type of product purchased. Required if there is an Item 2 Text. Refer to description for field 0720.
- Length: 4 - 23
- Data type: numeric

**0722 (Item Code 3)**
- Description: Item code describing type of product purchased. Required if there is an Item 3 Text. Refer to description for field 0720.
- Length: 4 - 23
- Data type: numeric

**0723 (Item Code 3)**
- Description: Flag indicating status of recurring payment (Card on file transaction)
- Valid values:  
    -   F - First Payment  
    -   S - Subsequent scheduled recurring payment (i.e., regular payment)  
    -   U - Unscheduled recurring payment/purchase
- Length: 1
- Data type: alphanumeric

**0724 (Ship to Address Line 1)**
- Description: If different than the billing street address.
- Length: 35
- Data type: alphanumeric
 
**0725 (Ship to Address Line 2)**
- Description: If different than the billing street address and an additional line is necessary.
- Length: 35
- Data type: alphanumeric

**0726 (Ship to City)** 
- Description: If different than the billing city.
- Length: 20
- Data type: alphanumeric

**0727 (Ship to State)**
- Description: If different than the billing state.
- Length: 2 
- Data type: alphanumeric
 
**0732 (eCommerce field migrated to 0191)**   

**0733 (Item 4 Text)** 
- Description: Description of charges. Required if there is an Item Code 4 (API field 0735).
- Length: 40
- Data type: alphanumeric

**0734 (Item 5 Text)** 
- Description: Description of charges. Required if there is an Item Code 5 (API field 0736).
- Length: 40
- Data type: alphanumeric

**0735 (Item Code 4)**
- Description: Item code describing type of product purchased. Required if there is an Item 4 Text. Refer to description for field 0720.
- Length: 4 - 23
- Data type: numeric

**0736 (Item Code 5)**
- Description: Item code describing type of product purchased. Required if there is an Item 5 Text. Refer to description for field 0720.
- Length: 4 - 23
- Data type: numeric

**0738 (Recurring Compliance Data)** 
- Description: Contains compliance data that merchants should retain and then return unaltered in the next recurring/card on file transaction.
- Length: 1 - 50
- Data type: alphanumeric

**0739 (Credential on File - Initiation and Purpose Indicator)**
Description: This field indicates if cardholder or merchant initiated the credential on file transaction and for what purpose.

**Note:** This field is required for all credential on file transactions. For existing integrations that do not use this field yet, Fusebox TPP interfaces will continue to make assumptions based on the fields that the POS/PMS is currently sending.

Valid values:
- Initial card on file transaction - first transaction establishes COF
  - F101- Credential on File (ad hoc)
  - F102 - Standing order (variable amount and fixed frequency)
  - F103 - Subscription (fixed amount and frequency)
  - F104 - Installment
- Cardholder initiated COF transactions (CIT) - Cardholder uses established COF
  - C101- Credential on File (ad hoc)
  - C102 - Standing order (variable amount and fixed frequency)
  - C103 - Subscription (fixed amount and frequency)
  - C104 - Installment
- Merchant initiated COF transactions (MIT) - Merchant uses established COF
  - M101 - Unscheduled Cred on File
  - M102 - Standing order (variable amount and fixed frequency)
  - M103 - Subscription (fixed amount and frequency)
  - M104 - Installment
  - M205 - Partial shipment
  - M206 - Related/delayed charge
  - M207 - No-show charge
  - M208 - Resubmission

- Length: 4
- Data type: alphanumeric




MOTO and eCommerce 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

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