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

Hi,

One type of payment that doesn't appear to be fully catered for is DCC.  For those who haven't seen this, this is where a customer has the option to pay in their credit card's currency rather than the local currency.

The credit card companies allow this, but have strict Compliance guidelines to protect the consumer.
Essentially, the DCC offer must include:

1. the exchange rate being applied
2. the margin being added to the foreign exchange rate (and in some cases the rate source)
3. disclaimer text (varies by credit card type).

So, for example--

An American customer (currency = USD) buying from a UK merchant (currency = GBP).
The customer selects GBP 75 worth of goods and enters their Visa card details.
The merchant gives the customer a DCC payment option such as--

Pay in your home currency (USD) 112.01
Exchange rate of 1.493 is based on X Bank Rate plus a 3% standard margin.  Cardholder choice is final.  The DCC service is provided by CompanyY.

To properly process the payment, a DCC provider will need:

1. the base currency (GBP), 
2. base amount (GBP 75), 
3. foreign/transaction currency (USD), 
4. foreign/transaction amount (USD 112.01).

Will the proposed payment standard accommodate the above process?

>From looking at the draft specification, there appear to be some optional data fields for the payment that may accommodate the processing needs of a DCC provider.  Am I interpreting these correctly?

But, I think support for the DCC offer would be needed as optional fields to allow for DCC offers to be made.

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