[payment agent] Payment architecture feature priorities

I took an action today to try and attempt to figure out how to
prioritize payment architecture features and map them to use cases:

https://www.w3.org/Payments/IG/track/actions/94

Here's the rationale that was used to create the payment architecture
feature list:

* Split the Payment Architecture into "levels":
     Level 1 - The minimum viable product
     Level 2 - Make architecture compelling for retailers
     Level 3 - Extend architecture to mobile/wireless devices
     Level 4 - Faster clearing/settlement
* We would suggest that W3C creates technical working groups to
  implement the levels in order... level 1 is highest
  priority, level 2 is next highest, and so forth.
* Map features in each level to use cases

Caveats:

* I only really focused on Level 1, expect Levels 2-4 to change
  quite a bit if we decide that this is a good approach.
* I don't think just doing Level 1 is compelling enough. It's there
  merely to illustrate the minimum necessary to accomplish a
  Web Payment round-trip.

Here's the document so far, we could discuss Payment Architecture Level
1 on the Payment Agent call tomorrow.

https://www.w3.org/Payments/IG/wiki/Payment_Architecture_Feature_Priorities

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: The Marathonic Dawn of Web Payments
http://manu.sporny.org/2014/dawn-of-web-payments/

Received on Friday, 24 April 2015 04:55:28 UTC