Re: [w3c/browser-payment-api] Change the way we request user data (#65)

**Proposal** for capturing _optional data_ for the payee:

1. Add section to the payment request to request "additional info" option be displayed by the user agent.
2. "Additional info" (or a custom label) option/button is displayed by the user agent.
3. When the payer presses "Additional info" (“Add VAT Identifier” in example) the user agent renders a separate view to collect the information based on the request data specified by the payee (similar format to [dynamic input field](https://github.com/w3c/browser-payment-api/pull/65#issuecomment-212488768) proposed by Adrian). 
4. Payer fills out field(s) and submits form and the data is sent to the payee. 

Ex. “Add VAT Identifier" placement within user agent

<img width="301" alt="paliga-test - checkout 2016-04-29 17-12-09 2016-04-29 17-12-11" src="https://cloud.githubusercontent.com/assets/2962326/14930029/f29e19d6-0e2e-11e6-9839-eb8d333bf07c.png">

Ex. Request data provided by payee

```
{
  requestData: [
    {
      label: "VAT Identifier",
      type: "string"
    }
  ] 
}
```
**Considerations**

- “Additional info” data would be expected to outside of the primary checkout flow, it would exist on a secondary view that doesn’t interfere with the streamlined checkout flow offered by the UA.
- This approach is meant to limit the impact additional info requirements would have on checkout experience while still providing flexibility. 
- All info captured in this form would be optional. 

---
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/pull/65#issuecomment-215888014