- From: Dave Longley <notifications@github.com>
- Date: Tue, 28 Nov 2017 15:21:37 +0000 (UTC)
- To: w3c/payment-handler <payment-handler@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/payment-handler/issues/236/347557103@github.com>
Hmm, I don't think `PaymentInstrument` is actually a "payment instrument" or "payment credential" as one would traditionally think, but rather a "hint" that the site understands and can surface to help the user make a selection. When the user selects a "hint", it is passed to the payment handler where that site will determine how to act on it. Such a hint will likely often map directly to a particular payment credential, but it need not. It could be used, for example, to inform the payment handler site that the user has selected that they want to pay using via a particular payment handler but using a new payment credential that they haven't provided to the site yet. Or it could be used to signify "pay with my default payment credential". That being said, I think it would be frustrating for the user if clearing site data wiped their registered "hints" and required them to revisit each payment handler site to get them reregistered. Perhaps revoking permission granted to an origin to act as a payment handler should be the mechanism by which `PaymentInstrument`s are forcibly cleared? This seems like the least surprising option to me. If the user wants to get those hints back, they would just revisit the site to grant permission again, at which point the site could reregister hints (aka `PaymentInstrument`s). -- 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/236#issuecomment-347557103
Received on Tuesday, 28 November 2017 15:22:13 UTC