Re: [w3c/payment-request] Alternative 'Pay' button wording options for Browser UI (#701)

> Note that this is supposed to be communicated by the merchant’s UI, and by calling PaymentResponse.complete(“unknown”). Would be great to explore if that’s sufficient.

It's post-action. But that could help. Or perhaps, additionally relying on those enums as selective input, for the UA to use a button label according to the expected results. I am too clear on what "unknown" would cover. Maybe "authorized" is broad enough that it could be added, leaving "unknown" to a more simple registration without validation.

e.g. Should the request sends a custom `{ "fail", "authorized"};` the UA can assess fairly reliably that this is payment authorization request and it does not expect the payment to be processed... just a thought.

-- 
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/701#issuecomment-381053949