Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19)

>      <h3>Registration and Unregistration</h3>
>      <ul>
> -      <li>The user registers a payment app with the user agent, which provides developers with primitives for this
> -          purpose. For example, when using a Web-based payment app, the user can push a button to register the payment app.
> -          When using a native app, the native app can open a Web page that supports registration.</li>
> +      <li>
> + We expect registrations will happen at various times (e.g., outside and inside of checkout): Here are some examples:
> + <ul>
> +<li>        When the merchant recommends a payment app and the user selects it, registration can happen in that moment without additional user action.</li>
> +<li>        When the browser recommends a payment app and the user selects it, registration can happen in that moment without additional user action. (There is an expectation that the display of browser-recommended apps will differ from the display of merchant-recommended apps).</li>
> +<li>        When the user installs native payment app, registration can happen as part of the app installation process.</li>
> +<li>        Users visiting a Web site (e.g., merchant or bank) may wish to explicitly register payment apps.</li>
> + </ul>

```html
<li>        Users visiting a Web site (e.g., merchant or bank) may wish to explicitly register payment apps unrelated to a specific checkout or payment.</li>
```

---
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/webpayments-payment-apps-api/pull/19/files/f17221097d5b71d07091af0d6665c6d924616ba8#r73844251