Wallets. Was: Dealing with the NASCAR Syndrome for Web Payments

I believe that addressing the entire wallet space is a very difficult idea.

Web-wallets can be hosted in the cloud.

Personally I' trying to *remove* the web-wallet concept completely and rather
build on local keys (=payment credentials) which [only] can work with payment-
provider-specific web-code embedded with the merchant's own application.

Then it will be up to the payment-providers if they want to support a common
check-out application or not.  Initially they certainly do not but that is
actually an advantage from a market-acceptance perspective.  I.e. there will
most likely be a [long] period where you still have to select payment method.

However you won't have to fill in any boring card stuff or use password,
a "bank-standard" PIN will do and with security will be on par with EMV.

If this pans out (...), this should [eventually] motivate setting up a joint
vendor for supplying the code since this is easier to swallow than VISA offering
MasterCard support.  That's how the ATM guys have done, going from proprietary
to more universal.

Regarding local wallets for NFC/iBeacon operation, I believe this can wait.
These use-cases could also use the web-version of this is they can think
of not using HCE and EMV.  This is a process...

Cheers,
Anders
http://webpki.org/papers/PKI/pki-webcrypto.pdf

Received on Thursday, 17 April 2014 11:46:32 UTC