Re: [w3c/payment-handler] Add userHint to PaymentManager (#206)

Managing "PaymentInstruments" is going to a somewhat complex matter for Payment Handler implementers if they really want a great experience for their users that have multiple devices. For example, whenever the user registers a new "payment instrument" on a payment handler's website, the website is going to do something like send a push notification to wake up service workers on other devices to do the same registration.

There's going to be significant thought and effort put into setting up icons, names, and doing maintenance on these things -- so if they aren't going to be used, we should really reconsider the approach entirely -- or at least understand a little bit more about what it takes to actually implement this stuff. I'm just saying I'm concerned with the direction.

Just imagine now that I'm setting a "userHint" of "***1234" that Chrome is showing ... and then Mozilla is showing the same user hint PLUS all of my instruments, some of which aren't "***1234". That will be quite confusing. How will Mozilla know whether or not they should show "userHint"? What if some people just want to do "user@example.com"?

-- 
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-handler/pull/206#issuecomment-325001311