Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)

It's fine if both (a) the payment app can reject the request and throw the user back to the mediator, and (b) the user can backup fro the payment app into the payment mediator, like if they do not like the results or the payment app is buggy, etc. 

I suspect the harder issue might be : Can a payment reject being an option for a particular transaction before the user even gets presented with the option?  To do that, a payment app would need to register a javascript filter with the payment mediator. 

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:

Received on Thursday, 14 April 2016 21:06:09 UTC