Re: The Payments Architecture within which a Web Payments Architecture occurs

Thanks Tony,

Regarding the W3C's role, here's what it says on pg 63 of "Core Principles
for Systemically Important Payment Systems" regarding any "systemically
important payment system":

"Responsibility C - The central bank should oversee compliance with the
Core Principles by systems it does not operate and it should have the
ability to carry out this oversight.
8.3.1 The designer and operator of a systemically important payment system
bear the primary responsibility for ensuring that the system complies with
the Core Principles. Where the central bank is not itself the operator, its
role is to oversee compliance, ensuring that the designer and operator
fulfil their responsibilities. The need for a sound basis for oversight and
the varying means by which this can be achieved are discussed in Part 1.
The need for clear definition of a central bank’s oversight objectives and
for public disclosure of its relevant policies is covered by Responsibility
A

While it's understood that many in the community aren't thrilled about that
oversight, various courts in various jurisdictions in the past year have
clarified which part of the payments architecture occurs in who's
bailywick. What I'm recommending is that it's much preferred to detect and
illustrate the boundaries ex ante, rather than ex post.

Joseph Potvin
Operations Manager | Gestionnaire des opérations
The Opman Company | La compagnie Opman
jpotvin@opman.ca
Mobile: 819-593-5983


On Thu, May 14, 2015 at 11:30 AM, Tony Camero <tonycamerobiz@gmail.com>
wrote:

> For what it's worth, I share Joseph's perspective in that my company is
> creating a web+mobile payments platform that would enable a user to
> transact in any single or dual-currency transaction involving potentially
> two or more currencies, whether State, virtual, or other flavor... and be
> able to transaction in various environments (web/mobile/analog) depending
> on the needs of the parties to the transaction.
>
> IMO a standardized "Payments Architecture" should be inclusive of web,
> mobile data (SMS or otherwise), bluetooth P2P, and even consider
> application to analog/offline payment protocols where practical.
>
>
>
> On Thu, May 14, 2015 at 10:06 AM, Melvin Carvalho <
> melvincarvalho@gmail.com> wrote:
>
>>
>>
>> On 14 May 2015 at 16:59, Joseph Potvin <jpotvin@opman.ca> wrote:
>>
>>> The issue that I'm raising is that a "Payments Architecture" in general
>>> is orthogonal to the "Architecture of the World Wide Web". Any architecture
>>> for "web mediated payments" needs to reference a Payments Architecture that
>>> is abstracted from whatever media are employed. And any architecture for
>>> "web mediated e-commerce" needs to reference an Commerce Architecture that
>>> is abstracted from whatever media are employed.
>>>
>>
>> I think I may be slightly confused as to the functions of a "Payments
>> Architecture", that are not covered in awww, or the ontologies.  Would you
>> be able to elaborate.
>>
>>
>>>
>>> Joseph Potvin
>>> Operations Manager | Gestionnaire des opérations
>>> The Opman Company | La compagnie Opman
>>> jpotvin@opman.ca
>>> Mobile: 819-593-5983
>>>
>>> On Thu, May 14, 2015 at 10:38 AM, Melvin Carvalho <
>>> melvincarvalho@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> On 14 May 2015 at 16:08, Joseph Potvin <jpotvin@opman.ca> wrote:
>>>>
>>>>> I would like to raise a general consideration to the CG list:
>>>>>
>>>>> What aspects of a "Web Payments: Technical Architecture" are unique to
>>>>> "Web" mediated payment, what what aspects are generic to payment via any
>>>>> medium?
>>>>>
>>>>> It seems to me that a generic payments technical architecture provides
>>>>> the functional system environment within and upon which a Web payments
>>>>> technical architecture occurs.  Therefore it seems to me critical to
>>>>> clearly separate these two in the document.
>>>>>
>>>>> The thought I'm attempting to underline is that a Web Payments
>>>>> Technical Architecture must point to an explicit external source that
>>>>> provides a generic Payments Achitecture, preferably one provided and
>>>>> maintained by a genuine global standards body, or something that in effect
>>>>> serves that function. The generic Payment Architecture ought to be
>>>>> sufficiently refined as to be consistent across all media
>>>>>
>>>>> A Web Payments Technical Architecture must (I would have thought)
>>>>> restrict its additive scope to that which is within the domain of the W3C,
>>>>> while explicitly referencing (in its text and diagrams) the generic
>>>>> Payments Achitecture that it is engaging.
>>>>>
>>>>
>>>> Web arch is about naming things using URIs as per awww [1].  The
>>>> payments work builds on that, and leverages other web technologies such as
>>>> HTTP, linked data, JSON LD etc.
>>>>
>>>> [1] http://www.w3.org/TR/webarch/
>>>>
>>>>
>>>>>
>>>>> --
>>>>> Joseph Potvin
>>>>> Operations Manager | Gestionnaire des opérations
>>>>> The Opman Company | La compagnie Opman
>>>>> jpotvin@opman.ca
>>>>> Mobile: 819-593-5983
>>>>>
>>>>
>>>>
>>>
>>>
>>> -- Joseph Potvin
>>> Operations Manager | Gestionnaire des opérations
>>> The Opman Company | La compagnie Opman
>>> jpotvin@opman.ca
>>> Mobile: 819-593-5983
>>>
>>>
>>
>


--