+1 to defining the messaging when registration happens via a browser. Native registration is clearly something we don't want to get into! FWIW I don't know that there is really an interesting difference between "open" and "proprietary" payment methods from our perspective. I don't even think I know what that means. Payment methods need to have a defined way of message passing from the merchant <--> method right? Or are you envisioning some sort of out of band communication because a method has a relationship with the merchant? --- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments-payment-apps-api/issues/8#issuecomment-235649953
Received on Wednesday, 27 July 2016 16:58:30 UTC