I think there are some UI challenges that would need to be figured out here because many existing implementations capture this information in parallel with payment handler selection. I think we would need a way for the browser to query the handler for this info before the handler is invoked so that the options can be shown mixed in with the browser's. That said, if those options changed each time I selected a payment handler that would suck. @Krystosterone how would you imagine the UI for this working? I.e. Let's assume I am on an Android phone and select Amazon as the payment handler (this is at the bottom of the sheet). The other info I am providing (name, shipping address) is higher in the sheet so I have likely already selected this. -- 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/issues/218#issuecomment-333206955
Received on Friday, 29 September 2017 18:45:06 UTC