Hi all, On direction of thinking for the semantics of canMakePayment and hasEnrolledInstrument is captured in this blog post: https://www.w3.org/blog/wpwg/2020/01/17/working-with-canmakepayment-and-hasenrolledinstrument/ Namely: canMakePayment does not require the browser to communicate with the payment handler, while hasEnrolledInstrument does. If we move in that direction (see also this proposal [1]), then there should not be the need for both algorithms: "Steps to check if a payment can be made" and "Steps to check if an instrument is supported" because the API surface only needs one of them. They could be combined. [1] https://docs.google.com/document/d/1C_xH-6sJb9UedrvifsvqS_2k_We0IlPSfWFo8Kg54ps/edit -- 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-method-basic-card/issues/87
Received on Monday, 30 March 2020 20:08:45 UTC