Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163)

Hmm, I can see what you are saying about waiting, but I believe the problem is unavoidable. @halindrome nailed my point, which is that there are certain expectations people have when viewing a display of what they are paying for. Without strong typing of what the items mean, any implementor is left to just figure it out and that is certain to fail. Wouldn't it be really confusing if your tax item was rendered first, then an actual good, then a discount, then another good? What a weird and clunky checkout experience.

I don't have any solid examples off the top of my head other than taxes, but I believe there are strong reasons why payment apps would want to know the breakdown of the payment as well. Since we have constructed the PaymentRequest prior to engaging with the payment app, our only hope for providing itemization compatibility between the apps is to provide an option to strongly type them.

---
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/browser-payment-api/issues/163#issuecomment-215921444