@rsolomakhin actually, while I agree with your point in general, I don't completely agree with your solution 😄 Most importantly, pre-auth is a feature of specific **payment methods** (just like recurring payments and other features we have explored). Some payment methods will support this concept, some won't. If we "add support" for these features it will likely be in the Basic Card payment method spec (not payment request) where we will add some additional payment method data that allows the merchant to specify that they are requesting a pre-auth not a payment. There will likely be value in defining some standard ways to express this so it can be consistent across other payment methods, or making it a property of the `PaymentRequest` but I expect that would be an evolution of the former happening first. My understanding of the purpose of `CanMakePayment` is not to verify funds but check if the user has payment instruments available that "can make the payment". Have I got that wrong? I'd be nervous about `CanMakePayment` having side-effects like actually checking a user's available balance (both from a privacy and usability perspective). @chadcampbell I've kept this open and marked it as Postponed so we can keep it under consideration as we plan our work for the next version of this API. -- 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/633#issuecomment-332622162
Received on Wednesday, 27 September 2017 18:59:14 UTC