Re: [w3c/webpayments-method-identifiers] Why URLs? (#9)

> Playing devil's advocate -- that doesn't mean we necessarily have to do anything about it. The user will just have a bad experience with that Payment App when it doesn't work ... and probably uninstall it

True, but there are two issues here:

1.) It's going to be very difficult to get certain payment method/app providers to play along if there isn't any way to protect their brand. 

2.) This is not the kind of UX I would feel comfortable shipping.

> To be clearer: an app that says it can service AlicePay.com but cannot has no substantially different property than an app that says it can service basic-card but cannot. Right?

You've just incentivized "Wallet providers" to  claim they support many different payment methods, even if it isn't true, to ensure they show up in the list of supported apps.

-- 
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/webpayments-method-identifiers/issues/9#issuecomment-240250067