Re: [w3c/browser-payment-api] Should the merchant be able to request your email and recipient phone number (#1)

I want to highlight that the data being requested here is intended to be gathered by the browser BEFORE the payment request is passed to the payment app.

Effectively there are two channels between the user and the website:
 1. website -> browser -> user (interactive) 
 2. website -> browser (purely as proxy) -> payment app -> user

In PR #133 I have made this distinction clearer so that we don't corrupt the payment request with data requests that are part of the "streamlined checkout flow". (Think of it as the Web Payments CG Checkout API Lite).

What we get from this separation is the ability to distinguish between:
 1. Data that is passed to the browser to improve the UX (line items) and request data that the **merchant** requires.
 1. Data that is passed to the payment app because it is required for processing the payment.

I would consider @djackso3 's request for KYC data, shipping data and billing data to be something that is required for the processing of the payment and also something that may or may not be required depending on the payment method.

---
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/1#issuecomment-207914480