@tommythorsen, > Or calling submitPaymentResponse with a response that indicates an error/cancellation? My view is that this is what you should do. Payment Apps are defined as receiving payment requests and sending payment responses in the proposed architecture document -- which keeps their API very simple. So, in this case, you would send a payment response that indicates the error/cancellation. Others may have different opinions. --- 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/issues/128#issuecomment-214753546Received on Tuesday, 26 April 2016 13:58:10 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:16 UTC