Multi-Currency Conversion - MCC
Multi-Currency Conversion allows the merchant 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.
When a terminal is set up with the Multi-Currency option:
- By default, the terminal can process transactions in the following currencies: US Dollar (USD), Canadian Dollar (CAD), Pound Sterling (GBP), Australian Dollar (AUD), Euro (EUR), and Japanese Yen (YEN).
- The terminal only supports MCC transactions paid with MasterCard and Visa. For other card brands, the terminal can only process transactions using the USD or CAD currency.
- The terminal only allows auto-settlement.
The following Credit Card transactions support MCC:
ccsale
(Sale)ccauthonly
(Auth Only)ccforce
(Force)ccimport
(Batch Import)
Transaction Processing
To process a credit card transaction for multi-currency conversion, the transaction request must include the ssl_transaction_currency
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.
If the original transaction needs adjustment (through cccomplete
, ccvoid
, ccupdatetip
or ccreturn
), exclude the ssl_transaction_currency
parameter from the request. The mentioned transactions will carry the original value of the transaction currency in the request.
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 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.
Currency Code | Currency Name | Exponents |
---|---|---|
AED | United Arab Emirates Dirham | 2 |
ANG | Netherlands Antillean Guilder | 2 |
ARS | Argentine Peso | 2 |
AWG | Aruban Florin | 2 |
AZN | Azerbaijani Manat | 2 |
BBD | Barbados Dollar | 2 |
BDT | Bangladeshi Taka | 2 |
BGN | Bulgarian Lev | 2 |
BHD | Bahraini Dinar | 3 |
BMD | Bermudian Dollar | 2 |
BOB | Bolivian Boliviano | 2 |
BRL | Brazilian Real | 2 |
BSD | Bahamian Dollar | 2 |
BWP | Botswana Pula | 2 |
CAD | Canadian Dollar | 2 |
CDF | Congolese Franc | 2 |
CHF | Swiss Franc | 2 |
CLP | Chilean Peso | 0 |
CNY | China Yuan Renminbi | 2 |
COP | Colombian Peso | 2 |
CRC | Costa Rican Colon | 2 |
CZK | Czech Koruna | 2 |
DKK | Danish Krone | 2 |
DOP | Dominican Peso | 2 |
DZD | Algerian Dinar | 2 |
EEK | Estonian Kroon | 2 |
EGP | Egyptian Pound | 2 |
ETB | Ethiopian Birr | 2 |
EUR | Euro | 2 |
FJD | Fiji Dollar | 2 |
GBP | Pound Sterling | 2 |
GTQ | Guatemalan Quetzal | 2 |
HKD | Hong Kong Dollar | 2 |
HRK | Croatian Kuna | 2 |
HTG | Haitian Gourde | 2 |
HUF | Hungarian Forint | 2 |
IDR | Indonesian Rupiah | 2 |
ILS | (New) Israeli Shekel | 2 |
INR | Indian Rupee | 2 |
IRR | Iranian Rial | 2 |
ISK | Icelandic Króna | 0 |
JMD | Jamaican Dollar | 2 |
JOD | Jordanian Dinar | 3 |
JPY | Japanese Yen | 0 |
KES | Kenyan Shilling | 2 |
KRW | South Korean Won | 0 |
KWD | Kuwaiti Dinar | 3 |
KZT | Kazakhstan Tenge | 2 |
LBP | Lebanese Pound | 2 |
LKR | Sri Lanka Rupee | 2 |
LSL | Lesotho Loti | 2 |
LTL | Lithuanian Litas | 2 |
LVL | Latvian Lats | 2 |
LYD | Libyan Dinar | 3 |
MAD | Moroccan Dirham | 2 |
MKD | Macedonian Denar | 2 |
MUR | Mauritian Rupee | 2 |
MWK | Malawian Kwacha | 2 |
MXN | Mexican Peso | 2 |
MYR | Malaysian Ringgit | 2 |
NAD | Namibian Dollar | 2 |
NGN | Nigerian Naira | 2 |
NOK | Norwegian Krone | 2 |
NPR | Nepalese Rupee | 2 |
NZD | New Zealand Dollar | 2 |
OMR | Omani Rial | 3 |
PEN | Peruvian Nuevo Sol | 2 |
PHP | Philippine Peso | 2 |
PKR | Pakistani Rupee | 2 |
PLN | Polish Zloty | 2 |
QAR | Qatari Rial | 2 |
RON | Romanian New Leu | 2 |
RSD | Serbian Dinar | 2 |
RUB | Russian Ruble | 2 |
SAR | Saudi Riyal | 2 |
SEK | Swedish Krona | 2 |
SGD | Singapore Dollar | 2 |
SYP | Syrian Pound | 2 |
THB | Thai Baht | 2 |
TND | Tunisian Dinar | 3 |
TRY | (New) Turkish Lira | 2 |
TTD | Trinidad and Tobago Dollar | 2 |
TWD | New Taiwan Dollar | 2 |
UAH | Ukrainian Hryvnia | 2 |
USD | US Dollar | 2 |
VEF | Venezuelan Bolivar Fuerte | 2 |
VND | Vietnamese Don | 0 |
XAF | Gabon Franc | 0 |
XCD | East Caribbean Dollar | 2 |
XOF | Ivory Coast Franc | 0 |
XPF | French Polynesian Franc | 0 |
ZAR | South African Rand | 2 |
ZMK | Zambian Kwacha | 2 |
ZWL | Zimbabwe Dollar | 2 |
note
- For JPY, there are no exponents after the decimal point. Any number after the decimal point is ignored.
- For ISK, the currency decimalization is changed from ‘2’ to ‘0’ for Authorizations and Submissions.
Example
important
- In this example, you will have to change the data values, such as
my_merchant_id
,my_user_id
,my_pin
, and transaction data to match your Converge account and meet the needs of your website. - Code samples provided are for demonstration only and should not be used for live transactions. All sensitive merchant data, including transaction amounts and your Converge credentials, should be placed in server side code.
Request
xmldata=
<txn>
<ssl_merchant_id>my_merchant_id</ssl_merchant_id>
<ssl_user_id>my_user_id</ssl_user_id>
<ssl_pin>my_pin</ssl_pin>
<ssl_test_mode>false</ssl_test_mode>
<ssl_transaction_type>ccsale</ssl_transaction_type>
<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
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>