Re: [w3c/payment-request] Richer negotiation re: address redaction? (#842)

We should distinguish between data required for the payment and the data requested by the merchant as part of checkout.

E.g. Billing address is actually needed to authorize a card payment in many markets but we also provide a mechanism for the merchant to ask for an email address, phone number etc.

In this API we don't have any influence over payment specific data (either in the request or response). Billing address is used in the card payment flow but is:
 - unique to certain territories
 - used as a fraud indicator along with potentially many other data points that are decided by the card industry

If there is a desire to make it possible that data like email and phone number can be requested but marked as optional then we should look at changing the [`PaymentOptions` dictionary](https://w3c.github.io/payment-request/#paymentoptions-dictionary) so that the fields are not boolean but rather some enum like `'required' | 'optional' | undefined`.





-- 
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/payment-request/issues/842#issuecomment-469344472