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

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

- The COF transaction category introduces two transaction types:
  - Scheduled COF
  - Unscheduled COF
- The stored credential transaction scenarios in this section primarily cover cardholder-initiated on no fixed schedule and also lodging industry specific usage of delayed, no-show and incremental charges.
- Lodging credential on file transactions are indicated by key API fields: 0723, 0738, 0739, 0305, 0047 - position 5, 0054.


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

## Credential on file 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 

### Program code - Field 0305

Valid values:

- 1 - Lodging
- 2 - Assured Reservation (no show)
- 3 - Advanced Deposit
- 4 - Delayed Charge
- 5 - Express Service
- 6 - Assured Reservation. Defaults to 1.
Length: 1

Data Type: numeric


### Compliance Data Value - Field 0738
This field contains the compliance data required to process COF transactions. The value is returned in the API response of the transaction that established the COF. This value must be retained and provided in API request for subsequent transactions using the COF.

### Credential on file initiation and purpose indicator - Field 0739
This field indicates if cardholder or merchant initiated the credential on file transaction and for what purpose. Merchants should determine the most applicable indicator for the given transaction.
Valid values:
**Initial card on file transaction (Establishes COF)**
- F101 - Credential on file (unscheduled)
- F102 - Standing order (variable amount and fixed frequency)
- F103 - Subscription (fixed amount and frequency)
- F104 - Installment

**Cardholder initiated COF transactions (Cardholder uses established COF)**
- C101 - Credential on file
- C102 - Standing order (variable amount and fixed frequency)
- C103 - Subscription (fixed amount and frequency)
- C104 - Installment

**Merchant initiated COF transactions (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



**When Establishing a COF**
- API Request: Not Present
- API Response: Compliance Data Value - Merchant POS must retain for all transactions using a COF

**When Using a COF**
- API Request: Send retained from field 0738 of the original authorization transaction response when the COF was established.
- API Response: Value returned in 0738 is possibly a different value from the request. Merchant does not need to store this value.  

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



## Scenarios establishing a credential on file

### Auth Only (01) - Check In

Cardholder and merchant agree to establish a COF at a hotel and perform the initial authorization transaction. The COF may be used for future transactions initiated by the cardholder or merchant for payment of lodging stays or hotel services.

**Example:** Cardholder checks into a hotel and agrees to place their card on file for future transactions. Use the following fields for check in:

- **Field 0723** - F (First payment to establish COF)
- **Field 0738** - Not required in request.
- **Field 0739** - F101
- **Field 0305** - 1 
- **Field 0047 position 5** - 0
- **Field 0054** - As entered
- **Initiated by** - Cardholder

### Sale (02) 
Cardholder and merchant agree to establish a COF while making a reservation and perform the initial sale transaction. The COF may be used for future transactions initiated by the cardholder or merchant for payment of lodging stays or hotel services.

**Example:** Cardholder makes an advanced deposit, express service arrangement, or assured reservation for a hotel stay and agrees to place their card on file for future transactions.

**Sale (02) - Advanced Deposit**

- **Field 0723** - F (First payment to establish COF)
- **Field 0738** - Not required in request.
- **Field 0739** - F101
- **Field 0305** - 3 
- **Field 0047 position 5** - 4
- **Field 0054** - As entered
- **Initiated by** - Cardholder

**Sale (02) - Express Service**

- **Field 0723** - F (First payment to establish COF)
- **Field 0738** - Not required in request.
- **Field 0739** - F101
- **Field 0305** - 5 
- **Field 0047 position 5** - 4
- **Field 0054** - As entered
- **Initiated by** - Cardholder

**Sale (02) - Assured Reservation**

- **Field 0723** - F (First payment to establish COF)
- **Field 0738** - Not required in request.
- **Field 0739** - F101
- **Field 0305** - 6 
- **Field 0047 position 5** - 4
- **Field 0054** - As entered
- **Initiated by** - Cardholder

**Zero-dollar Auth Only (01)**

- **Field 0723** - F (First payment to establish COF)
- **Field 0738** - Not required in request.
- **Field 0739** - F101
- **Field 0305** - 1 
- **Field 0047 position 5** - 4
- **Field 0054** - As entered
- **Initiated by** - Cardholder

## Scenarios using a credential on file

Guest arrives at the hotel and agrees to use the COF information provided for the initial reservation to check into the hotel.

**Auth Only (01) - Check In**

- **Field 0723** - S (Subsequent Payment)
- **Field 0738** - Value from original transaction response.
- **Field 0739** - M101
- **Field 0305** - 1 
- **Field 0047 position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Merchant

**Auth Only (01) - Check In**

- **Field 0723** - U (Unscheduled Payment)
- **Field 0738** - Value from original transaction response.
- **Field 0739** - C101
- **Field 0305** - 1 
- **Field 0047 position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Cardholder


## Advanced deposit / Express service / Assured reservation

Cardholder or merchant initiates a transaction for an advanced deposit, express service arrangement or assured reservation using the established COF

**Example:** Cardholder makes an advanced deposit, express service arrangement or assured reservation for a hotel stay using their established COF.
Merchant requires a payment for an advanced deposit, express service arrangement or assured reservation, a transaction is performed using the cardholder’s COF.

**Sale (02) - Advanced deposit**

- **Field 0723** - S (Subsequent Payment)
- **Field 0738** - Value from original transaction response.
- **Field 0739** - M101
- **Field 0305** - 3
- **Field 0047 position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Merchant


**Sale (02) - Advanced deposit**

- **Field 0723** - U (Unscheduled Payment)
- **Field 0738** - Value from original transaction response.
- **Field 0739** - C101
- **Field 0305** - 3 
- **Field 0047 position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Cardholder


**Sale (02) - Express service**

- **Field 0723** - S (Subsequent Payment)
- **Field 0738** - Value from original transaction response.
- **Field 0739** - M101
- **Field 0305** - 5
- **Field 0047 position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Merchant


**Sale (02) - Express service**

- **Field 0723** - U (Unscheduled Payment)
- **Field 0738** - Value from original transaction response.
- **Field 0739** - C101
- **Field 0305** - 5 
- **Field 0047 position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Cardholder


**Sale (02) - Assured reservation**

- **Field 0723** - S (Subsequent Payment)
- **Field 0738** - Value from original transaction response.
- **Field 0739** - M101
- **Field 0305** - 6
- **Field 0047 position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Merchant


**Sale (02) - Assured reservation**

- **Field 0723** - U (Unscheduled Payment)
- **Field 0738** - Value from original transaction response.
- **Field 0739** - C101
- **Field 0305** - 6 
- **Field 0047 position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Cardholder


**Sale (02) - No Show**

Merchant initiates a transaction for a No Show charge.

**Example:** The cardholder did not appear for their hotel reservation, and the merchant performs a transaction using the established COF.

- **Field 0723** - S (Subsequent Payment)
- **Field 0738** - Value from original transaction response.
- **Field 0739** - M207
- **Field 0305** - 2
- **Field 0047 position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Merchant


**Sale (02) - Delayed charge**

Merchant initiates a transaction for a delayed charge.

**Example:** The cardholder owes an amount after check out for additional charges, the merchant performs a transaction using the COF.

- **Field 0723** - S (Subsequent Payment)
- **Field 0738** - Value from original transaction response.
- **Field 0739** - M206
- **Field 0305** - 4
- **Field 0047 position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Merchant


**Incremental Auth (75)**

Merchant initiates an Incremental Authorization.

**Example:** Merchant requires an additional authorization amount for the lodging stay or incidental charges, an incremental authorization is performed using the COF.

- **Field 0723** - S (Subsequent Payment)
- **Field 0738** - Value from original transaction response.
- **Field 0739** - M101
- **Field 0305** - 1
- **Field 0047 position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Merchant


**Return (09)**

Cardholder or merchant initiates a return using the established COF.

**Example:** Merchant has overcharged for a previous lodging stay and needs to refund a different amount the cardholder.

- **Field 0723** - S (Subsequent Payment)
- **Field 0738** - Value from original transaction response.
- **Field 0739** - M101
- **Field 0305** - 1
- **Field 0047 position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Merchant


**Example:** Cardholder cancels portion of a lodging stay and an amount is to be refunded.

- **Field 0723** - U (Unscheduled Payment)
- **Field 0738** - Value from original transaction response.
- **Field 0739** - C101
- **Field 0305** - 1 
- **Field 0047 position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Cardholder


**Prior Authorization (07)**

Merchant initiates a Prior Auth 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 Auth Only (01)
- **Field 0738** - Value from original transaction response.
- **Field 0739** - M101
- **Field 0047 position 5** - Same as initial Auth Only (01)
- **Field 0054** - 01
- **Initiated by** - Merchant
- **Reason COF Used** - Same as initial Auth Only (01)

## Voids and Reversals

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

**Example:** Merchant needs to cancel a previous transaction, a void or full reversal is performed. 
Merchant has over-charged on previous authorization transaction, a partial reversal is performed.

- **Transaction Type** - 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** - C101 or M101
- **Field 0305** - Same as original
- **Field 0047 position 5** - 4
- **Field 0054** - 01
- **Initiated by** - Same as original
- **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. 
:::::




Credential on file 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

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