Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170)

rsolomakhin commented on this pull request.



> @@ -368,7 +373,7 @@ <h2>
       interface PaymentManager {
         [SameObject] readonly attribute PaymentInstruments instruments;
         [Exposed=Window] static Promise&lt;PermissionState&gt; requestPermission();
-        attribute DOMString userHint;     
+        attribute DOMString userHint;

@marcoscaceres: One way we originally envisioned doing what you propose is providing a way for the payment handler to specify which payment instrument is the default, so the UA can use its description as the user hint when not showing all instruments. However, this confused pretty much everyone, because people thought the default payment handler is the one that's currently selected inside of the payment handler and that had some kind of impact on processing the `PaymentRequestEvent`, which was not the intention. Our intention is to provide some user-specific data next to the common name of the payment handler, because we have seen higher checkout completion rates when we did this for shipping addresses. This user-specific data does not have to be the last four digits of the card number. It can be user's email address or username, for example, which is not something that you would typically find in the description of their instruments. Hence, we believe that giving the web developers the power to explicitly specify the user hint is the best approach that we could come up with. Do you have anything better in mind?

-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-handler/pull/170#discussion_r174221358