Dynamic Currency Conversion
Last updated
Was this helpful?
Last updated
Was this helpful?
Dynamic Currency Conversion (DCC) is a service that allows international customers to pay the purchase price in the local currency or their home currency. DCC is available for Worldline acceptance contracts with DCC expansion, via the Payment Page or the Transaction Interface flows. For this, the terminal used for making the payment request receives a base currency in which all transactions are settled. Via DCC, international customers are shown the purchase price in the base currency and the current exchange rate in their national currency. The customer can then decide the currency in which the payment is to be made. Saferpay automatically handles this step during the redirect.
The following payment methods do support DCC:
Mastercard (only via Worldline Acquiring)
Maestro (only via Worldline Acquiring)
Visa/V PAY (only via Worldline Acquiring)
While DCC itself is performed automatically, the card schemes require, that the merchant shares the DCC information to the payer, if DCC was performed. The merchant must share the following information:
The original amount and currency
The DCC amount and currency
The exchange rate
The markup rate
Besides the original transaction amount, which is set by the merchant beforehand, Saferpay does return all the DCC related information inside the DCC container, together with the rest of the transaction data, e.g. via the Payment Page Assert, or Transaction Authorize.
You -the merchant- have different options, when it comes to notifying the payer about DCC:
With the Payment Page, you can use its built in payer notification system by filling out the Notification.PayerEmail parameter. This will send a notification e-mail to the specified address, containing all necessary data. Alternatively, the parameter Notification.PayerDccReceiptEmail (API Spec version 1.35 or higher is required) can be used instead. In contrast to Notification.PayerEmail, an email is only sent when a DCC transaction was processed. If both parameters are used, only one email will still be sent (in the case of a DCC transaction, an email will be sent to the address in the Notification.PayerDccReceiptEmail parameter. If no DCC is performed, the address from the Notification.PayerEmail parameter will be used instead).
The parameter Notification.PayerDccReceiptEmail can be used (API Spec version 1.35 or higher is required).
An email is only sent in case of a DCC transaction, and in this case it replaces the Notfication.PayerEmail, containing only the necessary information for the DCC compliance.
Alternatively, you can of course send your own email and use the data provided by the API (API Spec version 1.27 or higher is required), as described above.
If #1, #2 and #3 are no options to you, if there were complications, or if you simply want to trigger the Saferpay notification again, you can also trigger the notification from the transaction details inside the Saferpay Backoffice.
You can access this information on a per terminalId basis, by logging into the Saferpay Backoffice and check the terminal-configuration under Settings => Terminals.
