Re: [w3c/payment-request] Improved error codes (Issue #1040)

stephenmcgruer left a comment (w3c/payment-request#1040)

I put together https://github.com/w3c/payment-request/pull/1050 to start exploring this, and I did hit some internal "hrm" feelings. A few non-structured thoughts:

1. Is it correct (conceptually) that a payment app should be able to directly indicate an internal failure that causes the `show()` (or `retry()`) prompt to be resolved? Or should the user be able to choose another payment handler instead, in that case? This may be addressable just by giving the browser the choice of how to handle the situation.

2. Should errors from the payment handler itself just be communicated in the `PaymentResponse` via method-specific `data`, rather than by rejecting the show/retry promise?

Interested in thoughts from everyone, but particularly @marcoscaceres (and NickS, but I don't know their github handle!) :)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/issues/1040#issuecomment-3524507778
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/payment-request/issues/1040/3524507778@github.com>