- From: Pelle Braendgaard <pelle@stakeventures.com>
- Date: Fri, 7 Oct 2011 14:26:38 -0400
- To: Web Payments <public-webpayments@w3.org>
- Message-ID: <CAHtLsUWg4sJpiPCXtb20YYDdkr=hUQQtPsijU6V9JoqOz4cGhQ@mail.gmail.com>
Here are two extra use cases related to the lower levels of the standard: Simple Payment Request User A can request payment either on their web site or in their contact details. User B pays the user by clicking the link and performing the payment. Point of Sale Payment Device A user can by coffee in a coffee shop through a mobile phone app using NFC, a payment card, SMS payment or some other unspecified device in the future. This use case allows different emerging physical payment devices to be used on top of an open payment standard. When user receives device he links it to his account with a payment provider. This process is similar to activating a new card today on your bank account. Once a user is authenticated with the card supplier he is taken through the OAuth flow with his payment provider issuing a token to the device/app provider. This can be revoked at any time by the user. Payments are handled in device firmware/ app code to perform payments based on whatever method NFC/stripereader/bumping etc that is used at the POS. -- http://picomoney.com - Like money, just smaller http://stakeventures.com - My blog about startups and agile banking
Received on Friday, 7 October 2011 18:27:07 UTC