Re: [w3c/browser-payment-api] Dynamic Currency Conversion (DCC) Support (#178)

In most cases, DCC is achieved through a message flow between the Merchant PSP (acquirer) and the DCC provider chosen by the acquirer. At the acceptor level (thus for the customer), there are the following impacts: 1/ there is an intermediary pseudo payment response displaying to the customer the exchange rate conditions and asking him whether he is OK or not for DCC.  2/ If he is consents to the DCC proposal, the usual authorisation process is carried on. At authorisation response step, it is mandatory to provide to the customer, via the authorisation payment response message, the exchange rate conditions that were applied (currencies, rates, mark-up on the rate, fees...). So, the message flow includes an extra step, and supplementary data have to conveyed to the customer.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/178#issuecomment-221914533