@adrianhopebailie : What's your definition of an open payment method? I would think that payment methods implemented inside of the browser (so far only `"basic-card"`) would let the merchant know the selected instrument properties (type and network for `"basic-card"`), because the selection happens inside of the browser payment sheet. For payment methods implemented in a payment app, Chrome currently does not have a way to know which instrument is being selected inside of the payment app, so Chrome could let the merchant know only the list of payment methods supported by the selected payment app. From spec perspective, we could make `PaymentOptionChangeEvent.method` a union of string and array and suggest that browsers populate `PaymentOptionChangeEvent.details` to the best of their ability. -- 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-request/issues/684#issuecomment-365633501
Received on Wednesday, 14 February 2018 15:01:22 UTC