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

## Transaction types  

A retail integration uses only a few of the many transaction types available. Below is a list of the transactions used by most retail POS applications.
- :magic-link[Authorization Only (Type 01)]{id="authorization-only-md"}
- :magic-link[Sale (Type 02)]{id="sale-transaction-md"}
- :magic-link[Prior-Authorized Sale (Type 07)]{id="prior-authorized-sale-md"}  
- :magic-link[Return (Type 09)]{id="return-md"}
- :magic-link[Void Sale (Type 11)]{id="void-sale-md"}
- :magic-link[Void Return (Type 17)]{id="void-return-md"}
- :magic-link[Transaction Inquiry (Type 22)]{id="transaction-inquiry-md"}
- :magic-link[Incremental Authorization (Type 75)]{id="incremental-authorization-md"}
- :magic-link[Partial Authorization Reversal (Type 76)]{id="partial-authorization-reversal-md"}


## Sale transactions
A typical retail sale transaction occurs in the following circumstances:
- Cardholder is present
- Final amount is known
- Goods or services are delivered at the time of the sale
- The final amount can increase after using the Authorization Only (01) if, for example, a customer wants to add additional goods to the order. In such a case, the Incremental Authorization (75) is used. This is considered a two-part transaction.

:::notice{important}
Elavon does not recommend padding the Reference Number (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.
:::


## One-part transaction

Electronic authorization is obtained for the final amount (e.g., $50.00) by performing a Sale transaction (02). The transaction is closed.

## Two-part transaction

In a two-part transaction, authorization is obtained for the original known amount (e.g., $50.00) by performing an Authorization Only (01).

- The customer adds additional merchandise and the POS runs an Incremental Authorization (75) to adjust the original amount (e.g., $25.00). The transaction is closed with Prior Authorization (07) and the new final amount of $75.00.

- The advantages of this type of transaction include the authorization of an additional amount before closing the transaction, ideal interchange qualifications, ideal authorization-related chargeback protection, and the ability to use a token. Additionally, only one transaction posts to the cardholder statement, generating minimal transaction fees.

- The drawbacks include the potential for a transaction fee assessment, the Authorization Only and Prior Authorization must match exactly in order to be funded, and if for some reason the Prior Authorization is not processed, the Authorization Only will eventually expire, and the merchant will not be funded for the transaction.  Additionally, it may be considered an Additional Authorization for some cards and regions.

:::::notice{note}
If the approval was obtained from a voice authorization center, the sale request must be resubmitted with the approval code to the Fusebox with the Force Flag (Field 0012) set to 1. Another option is to submit a Prior Auth without the Force Flag, but sending the approval code in Field 0006.
:::::

## Credential on file transactions

Credential on file (COF) transactions occur when a cardholder gives express permission to the merchant to store their payment credentials for use on a future purchase.

The COF transaction category introduces two transaction types:

- Scheduled COF
- Unscheduled COF

These types of transactions also update card brand rules, including merchant disclosure requirements.

The stored credential transaction category covers all COF transactions, including:

- Cardholder-initiated stored credential transactions - no fixed schedule
- Industry Specific (delayed, no-show, incremental)

Retail credential on file transactions are indicated by Fields 0723, 0738, 0739, 0305, 0047, position 5, and 0054.

**Note:** Descriptions for Field 0047 position 5, Field 0054, and Field 0738 are explained :magic-link[below]{id="retail-scenarios#additional-field-information"}.

### Scenarios establishing a credential on file

Cardholder and Merchant agree to establish a credential on file at a retail business and perform the initial sale or authorization transaction. The COF may be used for future transactions initiated by the cardholder or merchant for payment of goods or services.

**Example:** Cardholder makes a purchase and agrees to place their card on file with the merchant for future use.

**Sale (02)**
- **Field 0723** - (F) First payment to establish credential on file
- **Field 0738** - Not req in request
- **Field 0739** - F101
- **Field 0047, position 5** - Any
- **Field 0054** - As entered
- **Initiated by** - Cardholder

**Auth Only (01)**
- **Field 0723** - (F) First payment to establish credential on file 
- **Field 0738** - Not req in request
- **Field 0739** - F101
- **Field 0047,  position 5** - Any 
- **Field 0054** - As entered
- **Initiated by** - Cardholder  

**Zero-dollar Auth Only (01)**
- **Field 0723** - (F) First payment to establish credential on file 
- **Field 0738** - Not req in request
- **Field 0739** - F101
- **Field 0047, position 5** - Any 
- **Field 0054** - As entered
- **Initiated by** - Cardholder

### Scenarios using a credential on file

#### Recurring payment
Merchant initiates a recurring payment for goods or services using the established COF based on a standing arrangement with the cardholder.

**Example:** Merchant performs a transaction for monthly gym membership fees.

**Sale (02)**
- **Field 0723** - (S) Subsequent payment
- **Field 0738** - Value from original transaction response 
- **Field 0739** - M101
- **Field 0047, position 5** - 9 
- **Field 0054** - 01
- **Initiated by** - Merchant 

**Auth Only (01)**
- **Field 0723** - (S) Subsequent payment
- **Field 0738** - Value from original transaction response
- **Field 0739** - M101 
- **Field 0047, position 5** - 9 
- **Field 0054** - 01
- **Initiated by** - Merchant       

#### Cardholder-initiated Sale
Cardholder initiates a single purchase using the established COF.

**Example:** Cardholder purchases another item for delivery from the retail store.

**Sale (02)**
- **Field 0723** - (U) Unscheduled payment
- **Field 0738** - Value from original transaction response
- **Field 0739** - C101
- **Field 0047, position 5** - A 
- **Field 0054** - 01
- **Initiated by** - Cardholder
- **Reason COF Used** - Unscheduled payment

**Auth Only (01)**
- **Field 0723** - (U) Unscheduled Payment
- **Field 0738** - Value from original transaction response
- **Field 0739** - C101
- **Field 0047, position 5** - A 
- **Field 0054** - 01
- **Initiated by** - Cardholder
- **Reason COF Used** - Unscheduled payment

#### Merchant-initiated Sale
Merchant initiates a transaction using the established COF based on an arrangement with the cardholder.

**Example:** Merchant delivers a single product that was ordered or provides a one-time service.

**Sale (02)**
- **Field 0723** - (U) Unscheduled payment
- **Field 0738** - Value from original transaction response
- **Field 0739** - M101
- **Field 0047, position 5** - A 
- **Field 0054** - 01
- **Initiated by** - Merchant
- **Reason COF Used** - Unscheduled payment

**Auth Only (01)**
- **Field 0723** - (U) Unscheduled payment
- **Field 0738** - Value from original transaction response
- **Field 0739** - M101
- **Field 0047, position 5** - A 
- **Field 0054** - 01
- **Initiated by** - Merchant
- **Reason COF Used** - Unscheduled payment

#### Return (09)
Cardholder or Merchant initiates a Return transaction using the established COF.

**Example:** Cardholder returns a product to the store for a refund.  Merchant has overcharged for previous goods purchased or service provided. 

**Return (09)** - Merchant-initiated
- **Field 0723** - (U) Unscheduled payment
- **Field 0738** - Value from original transaction response
- **Field 0739** - M101
- **Field 0047, position 5** - A 
- **Field 0054** - 01
- **Initiated by** - Merchant
- **Reason COF Used** - Unscheduled Return

**Return (09)** - Cardholder-initiated
- **Field 0723** - (U) Unscheduled payment
- **Field 0738** - Value from original transaction response
- **Field 0739** - M101
- **Field 0047, position 5** - A 
- **Field 0054** - 01
- **Initiated by** - Cardholder
- **Reason COF Used** - Unscheduled Return    


#### Incremental Auth (75) 
Merchant initiates an Incremental Authorization.

**Example:** Merchant requires an additional authorization amount for service provided, an incremental authorization is performed using the COF.
- **Field 0723** - (S)  Subsequent payment
 **Field 0738** - Value from original transaction response
- **Field 0739** - M101
- **Field 0047, position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Merchant
- **Reason COF Used** - Unscheduled additional Authorization

#### Prior Authorization (07)
Merchant initiates a Prior Authorization to complete a previous COF authorization only transaction.

**Example:** Merchant needs to submit a prior authorization for a COF transaction as part of their End of Day process and initiate settlement. 
- **Field 0723** - Same as initial Authorization Only (01)
- **Field 0738** - Value from original transaction response
- **Field 0739** - M101
- **Field 0047, position 5** - Same as initial Authorization
- **Field 0054** - 01
- **Initiated by** - Merchant
- **Reason COF Used** - Same as initial Authorization Only (01)

#### Void and Reversal
Merchant initiates a Reversal or Void of a previous COF transaction.

**Examples:**
- Merchant needs to cancel a previous transaction - a void or full reversal is performed.
- Merchant has overcharged on previous authorization transaction - a partial authorization is performed.

**Full Reversal (61), Partial Reversal (76), Void Sale (11), Void Return (17)**
- **Field 0723** - Same as original 
- **Field 0738** - Value from original transaction response
- **Field 0739** - M101
- **Field 0047, position 5** - Same as original 
- **Field 0054** - 01
- **Initiated by** - Merchant
- **Reason COF Used** - Same as original 

:::::notice{note}
While credential on file integrations are not third party processor specific, if a merchant changes third party processor with already established credentials on file, it is advised that the merchant re-establish those credentials with the new third party processor. 
:::::

## Additional field information

### POS Data Code - Field 0047 position 5 
#### Cardholder present value
0: Cardholder present
 

#### Cardholder not present values 
1: Cardholder not present (reason not specified)
2: Cardholder not present, mail order
3: Cardholder not present, telephone order 
4: Cardholder not present, Industry Practice 
5: Cardholder not present, eCommerce
A: Cardholder not present, Standing Authorization - Unscheduled
9: Cardholder not present, Standing Authorization – Recurring or Installment


### POS Entry Mode - Field 0054 
Entry mode of the transaction. Valid values:
01: Manual/Key Entry
05: EMV  
07: Contactless Chip Card 
80: EMV fall back to swipe 
90: Magnetic Stripe
91: Contactless Mag Stripe      

### Compliance Data Value - Field 0738 
This field contains the compliance data required to process credential on file transactions. The value is returned in the API response of the transaction that established the COF. This value must be retained by the merchant POS.
The stored value must be provided on in the API request by the POS on all transactions using the COF.

:::notice{important}
When attempting to establish a COF, if a value is not returned in response field 0738, the COF was not established. The merchant must treat this and any future transactions for this card as non-COF transactions. In this case, do not send 0723 and 0738 on those future transactions.
:::


## Retail invoice

The image below shows how the required receipt information can be incorporated into a standard retail invoice.

:::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/fusebox/retail.png" alt="retail" max-width="" max-height=""}
::: 



Retail scenarios

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