@tommythorsen > The browser is not able to answer questions regarding the contents of the data fields in PaymentMethodData and PaymentDetailsModifier dictionaries. The structure of the contents of these fields are proprietary, and only known by the payee (the merchant) and the payment provider (the one that owns the payment app). I think I get it, but could you provide a quick example (with code)? I understand the thing about the proprietary structures, but what isn't clear to me is how the other origin would answer that without any access to origin data or communication. It kinda feels like the recommended apps issue - too much time is being spent discussing the mechanism rather than the bigger picture. > Are there any examples of similar [sandboxing] in existence today, or are we treading new ground here? If it's the latter, then I am apprehensive about this. I think it's new ground. There are worklets from the houdini project, which may be similar. However, are we sure this solves the problem, if the code has no access to network or storage? -- 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/96#issuecomment-275090973
Received on Wednesday, 25 January 2017 12:02:59 UTC