I think @zkoch is probably the best person to answer from Google's side actually :). Failing makes sense to me, but I have to assume there was some rationale behind the original design to ignore invalid data... > We would prefer to keep the implementation as is and think that having invalid data reject the entire transaction is a good solution to the problem I'm confused: do you want to keep the implementation as-is, or do you want to have invalid data reject the transaction? Those are mutually exclusive. -- 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/pull/418#issuecomment-281115738
Received on Monday, 20 February 2017 15:58:52 UTC