stephenmcgruer created an issue (w3c/web-based-payment-handler#428) See https://github.com/w3c/payment-request/pull/1050 and https://github.com/w3c/payment-request/issues/1040, where the Payment Request API is now defining more explicit steps to let payment handlers report back internal errors (as differentiated from user abort). The Web-Based Payment Handler spec will need to be updated to match, likely by being specific about what happens when the promise passed to respondWith is rejected (and with what types, to let them choose between AbortError and OperationError). It will also have to consider backwards compatibility. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/web-based-payment-handler/issues/428 You are receiving this because you are subscribed to this thread. Message ID: <w3c/web-based-payment-handler/issues/428@github.com>
Received on Tuesday, 3 March 2026 17:31:05 UTC