Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98)

@marcoscaceres,

You wrote: "A payment app is a web application that is registered to handle requests for payment via one or more payment methods. Payment methods are processed via one or more service workers". 

Here are my annotations:

 - "A payment app [that conforms to this specification] is a web application..."

    (There may be other payment app implementations that do things differently.

 - "that is registered to handle requests for payment via one or more payment methods."
    Ok.

 - "Payment methods are processed via one or more service workers".

    I would avoid the word "processed" because "payment processing" may be interpreted
    a particular way in the payments industry. 

What about this, merging your text with some of the text in the task force's spec, something like:

 "A payment app is software that enables the user to fulfill a payment request for one or more payment methods. A payment app that conforms to this specification is a Web application where one or more service workers handle the payment request and response."

Regarding consent from the user:

 * +1 to requiring consent when the payment app is first registered
 * -1 to requiring consent every time the payment app's capabilities change.

Ian



 
    

-- 
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/webpayments-payment-apps-api/issues/98#issuecomment-275585018