Re: Payment architecture vocabulary

Hi all,

To add some context before we chat later, the goal here is a common set of
terms to use in our technical documentation. The audience for W3C
documentation is developers, the majority of whom have no prior exposure to
payments industry terminology or definitions. One could argue that the
value of using industry terminology that predominantly originates from
regulatory and policy documents and is targeted at a different audience, is
limited.

By using existing terms such as payment scheme and payment instrument we
also limit ourselves in terms of what these can be from a technical
perspective. We need terminology for components of a technical
architechture. There is not a hard requirement that these terms correlate,
1:1 with policy and regulatory components.

For example, the architecture defines a component called a "payment app".
This is very similar to what many of us define as a payment instrument but
may also have features such as the ability to generate a token, communicate
with a 3rd party payment service or be installed in the host platform. This
is valuable in terms of the architecture and by calling this a payment
instrument we risk gaining little but confusing many who have preconceived
ideas about what a payment instrument is.

There may be a need for the IG to develop some guidance for non-technical
audiences about how the WG terminology relates (if it does) to more
traditional terminology.

On 4 December 2015 at 19:12, Telford-Reed, Nick <
Nick.Telford-Reed@worldpay.com> wrote:

> All
>
>
>
> The web payments group is trying to define a working vocabulary for some
> specific concepts
>
>
>
> *Current Terminology*
>
> *Previous Terminology*
>
> *Definition*
>
> Payment App
>
> Payment Instrument
>
> A piece of software that enables a payer to make payments (usually
> provided by the payer's PSP)
>
> Payment Method
>
> Payment Scheme
>
> A way of paying. A system and set of rules for payments. A payment app may
> support one or more payment methods
>
> Payment Mediator
>
> Digital Wallet
>
> Coordinates the flow of messages between a payee’s application and the
> payer’s payment apps
>
>
>
>
> https://github.com/w3c/webpayments/wiki/A-Payments-Initiation-Architecture-for-the-Web#definitions
>
>
>
> David E and I took an action to discuss these definitions within the Web
> Payments Interest Group – I’d be grateful if we could include this on the
> agenda for Monday’s meeting.
>
> Thanks
>
> Nick
>
>
>
> --
>
> Nick Telford-Reed | Technology Innovation | m: +447799473854 | t: +44 203
> 664 5069
>
> s: WorldPay Centre, 270-289 Science Park, Milton Rd, Cambridge CB4 0WE UK
>
>
>
>
> This e-mail and any attachments are confidential, intended only for the addressee and may be privileged. If you have received this e-mail in error, please notify the sender immediately and delete it. Any content that does not relate to the business of Worldpay is personal to the sender and not authorised or endorsed by Worldpay. Worldpay does not accept responsibility for viruses or any loss or damage arising from transmission or access.
>
> Worldpay (UK) Limited (Company No: 07316500/ Financial Conduct Authority No: 530923), Worldpay Limited (Company No:03424752 / Financial Conduct Authority No: 504504), Worldpay AP Limited (Company No: 05593466 / Financial Conduct Authority No: 502597). Registered Office: The Walbrook Building, 25 Walbrook, London EC4N 8AF and authorised by the Financial Conduct Authority under the Payment Service Regulations 2009 for the provision of payment services. Worldpay (UK) Limited is authorised and regulated by the Financial Conduct Authority for consumer credit activities. Worldpay B.V. (WPBV) has its registered office in Amsterdam, the Netherlands (Handelsregister KvK no. 60494344). WPBV holds a licence from and is included in the register kept by De Nederlandsche Bank, which registration can be consulted through www.dnb.nl. Worldpay, the logo and any associated brand names are trade marks of the Worldpay group.
>
>
>
>