Dynamic Currency Conversion (DCC) gives shoppers paying from abroad the choice to pay in your local currency or their own billing currency. The terminal detects when a card's billing currency differs from the local currency and prompts the shopper to choose — if they accept, Adyen applies the FX conversion (with markup) and that markup becomes revenue for the merchant; if they decline, the transaction runs in local currency as usual. No extra contract is required, and reporting is built in — but you must comply with card scheme disclosure and receipt rules to use it.
🛠 Pre-Requisites & Compliance
Before you begin:
Ensure you have the correct integration type — a Terminal API integration with payment terminals, or a standalone solution.
Verify you have an API credential with the "Management API — Terminal settings read and write" role to enable DCC via API. For DCC reports and overviews, make sure your Customer Area role includes "Merchant view POS Payment Report" and "Merchant POS Report."
If you plan to use DCC with pre-authorization/authorization adjustment, subscribe to Standard webhooks so you receive the final captured amount.
Confirm card scheme certification: DCC is only certified for Visa, Mastercard, and Maestro (contact chip and contactless, plus authorization adjustments).
Check currency and country/region support. Adyen supports a defined list of DCC currencies, and you can select a custom subset. DCC is live in almost all countries/regions where Adyen has a POS solution — the one notable exception is Brazil, where DCC isn't currently available.
Note that surcharging and DCC cannot both apply on the same transaction — if surcharge is active, Adyen will skip DCC.
🔧 Configuration Steps
Enable DCC, either via API call or by contacting Adyen Support/your Account Manager.
Choose your currency subset — decide which of the supported DCC currencies you want to offer shoppers, rather than defaulting to the full list.
Set up webhooks if you're using DCC alongside pre-authorization, so you can add the final captured amount from the CAPTURE webhook to the receipt or invoice.
Confirm your receipt setup:
Adyen-generated receipts automatically include the exchange rate, markup, both currency amounts, and a DCC acceptance statement — fully compliant out of the box.
If your integration generates its own receipts, you're responsible for including all of that same information yourself.
Turn on DCC reporting so DCC status and markup show up correctly (see Reporting below), and give your reconciliation process a heads-up — see the note below.
📊 Reporting & Reconciliation
Funds settle in the original transaction currency plus your share of the markup — not the converted amount. For example, a USD 100 transaction where the shopper accepts DCC and pays EUR 90 still settles as USD 100 (plus markup) to the merchant. This can affect automated reconciliation, so flag it before enabling.
The Received Payment Details report shows DCC as accepted, declined, or not offered.
The Settlement Details report includes a DCC Markup column, but it has to be manually enabled/configured to show.
The DCC Overview dashboard (Reports > Point of sale > Dashboards > Dynamic currency conversion) gives a management-level view of DCC usage, acceptance, and earnings across locations.
⚠️ Key Considerations for Valpay & Partners
DCC must always be an active, opt-in choice — never offered by default or on an opt-out basis. The cardholder has to take an action on an electronic screen or pin pad to accept it.
Both currency options must be presented neutrally: same size, same formatting, no verbal steering either way. Telling a shopper to "always decline DCC" (or the reverse) is a compliance violation.
Receipts must disclose the transaction amount in both currencies, the currency codes/symbols, the exchange rate, any markup or fees, and a statement that the cardholder was offered a currency choice — plus a statement that DCC was provided by the merchant. Adyen's own receipts handle this; custom receipts don't.
For hospitality with Express Checkout, the exchange rate can change between check-in and check-out — merchants need to disclose that at check-in so there are no surprises at the end.
Just because the feature is enabled doesn't mean a merchant is compliant — disclosure, receipts, and active choice are still on them to get right, and getting it wrong risks fines and loss of DCC privileges.
If you're rolling this out across multiple merchants, pilot with one merchant or store first, validate the terminal flow and reporting, then expand.