@jnormore, I am glad to hear of the discount code use case; that reinforces my sense (in discussion within the web payments IG) that loyalty, coupons, discount codes, etc. would be a valuable layer on top of the infrastructure we are building. I believe, however, that those are out of scope for our current working group per our charter [1]: "Recommendations for loyalty schemes and coupons, digital receipts, digital credentials, tickets, and location services are out of scope. Future W3C activities may seek to increase interoperability of these or other additional digital wallet capabilities." I am still interested in finding ways to create a superior user experience based on merchant/customer dialog, and what guidance we might provide to any merchant that wants to use the (future) API but where the API does not have built-in features to let them collect data that they need. Should this happen before pushing the buy button? Should payment apps step in through back-channel discussions with merchants and offer their own UI for gathering data? Ian [1] https://www.w3.org/Payments/WG/charter-201510.html --- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/pull/65#issuecomment-214553603
Received on Monday, 25 April 2016 22:46:07 UTC