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

Dynamic currency conversion (DCC) allows a cardholder to make a point-of-sale (POS) credit card purchase in a foreign country using his/her home currency.

DCC is the process of pre-converting the transaction amount to the cardholder currency before submitting the transaction for authorization with the card issuer. The currency conversion is calculated with the current day’s currency exchange rate instead of the exchange rate used post-submission by the card brand or the card issuer.
 
With DCC, international cardholders will know exactly what their total purchase in their home currency. Conversion rates are typically much more competitive than those at money exchange kiosks or third party currency conversion providers. Each receipt shows the purchase in business’ local currency, the conversion rate, plus the cardholder’s home currency amount. This makes it easier for travelers to reconcile purchases when paying card balances.
 
Elavon’s DCC service offers 66 conversion currencies.
Regions supported: **US & Canada**
Card Brands supported: **Visa & Mastercard**
Exclusion: **DCC is prohibited on contactless transaction at or below the CVM limit or ceiling limit.**
 
If DCC is enabled and a card reader with a display is used, the DCC confirmation will display automatically on the card reader, and the cardholder will have the choice of currency to pay. If cardholder chooses to pay in the home currency, the transaction outcome returned by CommerceSDK to the integrator will include information about the DCC transaction, such as the cardholder amount and currency, conversion rate, markup percent, and rate provider. This information must be included in receipts, along with a statement indicating cardholder agreed to pay in the home currency. See the following table for DCC attributes returned in the transaction response.
 
| | CWS | Java | Objective-C | C# |
| --- | --- | --- | --- | --- |
| **Transaction Response Element/Class** | paymentTransactionData | ECLCardTransactionOutcome | ECLCardTransactionOutcome | PaymentTransactionData |
| **DCC attributes** | dccAmount dccConversionRate dccMarkupPercent dccRateProvider | getDccAmount() getDccConversionRate() getDccMarkupPercent() getDccRateProvider() | dccAmount dccConversionRate dccMarkupPercent dccRateProvider | dccAmount dccConversionRate dccMarkupPercent dccRateProvider |

If using a card reader without a display (for example, Moby/5500) or for token transactions, CommerceSDK will return the DCC eligibility information via a callback to the integrating POS application. The application must display the DCC confirmation prompt to the cardholder. 

:::::notice{important}

***DCC screen requirements*** 

Some of the card readers supported by Commerce SDK do not have a display or a pin pad. To support DCC when connected to those devices, Commerce SDK will send DCC data to Integrator’s POS system through API callbacks to present DCC options to a cardholder on the POS screen instead of displaying it on a card reader. 

In this case Integrator’s POS system must clearly display the following details on the screen:

 - Purchase amount in the local and cardholder’s currency
 - Amounts with both currency symbols
 - Exchange rate used for the currency conversion
 - Additional fees or markup assessed

The Exchange Rate should be displayed as a ratio between the transaction in the merchant’s local currency or the cardholder’s home currency. 

    Example: 1 USD = 000.73485 GBP 

The Currency Conversion Fee percentage is required to be displayed directly under the Exchange Rate. 

The screen should give a choice to accept or decline currency conversion. The preferred option for customer choice would be to provide buttons with cardholder’s & business’s local currencies. 

Currency choice buttons should be of the same size, font, and color. Devices should not use colors such as red and green to influence cardholder’s choice. 

*Note:* When the device screen supports images, it is recommended that the appropriate flags associated with each currency are displayed. 
:::::

Once the cardholder chooses the currency to pay, the application must return the result to CommerceSDK and continue the transaction. See the following code samples for when the POS application needs to display the DCC confirmation prompt.

## Code samples

### CWS
 
When DCC decision is needed from the POS application, CWS sets property requiredInformation to "RequireDccConfirmation" in the response to `getPaymentTransactionStatus`. CWS also sets property dccEligibilityInfo with the DCC details.
 
#### Request
 
```json
{
 "requestId" : "75962782",
 "targetType" : "paymentGatewayConverge",
 "method" : "getPaymentTransactionStatus",
 "parameters" : {
 "paymentGatewayId" : "b9d5db2a-cd04-4dfa-adf3-dbdc6ce21123",
 "chanId" : "4357f858-59e4-46e6-96f0-a2e724bbba0c"
 }
}
```

#### Response
 

 ```json
 {
 "statusDetails" : "REQUEST_ACCEPTED",
 "requestId" : "75962782",
 "data" : {
 "paymentGatewayCommand" : {
 "completed" : false,
 "eventQueue" : [ {
 "timeStamp" : "1713975931682",
 "statusDetails" : "CARD_ELIGIBILITY_LOOKUP_COMPLETED"
 } ],
 "chanId" : "4357f858-59e4-46e6-96f0-a2e724bbba0c",
 "requiredInformation" : [ "RequireDccConfirmation" ],
 "dccEligibilityInfo" : {
 "dccToken" : "ee2952887f3eb0031d907df727d4a71010317474",
 "dccAmount" : {
 "baseAmount" : {
 "currencyCode" : "USD",
 "amount" : 100
 },
 "cardholderAmountString" : "0.84",
 "cardholderCurrency" : "GBP",
 "cardholderAmount" : 84
 },
 "dccRateProvider" : "US Bank",
 "dccConversionRate" : 0.83994,
 "dccMarkupPercent" : 3.25,
 "merchantAmount" : "1.00",
 "cardholderCurrency" : "GBP",
 "cardholderAmount" : "0.84",
 "merchantCurrency" : "USD"
 },
 "warnings" : [ ]
 }
 }
}
```

After getting DCC decision from the cardholder, integrating POS system can make `continuePaymentTransaction` request with decision **Accept**, **Reject**, or **Cancel**.
 

 #### Request
 
```json
{
 "requestId" : "75962783",
 "targetType" : "paymentGatewayConverge",
 "method" : "continuePaymentTransaction",
 "parameters" : {
 "RequireDccConfirmation" : "Accept",
 "paymentGatewayId" : "b9d5db2a-cd04-4dfa-adf3-dbdc6ce21123",
 "chanId" : "4357f858-59e4-46e6-96f0-a2e724bbba0c"
 }
}
```

### Java

```java
// Method requireDccDecision is introduced to abstract class ECLTransactionProcessingListener
// CSDK will ask integrating POS system to perform DCC confirmation through this method.
@Override
public void requireDccDecision(ECLTransactionInterface transaction, ECLTenderInterface tender,
 ECLDccEligibilityInfo dccEligibilityInfo, ECLTransactionProcessingCallbackListener transactionProcessingCallbackListener)
{
 // Integrating POS system sends the DCC decision back through interface transactionProcessingCallbackListener from the above method.
 // The first three parameters are the same ones from the above method,
 // and the last one is the decision. Allowed values for the last parameter are
 // ECLDccDecision.ACCEPT : Accept DCC and pay in cardholder's home currency
 // ECLDccDecision.REJECT : Reject DCC and pay in merchant's local currency
 // ECLDccDecision.CANCEL : Cancel the transaction
 ECLDccDecision decision = ...
 transactionProcessingCallbackListener.setDccDecision(transaction, tender, dccEligibilityInfo, decision);
}
```

### Objective-C

```objc
 // Implementation of [ECLTransactionProcessingDelegate shouldProvideDccDecision:tender:dccEligibilityInfo:]
// CSDK will ask integrating POS system to perform DCC confirmation through this method.
- (void)shouldProvideDccDecision:(id<ECLTransactionProtocol>)transaction tender:(id<ECLCardTenderProtocol>)cardTender dccEligibilityInfo:(ECLDccEligibilityInfo *)dccEligibilityInfo {
 // Set decision. Allowed values are
 // ECLDccDecisionAccept : Accept DCC and pay in cardholder's home currency
 // ECLDccDecisionReject : Reject DCC and pay in merchant's local currency
 // ECLDccDecisionCancel : Cancel the transaction
 cardTender.dccDecision = ...
 dispatch_async(dispatch_get_main_queue(), ^() {
 // use dispatch_async and call continueProcessingTransaction using your account reference (see sample app for more details)
 [[_account transactionProcessor] continueProcessingTransaction:transaction using:cardTender delegate:self];
 });
}
```

### C\#
 
```c#
// Assume a CWS object cws is created and we have a delegate MyPaymentComplete to receive transaction update.
cws.StartPaymentTransaction(bea, MyNotifyCWSEvent, MyPaymentComplete);
 
// The following code demonstrates how to handle DCC confirmation
public void MyPaymentComplete(PaymentTransactionResults paymentResults)
{
 // get required information
 String[] req = paymentResults.GetRequiredInformation();
 if (null != req)
 {
 Dictionary<string, string> info = new Dictionary<string, string>();
 for (int i = 0; i < req.Length; i++)
 {
 if (String.Compare(req[i], "RequireDccConfirmation", true) == 0)
 {
 info["RequireDccConfirmation"] = "Accept"; // can also set to "Reject" or "Cancel"
 }
 }
 
 if (info.Count != 0)
 {
 // Continue the transaction
 cws.StartContinuePaymentTransaction(m_PaymentGatewayId, chanId, info, MyNotifyCWSEvent, MyPaymentComplete);
 }
 }
}
```

Dynamic currency conversion

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

Elavon Commerce SDK Overview

Integration Methods

Commerce Web Services

Java (Windows)

Java (Android)

Objective-C (iOS)

System

Get Environment Information

Get Converge Account Information

Validate BMS Credentials

Payment Terminals

Payment Terminals Overview

Ingenico

iCMP

iPP320

iSC250

Lane/3000

Lane/3600

Lane/5000

Link/2500

Moby/5500

RP457c

Self/4000

Card Reader Connection

Device Connection Criteria

Card Reader Configuration

Get Card Reader Information

24-Hour Reboot

On-Demand

Get Device Status

Reset Card Reader

Reboot Card Reader

Encrypted Card Read

Cancel Card Read

Prompt PIN Entry

Capture Card Data

Get Customer Input

Phone Number

Volume Control

Set Shutdown Timeout

Signature Capture

Set Time Zone on Card Reader

TMS Update Check Time Window

SSL Certificate Update Process for Card Reader

Printers

Printers Overview

Get Printer Information

Print Receipts

On Demand Print Receipt

Transaction Types

Transactions Overview

Sale

Auth Only

Auth Only Increment

Convert Auth Only to Sale

Auth Only Reversal

Void

Linked Refund

Stand Alone Refund

Debit Balance Inquiry

Post Auth Tip Adjust

Continue Transaction

Cancel Transaction

Transaction Lookup

Processing Options

Processing Options Overview

Address Verification Service

Force Sale

Gratuity

Manual Card Data Entry

Merchant Transaction Reference

Partial Approval

Token Request

Pay with Token

Retrieve CVM Signature

Invoice Number