- From: Timothy Holborn <timothy.holborn@gmail.com>
- Date: Thu, 24 Apr 2014 01:50:37 +1000
- To: Kumar McMillan <kmcmillan@mozilla.com>
- Cc: Manu Sporny <msporny@digitalbazaar.com>, "public-webpayments@w3.org" <public-webpayments@w3.org>
Look up rww / data.fm - create a webid. Download the source, make your own server. Incorporated legal entities should have EQUAL rights (ideally, we prioritise natural legal beings over Incorporated ones, rule of law should be accessible).... Tech standards can handle proxy / duplicate receipts, I imagine. IMHO. Timh Sent from my iPad > On 24 Apr 2014, at 1:43 am, Kumar McMillan <kmcmillan@mozilla.com> wrote: > > >> On Apr 22, 2014, at 8:17 PM, Manu Sporny <msporny@digitalbazaar.com> wrote: >> 4. Standardize payment initiation: >> https://web-payments.org/specs/source/web-commerce-api/ >> 5. Standardize digital receipts: >> https://web-payments.org/specs/source/web-commerce/ > > To specifically solve the nascar problem I think you only need these two things ^ > > A web API (or JavaScript shim) just needs to know how to invoke a compliant payment provider and how to verify the purchase. Each payment provider could still handle identity / credentials themselves. > > -Kumar
Received on Wednesday, 23 April 2014 15:51:10 UTC