- From: Stephen McGruer <notifications@github.com>
- Date: Fri, 17 Feb 2023 12:10:35 -0800
- To: w3c/payment-handler <payment-handler@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 17 February 2023 20:10:48 UTC
Hi there; thanks for filing the issue. Unfortunately `PaymentManager.Instruments` has been removed from the Payment Handler specification (https://github.com/w3c/payment-handler/pull/409) and from Chromium as of M111 (currently in Beta, to be released to Stable in early March). The concept of a browser-managed instruments never fully matured in the ecosystem, and instead things moved in the direction of just having a payment app which is responsible for handling whatever payment methods it wants to internally to its own logic (server and client). The still-supported way to install such a payment app is via the JIT path that is mentioned in the spec [here](https://w3c.github.io/payment-handler/#just-in-time-registration), but which there is also a web.dev article on that may be useful - https://web.dev/setting-up-a-payment-method/ I hope that this helps! -- Reply to this email directly or view it on GitHub: https://github.com/w3c/payment-handler/issues/410#issuecomment-1435189375 You are receiving this because you are subscribed to this thread. Message ID: <w3c/payment-handler/issues/410/1435189375@github.com>
Received on Friday, 17 February 2023 20:10:48 UTC