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, the cardholder is 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. 

With the dynamic currency option: 

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

### Step 1. Implement transaction flow

You must provide the choice to the cardholder to accept or decline the DCC service and display all relevant information to make an informed decision. The following steps outline the process of sending a DCC transaction with XML API:

1. The website or POS application collects the payment information. 
2. Cardholder enters or swipes a Visa or MasterCard card at the checkout. Use a :magic-link[DCC test card]{id="test-cards#services"}.
3. Converge determines if the card is a foreign card.
4. Converge returns a decision response providing a transaction ID, rates, markup, and currency information.
5. The website or POS application displays the option to the cardholder with the information returned by Converge
6. The cardholder makes a choice at the website or POS application:
 - If the cardholder opts to process in home currency, the website or POS application sends the transaction ID for that transaction with DCC option value of Y.
 - If the cardholder opts to process in merchant currency, the website or POS application sends the transaction ID for that transaction with DCC option value of N.
7. 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 in :magic-link[/processxml.do.]{id="api-reference#tag/Process-Transaction-Online"} 

- `ccsale` (Credit card sale)
- `ccauthonly` (Credit card authorization)

:::::notice{note}

There is a 15-minute window given to allow the website or POS application to send the option.
:::::
### Step 2. Receipts

**Receipt requirements for VISA**

- 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 that indicates the cardholder’s acceptance of the currency conversion.
- A statement in an area easily seen by the cardholder that states that DCC is offered by the merchant.

**Receipt requirements for MasterCard**

- Pre-conversion currency and amount.
- Conversion rate or method.
- Post-conversion currency and amount.
- A prescribed statement, “I have chosen not to use the MasterCard currency conversion method and I will have no recourse against MasterCard concerning currency conversion or its disclosure.”

**Special requirements for internet**

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

#### Receipt example

**Merchant Copy**

Header1 FRIENDLY TERMINAL XXXXXXXXXXXXXXXXXXXXX Date: 11/04/2010 11:07:30 AM CREDIT CARD SALE CARD DATA: **********0002 S TRANSACTION CURRENCY: JPY CONVERSION RATE: 85.05321 CONVERSION MARKUP: 3.25% MERCHANT AMOUNT: $2.00 USD TRANSACTION AMOUNT: ¥170.00 JPY APPROVAL CD: N19586 CLERK ID: my_merchant_id RECORD #: 001 I HAVE BEEN OFFERED THE CHOICE OF CURRENCIES FOR PAYMENT INCLUDING THE MERCHANT'S LOCAL CURRENCY. MY DECISION TO ACCEPT CURRENCY CONVERSION ON THIS TRANSACTION IS FINAL. I ACCEPT THE RATE OF CONVERSION,(INCLUSIVE OF CONVERSION FEE 3.25%), FINAL AMOUNT, AND THAT THE FINAL SETTLED TRANSACTION CURRENCY IS {JPY}. I UNDERSTAND THAT VISA HAS A CURRENCY CONVERSION PROCESS, AND THAT I HAVE CHOSEN NOT TO USE THE VISA CURRENCY CONVERSION PROCESS. CURRENCY CONVERSION IS CONDUCTED BY THE MERCHANT AND IS NOT ASSOCIATED WITH OR ENDORSED BY VISA. I AGREE TO THE TRANSACTION RECEIPT INFORMATION BY MARKING THE ACCEPT BOX BELOW. [ ] I ACCEPT X_________________________________________________ JPY STANDARD VI Trailer1 Merchant Copy 

**Customer Copy**

Header1 FRIENDLY TERMINAL XXXXXXXXXXXXXXXXXXXXX Date: 11/04/2010 11:07:30 AM CREDIT CARD SALE CARD DATA: **********0002 S TRANSACTION CURRENCY: JPY CONVERSION RATE: 85.05321 CONVERSION MARKUP: 3.25% MERCHANT AMOUNT: $2.00 USD TRANSACTION AMOUNT: ¥170.00 JPY APPROVAL CD: N19586 CLERK ID: my_merchant_id RECORD #: 001 I HAVE BEEN OFFERED THE CHOICE OF CURRENCIES FOR PAYMENT INCLUDING THE MERCHANT'S LOCAL CURRENCY. MY DECISION TO ACCEPT CURRENCY CONVERSION ON THIS TRANSACTION IS FINAL. I ACCEPT THE RATE OF CONVERSION,(INCLUSIVE OF CONVERSION FEE 3.25%), FINAL AMOUNT, AND THAT THE FINAL SETTLED TRANSACTION CURRENCY IS {JPY}. I UNDERSTAND THAT VISA HAS A CURRENCY CONVERSION PROCESS, AND THAT I HAVE CHOSEN NOT TO USE THE VISA CURRENCY CONVERSION PROCESS. CURRENCY CONVERSION IS CONDUCTED BY THE MERCHANT AND IS NOT ASSOCIATED WITH OR ENDORSED BY VISA. Trailer1 Customer Copy

### Sample DCC credit card transaction

**Send a ccsale request**

```curl
curl -X POST 'https://api.demo.convergepay.com/VirtualMerchantDemo/processxml.do' \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 
'xmldata= 
<txn>
 <ssl_transaction_type>ccsale</ssl_transaction_type>
 <ssl_account_id>my_account_id</ssl_account_id>
 <ssl_user_id>my_user_id</ssl_user_id>
 <ssl_pin>my_pin</ssl_pin>
 <ssl_vendor_id>my_vendor_id</ssl_vendor_id>
 <ssl_card_number>0000000000000000</ssl_card_number>
 <ssl_exp_date>1219</ssl_exp_date>
 <ssl_amount>1.00</ssl_amount>
</txn>'
```

**Receive a DCC decision response**

```XML
<txn>
 <id>ekU9j0L0iFO9m9FELAqK8E6</id>
 <ssl_txn_currency_code>EUR</ssl_txn_currency_code>
 <ssl_markup>3.25</ssl_markup>
 <ssl_conversion_rate>.76373</ssl_conversion_rate>
 <ssl_amount>1.00</ssl_amount>
 <ssl_cardholder_amount>0.76</ssl_cardholder_amount> <dccoption>
 <option label="Please charge my purchase in my home currency">Y</option>
 <option label="Do not charge me in my home currency. charge my purchase in US dollars">N</option>
 </dccoption>
</txn>
```

**Cardholder accepts DCC and second request sent requesting card to be charged in foreign currency**

```curl
curl -X POST 'https://api.demo.convergepay.com/VirtualMerchantDemo/processxml.do' \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 
'xmldata= 
 <txn>
 <ID>ekU9j0L0iFO9m9FELAqK8E6</ID>
 <dccoption>Y</dccoption>
 </txn>'
```

**Receive a final response and print receipt**

```XML
<txn>
 <ssl_card_number>00********0000</ssl_card_number>
 <ssl_exp_date>1219</ssl_exp_date>
 <ssl_amount>1.00</ssl_amount>
 <ssl_cardholder_amount>0.76</ssl_cardholder_amount>
 <ssl_cardholder_currency>EUR</ssl_cardholder_currency>
 <ssl_conversion_rate>.76373</ssl_conversion_rate>
 <ssl_markup>3.25</ssl_markup>
 <ssl_invoice_number/>
 <ssl_result>0</ssl_result>
 <ssl_result_message>APPROVAL</ssl_result_message>
 <ssl_txn_id>101641221295DB876-F2A9-7B6A-B173-2737983B7693</ssl_txn_id>
 <ssl_approval_code>N05465</ssl_approval_code>
 <ssl_txn_time>01/20/2011 01:05:44 PM</ssl_txn_time>
</txn>
```

**Cardholder declines DCC and second request sent requesting card to be charged in merchant currency** 

```curl
curl -X POST 'https://api.demo.convergepay.com/VirtualMerchantDemo/processxml.do' \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 
'xmldata= 
<txn>
 <ID>iQ4AezhcjmJznh3BYLZ0-W9</ID>
 <dccoption>N</dccoption>
</txn>'
```

**Receive a final response**

```XML
<txn>
 <ssl_card_number>00********0000</ssl_card_number>
 <ssl_exp_date>1219</ssl_exp_date>
 <ssl_amount>1.00</ssl_amount>
 <ssl_result>0</ssl_result>
 <ssl_result_message>APPROVAL</ssl_result_message>
 <ssl_txn_id>101641221593ACBA6-BAFD-76B7-4948- B3DE68CFD0CC</ssl_txn_id>
 <ssl_approval_code>CMC142</ssl_approval_code>
 <ssl_account_balance>1.00</ssl_account_balance>
 <ssl_txn_time>01/20/2011 01:07:23 PM</ssl_txn_time>
</txn>
```

## Multi-currency conversion - MCC 

Multi-currency conversion allows you to sell products and services in a variety of currencies but receive their 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, then the following requirements must be met: 

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

With the multi-currency option: 

- 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[/processxml.do]{id="api-reference#tag/Process-Transaction-Online"} 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: 

- `ccsale` (Credit card sale) 
- `ccauthonly` (Credit card authorization only) 
- `ccimport` (Batch import transaction)

### Sample MCC credit card transaction

```curl
curl -X POST 'https://api.demo.convergepay.com/VirtualMerchantDemo/processxml.do' \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 
'xmldata= 
<txn>
 <ssl_transaction_type>ccsale</ssl_transaction_type>
 <ssl_account_id>my_account_id</ssl_account_id>
 <ssl_user_id>my_user_id</ssl_user_id>
 <ssl_pin>my_pin</ssl_pin>
 <ssl_vendor_id>my_vendor_id</ssl_vendor_id>
 <ssl_card_number>0000000000000000</ssl_card_number>
 <ssl_exp_date>1219</ssl_exp_date>
 <ssl_amount>200</ssl_amount>
 <ssl_transaction_currency>JPY</ssl_transaction_currency>
</txn>'
```

**Response**

```XML
xmldata=
 <txn>
 <ssl_card_number>00********0000</ssl_card_number>
 <ssl_exp_date>1219</ssl_exp_date>
 <ssl_amount>200</ssl_amount>
 <ssl_transaction_currency>JPY</ssl_transaction_currency>
 <ssl_result>0</ssl_result>
 <ssl_result_message>APPROVAL</ssl_result_message>
 <ssl_txn_id>AA47AE-BD32FF54-BE12-4046-98E9- F78E9D75212D</ssl_txn_id>
 <ssl_approval_code>N05465</ssl_approval_code>
 <ssl_txn_time>11/19/2013 12:02:29 AM</ssl_txn_time>
 </txn>
```

Currency conversion