Ask the user whether they allow the payment app to be registered to handle the indicated payment methods (unless a prearranged trust relationship applies or the user has already granted or denied permission explicitly for this payment app).
https://w3c.github.io/webpayments-payment-apps-api/#set-manifest number 9, 10
Hm, we definitely need to get strings reviewed here. I'm not sure this string is clear to users about what's happening.
+Shimi, any thoughts on how we could make this clearer? The idea is that when a user visits a site that can handle payments (e.g. paypal.com), that site can request that they be added as a payment hander for payment request.
I'm wondering whether there is a better alternative than using a permission prompt here since we know prompts have so many problems. It would be good to meet and chat about this a bit more in person to understand the background and constraints :)
It sounded like raymes@ had some concerns about using a permission prompt here, did you ever get the chance to sync with any of the permission folks about this?
rouslan@ and others, is there another problem other than string? raymes@'s comment sounds that it is not perfect in security perspective. Could you explain to me what the risks are?
The payment handler is based on service-worker extension feature such as
push-notification or background-sync and so on.
If payment handlers are registered once, their list can be shown on the Payment
Request UI from merchant site initiated.
Also, users can select one thing of the list and then "paymentrequest" event
will be triggered in the associated service worker.
Although the event is triggered by user interaction on PaymentRequest UI,
the permission prompt is still needed for the following reasons.
- If we would be able to install payment handlers implicitly, fishing payment
handler might be increased. For examples, look-like PayPal but fishing
payment handler can be shown on PaymentReqeust UI. Users have to check origin
and then select safe payment handler but it's not easy if the look-and-feel
is the same.
- The SW event might be triggered without user interaction like
push-notification. (e.g. canMakePayment(), abort())
Comment 1 by rouslan@chromium.org
, Nov 16 2016