Re: [w3c/payment-handler] registration paymentManager instruments .set 'instrument-key' handler payment (Issue #410)

I'm assuming here that `https://testpr.fr/manifest.json` is an example URL, since that 404s in my browser. Not having a real reproduction website makes this a little harder to understand.

Anyway, some high level notes:

1. The installer is no longer necessary (though I think it technically should work) - the PaymentRequest.show() call will do the install for you when it encounters the payment method manifest.
2. You don't actually show the contents of the web app manifest (https://testpr.fr/manifest.json) in your comment above, knowing that would be helpful.
3. Your Payment Request code looks roughly correct, **assuming** that at https://testpr.fr one can find either the payment method manifest you include above, or that it responds with a Link header pointing to the manifest (as [described here](https://web.dev/setting-up-a-payment-method/#optionally-route-the-browser-to-find-the-payment-method-manifest-in-another-location)).

As a suggestion, https://rsolomakhin.github.io/pr/ph-icon-size/ is a demo that trigger a number of different payment handlers (depending on what button is clicked). The individual payment handler's code can be found at e.g. https://rsolomakhin.github.io/pr/apps/icon-sizes/icon-24-test/payment_method_manifest.json . Possibly looking at both the triggering code and the web app manifest+code may help.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-handler/issues/410#issuecomment-1476429846
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/payment-handler/issues/410/1476429846@github.com>