Repeating what I said in #103... When making a purchase "in real life", it is uncommon to tell the payment processor exactly what is being purchased - instead, only the merchant's info and how much it costs is shared. Otherwise, the payment processor (e.g., my local bank) could gather an extensive list of things that I've purchased over time (which is fairly scary from a privacy perspective). Thus, in the interest of privacy, perhaps we shouldn't send the `displayItems` to the payment handler's service worker? Alternatively, we could instead allow the user to not share display items, or allow them to send a generic "Goods or Services" instead item instead. Rather, when the user goes to make a purchase, where the user chooses which PWA to use to fulfill the payment, the browser can display the items there instead.  Having said that, looking over PayPal invoices received over email, PayPal does get sent the display items during a purchase. 🤔 -- 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/91#issuecomment-279904374
Received on Wednesday, 15 February 2017 03:04:17 UTC