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 

Converge uses Elavon conversion tools to process Dynamic Currency Conversion (DCC) for merchants. 

The merchant is pricing in USD or CAD, but when the card is entered and is determined to be DCC eligible, Cardholder is then given a choice to pay with their currency (foreign); this agreed currency becomes the transaction currency, regardless of the merchant’s pricing currency. Cardholder accepts to pay with their local currency and the conversion rates associated with it: 

- Transactions are funded in one single currency where the merchant currency can be USD or CAD. 
- Cardholders are prompted for a choice to pay in their local currency (foreign) 

**Requirements**

If you want to use DCC in Converge, then the following requirements must be met: 

- DCC is enabled. Verify by calling :magic-link[/VirtualMerchantDemo/accountxml.do]{id="api-reference#tag/Terminal-Management"} with transaction type `terminalsetup`. 
- Region set to USA or Canada. 

When the Dynamic-Currency option is enabled: 

- DCC supports MasterCard and Visa transactions only. Other card types will process as normal and will not trigger DCC processing. 
- The conversion triggers when the card is entered, and rates will be presented for any of the following currencies: US Dollar, Canadian Dollar, Pound Sterling, Australian Dollar, Euro, and Japanese Yen. 

### Transaction flow

1. HPP collects the payment information. 
2. Cardholder enters a Visa or MasterCard card at the checkout. Use a :magic-link[DCC test card.]{id="test-cards#services"}
3. Converge will determine if the card is a foreign card. 
4. HPP displays the option to the cardholder with the information returned for conversion. 
5. The cardholder makes a choice: 
 - Selects to process in home currency. 
 - Selects to process in merchant currency. 
6. Converge processes the transaction and returns a response to the website displaying the results with conversion rates and amounts agreed on. 

The following transaction types are supported when processing DCC transactions: 

- Credit Card Sale
- Credit Card Authorization

Once you enable this feature, customers who arrive at your hosted payment page will automatically be prompted by DCC if their card is foreign.

## Multi-currency conversion - MCC 

Multi-currency conversion allows you to sell products and services in a variety of currencies but receive funding from Elavon in just one currency. 

MCC is beneficial to merchants with websites that target particular demographics in countries other than their own. 

For example, a US merchant's website targets customers in Europe, displays prices in Euro (EUR), processes payments in EUR but clears payments in US Dollars (USD) through a US bank account. Another example is a Canadian merchant's website that targets customers in Australia, processes transactions in Australian Dollars (AUD), and deposits payments in Canadian Dollars (CAD) to a Canadian bank account. 

**Requirements**

If you want to use MCC in Converge, the following requirements must be met: 

- MCC enabled. Verify by calling :magic-link[/VirtualMerchantDemo/accountxml.do]{id="api-reference#tag/Terminal-Management"} with transaction type `terminalsetup`. 
- Region set to USA or Canada. 

When Multi-Currency option is enabled: 

- Can process transactions in various currencies listed in the :magic-link[table]{id="supported-dcc-currency-codes"}. 
- Only supports MCC transactions paid with MasterCard and Visa. For other card brands, it can only process transactions using the USD or CAD currency. 
- Only allows auto-settlement. 

### Transaction processing

To process a credit card transaction for multi-currency conversion, the :magic-link[/hosted-payments/transaction_token]{id="api-reference#tag/Request-Session-Token"} must include the :magic-link[`ssl_transaction_currency`]{id="supported-dcc-currency-codes"} and  `ssl_amount`  parameters. 

Converge uses the exchange rates provided by Elavon's designated currency exchange desk provider to convert the transaction amount from the submission currency to the single funding currency on the merchant's account. 

For the `ssl_amount` value, use the number of decimal places that corresponds to the currency code passed to the  `ssl_transaction_currency` parameter. Most currencies support 2 exponents (decimal places) except for the few of them mentioned below. But Converge automatically rounds up (1.236 to 1.24) or rounds down (1.235 to 1.23) the transaction amount to 2 exponents. 

The following credit card transactions support MCC: 

- Credit Card Sale 
- Credit Card Authorization Only

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

Overview

API reference

Integration guide

Customize payment page

Payment types

Take a payment

Transaction management

Additional options

Wallets

Point of sale lending

3D Secure 2

Doing Business As

Export scripts

Fees

Shopping cart plugins

Billing and invoicing / Hospitality

Authentication

Invoice lifecycle

Managing invoices

Status and error codes

Elavon domains and IP addresses

Error codes

Response codes

Supported MCC currency codes

Test cards

Release notes