IIRC @adrianba has already said he doesn't want to make PaymentRequest a singleton but that's okay. The privacy problems only start when the website calls `show()`. I could imagine a mechanism by which if you call `canUserPay()` (or whatever we call this function) and it returns a `true` then we start to restrict things until the merchant calls `show()`. Or perhaps we stop creation of new PaymentRequests after that has been called on any PaymentRequest? We need to model this a little better I think before we make a concrete proposal --- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/159#issuecomment-232035671
Received on Tuesday, 12 July 2016 12:44:22 UTC