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

DCC transaction receipts must contain:

 - The price of the goods or services in the merchant’s home currency, accompanied by the currency symbol or code next to the amount.

 - The total price in the transaction currency accompanied by the words “Transaction Currency” and the currency symbol or code next to the amount.

 - The exchange rate used to convert the total price from the merchant’s home currency to the transaction currency.

- Any mark-up or commission included in the exchange rate as an amount or a percentage. This information may be shown as a separate line item or in the disclosure verbiage on the transaction receipt.

 - An “I accept” check-box indicating the cardholder’s acceptance of the currency conversion.

 - A statement in an area easily seen by the cardholder stating that DCC is offered by the merchant.

## Additional transaction receipt requirements



### eCommerce merchants

- An “I accept” check-box indicating the cardholder’s acceptance of the currency conversion. This box may be pre-filled based on the “I Accept” button selection from the payment page; or

- A statement indicating that the cardholder has been offered a choice of currencies including the merchant’s local currency.

### Lodging merchants – Priority Checkout (formerly known as Express Service transactions):

- Receipts for delayed and amended charges should be delivered to the cardholder within three business days of the charge.



## Special requirements for eCommerce and cardholder-activated terminals

- Screen messages at unattended POS terminals must not require the cardholder to select “Yes” or “No” when choosing currency conversion. Indirect means, such as the colors red and green, must not be used to influence the cardholder’s choice.

## Language requirements for DCC receipts

- Visa recommends that the DCC receipt be printed in English. As part of the DCC certification with Visa, all example sales receipts will be required to be translated to English.

::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/fusebox/image4.png" alt="dcc example receipt"}


## Example disclosure language:

"I have been offered the choice of currencies for payment including the merchant’s local currency. My decision to accept the currency conversion on this transaction is final. Currency conversion is conducted by the Business Name. Cardholder expressly agrees to the transaction receipt information by marking the “Accept” box."

In the lodging industry, receipts are not generally produced until the customer checks out and the receipt is in the form of a folio statement. DCC requires a disclosure document be provided to the customer when they opt-in to DCC. The following is a sample of what should be provided in this document.

::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/fusebox/image5.png" alt="dcc example disclosure"}
 

## DCC receipt data

The following fields have been identified as being required on a DCC receipt.

**140 (Merchant Currency)**
- Description: Merchant transaction currency code
- Approval: Yes
- Decline: No

**142 (Cardholder Currency)**
- Description: Cardholder ISO currency code 
- Approval: Yes
- Decline: No

**144 (Converted Currency Amount)**
- Description: Cardholder transaction amount
- Approval: Yes
- Decline: No 

**150 (DCC Rate)**
- Description: Foreign currency exchange rate
- Approval: Yes
- Decline: No 

**151 (DCC Indicator)**
- Description: DCC eligible terminal indicator. Valid values include: 0 = Not DCC Capable 1 = DCC Capable and cardholder has opted -in 2 = DCC BIN match, but no corresponding rate for that currency 3 = DCC capable, but cardholder has opted-out. 
- Approval: No
- Decline: No 

**159 (DCC Exponent)**
- Description: Number of exponent digits in the DCC rate 
- Approval: Yes
- Decline: No 
 
**164 (DCC File ID)**
- Description: In the case where Simplify or the payment application performs the DCC Inquiry on behalf of the POS/PMS, they will need to populate the value from field 7007 in the transaction type 46 response into field 0164 in the authorization response to the PMS/POS. PMS/POS store this value for receipt printing and research of previous rates 
- Approval: Yes
- Decline: No 

**165 (DCC Markup Percentage)**
- Description: DCC rate markup with the 2 implied decimals (3.25% is 0325). 
- Approval: Yes
- Decline: No 
 
**166 (DCC Rate Provider)** 
- Description: Indicates the name of the currency rate provider 
- Approval: Yes
- Decline: No 

**7007 (Transaction Identifier)** 
- Description: This field will be a unique identifier to reference the transaction. We advise that the PMS/POS store this value from the DCC Inquiry response for receipt printing and research of previous rates in financial transactions. 
- Approval: Yes
- Decline: Yes 
 
**7007 (Check Box)** 
- Description: The receipt should contain a check box marked appropriately to identify if the cardholder has opted in or opted out.
- Approval: Yes
- Decline: No

DCC receipt requirements

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

Gift and stored value cards

Gift and stored value card transactions

Gift and stored value card API fields