Re: [w3c/web-based-payment-handler] Allow web-based payment handlers to report back internal error via Payment Request API (Issue #428)

stephenmcgruer left a comment (w3c/web-based-payment-handler#428)

So I think it suffices to:

1. Change the [Respond to PaymentRequest algorithm](https://w3c.github.io/web-based-payment-handler/#dfn-respond-to-paymentrequest-algorithm) to say:

```
8. Upon rejection of handlerResponsePromise with |reason|:
    1. Run the payment app failure algorithm with |reason|, and terminate these steps.
```

2. And then change the payment app failure algorithm to say something akin to:

```
1. If |reason| is a "OperationError" DOMException, then
    1.1. Run the "payment handler indicates an internal error algorithm" from [payment-request]
2. Else,
    2.1. Run the "user aborts the payment request algorithm" from [payment-request].
NOTE: (Explain about backwards compatibility here)
```

3. Update other call sites to the payment app failure algorithm appropriately.

We also should think about verbiage allowing the user agent to return the user to an app selector rather than error out, but thats likely lower priority given current usage patterns of Payment Request (largely single-app).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/web-based-payment-handler/issues/428#issuecomment-3997308270
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/web-based-payment-handler/issues/428/3997308270@github.com>