W3C home > Mailing lists > Public > public-payments-wg@w3.org > May 2016

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

From: Tommy Thorsen <notifications@github.com>
Date: Thu, 26 May 2016 06:50:32 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/110/221876259@github.com>
> So in this example, the app technically supports payment methods C (i.e. it understands the messages and requirements) but it is not able to process payments using that method therefor it should not register itself as supporting method C until the user loads a payment instrument that enables that.

I think we are going to have problems enforcing this. If I put myself in the shoes of a payment app developer: why would I not register all of my supported payment methods as enabled all the time? Even if the user hasn't registered a payment instrument in my app yet, I can lead him through the instrument registration process as part of the payment process.

That way, the user gets to buy his thing without being told `ERROR: NO MATCHING PAYMENT APP`, and I get to make some money off the transaction. Everybody wins! (Except for the users that have many payment apps installed, only some of which have suitable payment instruments registered, but all showing up in the payment app selector regardless).

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Received on Thursday, 26 May 2016 13:51:25 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 26 May 2016 13:51:26 UTC