LogoLogo
BlogLogin
English
English
  • An Introduction to Saferpay
    • Licensing
      • Legacy licensing
    • Reconciliation
    • Acquirers & Payment Methods
    • Web Shop Plugins and certified partners
      • ePages Beyond
      • ePages NOW
      • Magento 2
      • Odoo
      • PrestaShop
        • PrestaShop User Guide
      • Salesforce Commerce Cloud
      • SAP Commerce Cloud
      • Shopware 6
        • Shopware 6 User Guide - German
        • Shopware 6 User Guide - English
      • WordPress WooCommerce
      • Shopify
    • Supported Languages
    • Common Saferpay terms - Glossary
  • News
    • Changes for transactions without customer presence
    • Changes for the Saferpay Hosted Forms, Fields and Payment Page
  • Quick Links
    • Web Shop Plugins and certified partners
    • Secure PayGate
    • User Administration
    • Payment Page Configuration
    • Risk Management
    • API Authentication
  • Interfaces
    • Payment API (aka JSON API)
    • Management API
    • Backoffice
      • The Home screen
      • Batch Processing
      • Transactions
        • Transaction Details
        • Batch Close
        • Declined transactions
        • Pending authorizations
        • Analytics
        • SEPA Refunds Export
        • Authorization & Payment
        • Credit
      • Risk Management
      • Secure PayGate / Payment Links
      • Secure Card Data
        • Secure Card Data Details
      • Settings
        • JSON API basic/Client Certificate authentication
        • User Administration
        • Payment Page Configuration
      • Online Support
      • User Profile
    • Saferpay OnSite
    • Feedback
  • Integration Guide
    • Integrating Saferpay
    • Ways of integration
      • General Information
        • Data Security and PCI DSS
        • Versioning
        • 3-D Secure
        • PSD2
        • Dynamic Currency Conversion
        • Iframe Integration and CSS
        • Fraud Intelligence
          • Silver
          • Fraud Intelligence Integration
      • Payment Page
        • Payment Page checklist
      • Transaction Interface
        • Recurring Payments
        • Refunds
          • SEPA Refunds
      • Capture and Daily Closing
        • Partial Captures
          • Marketplace
      • Secure Card Data - Tokenization
      • Saferpay Fields
      • Inquire Interfaces
      • Mobile Integration
      • Omni-Channel
      • Mail Phone Order
      • Error Handling
      • API Health Check
      • Saferpay API Specification
    • Payment Methods & Wallets
      • General and special cases
      • Account-to-Account Payments
      • Alipay+
      • Apple Pay
      • American Express
      • Bancontact
      • Billie
      • blik
      • Click to Pay
      • Diners Club International & Discover Card
      • eps
      • giropay
      • Google Pay
      • iDEAL 2.0
      • JCB
      • Klarna Payments
      • Maestro International
      • Mastercard
      • paydirekt
      • PayPal
      • PostFinance Pay
      • Przelewy24
      • Reka
      • SEPA Direct Debit
      • Sofort by Klarna
      • TWINT
      • UnionPay
      • Visa & V PAY
      • WeChat Pay
      • WL Crypto Payments
    • Testing
    • Go-Live
    • Frequently Asked Questions
    • Saferpay Demo
      • Saferpay Demo Environment
      • Saferpay Demo Shop
    • Support
    • Changelog
Powered by GitBook
On this page
  • DCC Compliance
  • How to gather the DCC information via API
  • Payer notification options
  • Find out if DCC is active

Was this helpful?

  1. Integration Guide
  2. Ways of integration
  3. General Information

Dynamic Currency Conversion

PreviousPSD2NextIframe Integration and CSS

Last updated 1 year ago

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.

Supported Payment Methods

The following payment methods do support DCC:

  • Mastercard (only via Worldline Acquiring)

  • Maestro (only via Worldline Acquiring)

  • Visa/V PAY (only via Worldline Acquiring)

Example of the DCC Screen

DCC Compliance

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

How to gather the DCC information via API

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.

Example of a DCC response

"Dcc": {
    "PayerAmount": {
      "Value": "352",
      "CurrencyCode": "JPY"
    },
    "Markup": "3%",
    "ExchangeRate": "1.234"
  }

Payer notification options

You -the merchant- have different options, when it comes to notifying the payer about DCC:

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

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

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

Find out if DCC is active

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 .

You can access this information on a per basis, by logging into the Saferpay Backoffice and check the terminal-configuration under Settings => Terminals.

trigger the notification from the transaction details inside the Saferpay Backoffice
(click to enlarge)
terminalId