Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316)

The throttling happens per top-level frame, so iframe based libraries should not be affected, unless multiple iframes embedded on the same page query different payment methods at the same time. Let's encourage a single embedded iframe approach to avoid this situation.

As for sharing `secure.squarespace.com` among multiple merchants with different payment preferences, you can pre-query `canMakeActivePayemnt()` before navigation to `secure.squarespace.com` and pass the query result on. So, for example, `https://charlie-shop.squarespace.com` can query 'canMakeActivePayment()` for "visa" and then open up something like `https://secure.squarespace.com/payment-request/visa` to complete the checkout process.

-- 
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/browser-payment-api/pull/316#issuecomment-261245974