[w3c/payment-request] Real use case for .complete("unknown") - or mark "at risk" (#584)

As part of https://github.com/w3c/payment-request/pull/583, we've somewhat struggled to come up with a real use case for completing a payment response with "unknown". 

Although "unknown" feels like a good idea, can anyone think of a *real* use case where:
 
* somehow you get into the "unknown" situation? 
* "fail" doesn't suffice? 

If we can't come up with something useful, we should probably mark it "at risk". 

Also noting that Chrome (on desktop) currently treats `.complete("unknown")` the same as `.complete("success")`, in that it just closes the payment sheet and doesn't inform the user about anything. 

I'm not sure yet what we will do in Firefox. It will depend on the outcome of this discussion, I guess.   

In the spec, "unknown" plays no role in any algorithm. 

-- 
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/payment-request/issues/584