Dynamic Currency Conversion (DCC) provides point-of-sale exchange rates to customers using a card issued in a currency other than the merchant’s base (or store) currency. For a more detailed explanation and step-by-step instructions, see our Dynamic Currency Conversion article.

The DCC feature is currently not available in the United States or Canada. 

The amount of information that must be presented to the customer, such as rate or margin, varies by Acquirer and Currency Conversion Processor. For more information, consult with Global Payments (or your Acquirer).

info

Rate Lookup

The Rate Lookup request determines if a card is eligible for DCC. If so, it returns the most up-to-date exchange rate, along with additional currency conversion information.

If the card is not eligible for DCC or the currency of the card is the same as the merchant's base, a result code of 105 will be returned. In this case, you can proceed with a regular authorization without including any DCC information.

api-dcc-rate
<?xml version="1.0" encoding="UTF-8"?>
<request type="dccrate" timestamp="20180613173251">
  <merchantid>MerchantId</merchantid>
  <account>internet</account>
  <orderid>HUrD-jsFSniaul_g0_z4YA</orderid>
  <amount currency="EUR">1001</amount>
  <card>
    <number>4006097467207025</number>
    <expdate>1218</expdate>
    <chname>James Mason</chname>
    <type>VISA</type>
  </card>
  <!-- Begin DCC Elements -->
  <dccinfo>
    <ccp>Currency Conversion Processor</ccp>
    <type>1</type>
    <ratetype>S</ratetype>
  </dccinfo>
  <!-- End DCC Elements -->
  <sha1hash>30e37e11a44ff9eee125933bd48455991820a7d7</sha1hash>
</request>

Authentication with DCC

Where the customer is offered a DCC choice, the authentication request requires the currency and amount the customer will pay. This is a requirement of 3D Secure (3DS) whereby the amount and currency authenticated should match the amount and currency authorized.

Where the customer declines the offer or is not offered DCC, the merchant amount and currency is all that is required.

Where the customer accepts the DCC offer, both the merchant amount and currency, and the customer amount and currency are required. 

When 3DS2 is used with an authorization request requiring the customer to authenticate the card used in a transaction, populate the additional fields in the 3DS2 authentication request.

authentication-with-dcc
"order": {
....
      "amount": "MerchantAmount",
      "currency": "MerchantCurrency",
....
      }
"currency_conversion": {
        "payer_amount": "CustomerChosenCurrencyAmount",
        "payer_currency": "CustomerChosenCurrency"

Authorization with DCC

After the customer decides which currency they want to use, you can send the additional DCC information in your authorization request.

api-authdcc

To process an authorization with DCC information, you must use the same Order ID as the DCC Rate Lookup request.

info
<?xml version="1.0" encoding="UTF-8"?>
<request type="auth" timestamp="20180613173251">
  <merchantid>MerchantId</merchantid>
  <account>internet</account>
  <orderid>HUrD-jsFSniaul_g0_z4YA</orderid>
  <amount currency="EUR">100</amount>
  <card>
    <number>4006097467207025</number>
    <expdate>0424</expdate>
    <chname>James Mason</chname>
    <type>VISA</type>
    <cvn>
      <number>123</number>
      <presind>1</presind>
    </cvn>
  </card>
  <autosettle flag="1"/>
  <!-- Begin DCC Elements -->
  <dccinfo>
    <ccp>Currency Conversion Processor</ccp>
    <type>1</type>
    <rate>1.6728</rate>
    <ratetype>S</ratetype>
    <amount currency="AUD">167</amount>
  </dccinfo>
  <!-- End DCC Elements -->
  <sha1hash>0a9256911d62e42058abc0a72ceece3fa7e81ba3</sha1hash>
</request>

Generate hash

Follow the steps in this section to build the request security hash, concatenate the specified fields and hash them using the SHA-1 algorithm, concatenate the hashed string with your Shared Secret, hash it again, and add the resulted string to the request.

generate-hash

In addition to SHA-1, you can also generate your hash using SHA-256. The resulting hash should be placed in the <sha256hash> tag instead of the <sha1hash> tag. For more information, contact our support team at ecomsupport@globalpay.com.

info

Build the Request hash

Use the drop-down arrow below to select a request type. After making a selection, follow the steps to build the request hash for that type.

Check hash

Follow the steps in this section to build the response security hash, concatenate the specified fields and hash them using the SHA-1 algorithm, concatenate the hashed string with your Shared Secret, hash it again, and add the resulted string to the request.

Check the Response hash

Use the drop-down arrow below to select a request type. After making a selection, follow the steps to check the response hash for that type.

check-hash
Internal Title
API Reference
Show Content Nav
On
Tags