- From: Shane McCarron <shane@halindrome.com>
- Date: Tue, 8 Dec 2015 09:51:37 -0600
- To: "public-webpayments-ig@w3.org" <public-webpayments-ig@w3.org>
- Message-ID: <CAJdbnOCEGQSWTCp9wGkGDWKNUMcTadzwaJ9AvdJkqBZ31kW4Ow@mail.gmail.com>
On Tue, Dec 8, 2015 at 9:08 AM, Dave Longley <dlongley@digitalbazaar.com> wrote: > Payment device/mechanism/credential? Unless I misunderstand the definition (and my restatement of that definition) none of these really match it. > > > On 12/08/2015 08:42 AM, David Jackson wrote: > >> Payment service? Payment type? >> >> David Jackson | Senior Director Financial Services >> M: +1.614.570.1237 | VoIP: +1.614.465.6654 >> Oracle Industry Solutions Group >> New York City | Columbus >> >> >> Shane McCarron <shane@halindrome.com> wrote: >> >> Hmm - no. Method has a connotation that (to me) makes it too easily >> confused / conflated with Payment Scheme (e.g., for this transaction my >> payment scheme/method is paypal). >> >> Maybe we should spend a minute expanding the definition of the term in >> the hopes that it will help solidify in everyone's mind what this term >> maps to? The current definition reads "A piece of software that enables >> a payer to make payments (usually provided by the payer's PSP)" >> >> Wikipedia (not definitive, I know) defines a PSP as "A payment service >> provider (PSP) offers shops online services for accepting electronic >> payments by a variety of payment methods including credit card, >> bank-based payments such as direct debit, bank transfer, and real-time >> bank transfer based on online banking." This happens to correspond with >> what I think a PSP is. And it has nothing to do with a payer. So I am >> already confused when I look at our term "Payment Application" and its >> corresponding definition. I also think the definition is overly >> simplistic. >> >> I think the thing we are really trying to make up a term for is "One or >> more pieces of software that act as a conduit between the payer and >> their various funding sources, enabling the payer to make payments from >> one or more of those funding sources." Before I explore this any >> further.... is that correct? >> >> On Tue, Dec 8, 2015 at 7:03 AM, David Jackson >> <david.dj.jackson@oracle.com <mailto:david.dj.jackson@oracle.com>> wrote: >> >> Payment method? >> >> -- >> David Jackson | Senior Director Financial Services >> Mobile: +16145601237 <tel:%2B16145601237> | VOIP: +16144656654 >> <tel:%2B16144656654> >> Oracle Industry Solutions Group >> New York City | Columbus, Ohio >> >> >> >> >> -----Original Message----- >> From: Telford-Reed, Nick [mailto:Nick.Telford-Reed@worldpay.com >> <mailto:Nick.Telford-Reed@worldpay.com>] >> Sent: Tuesday, December 08, 2015 6:51 AM >> To: nshearer@apple.com <mailto:nshearer@apple.com>; >> Joerg.Heuer@telekom.de <mailto:Joerg.Heuer@telekom.de> >> Cc: David_E3@VERIFONE.com; public-webpayments-ig@w3.org >> <mailto:public-webpayments-ig@w3.org> >> Subject: RE: Web Payments IG Telcon Agenda - 2015-12-07 @ 10:00 AM >> Eastern Time (US) for 60 minutes >> >> Suggestions welcome then. Payment instrument seems too esoteric for >> "non-payments" folk. Payment app is overloaded. Anyone got an >> alternative? >> >> N >> >> -- >> Nick Telford-Reed >> e: nick.telford-reed@worldpay.com >> <mailto:nick.telford-reed@worldpay.com> | m: +447799473854 >> <tel:%2B447799473854> | t: +44 203 664 5069 >> <tel:%2B44%20203%20664%205069> >> >> >> > -----Original Message----- >> > From: nshearer@apple.com <mailto:nshearer@apple.com> >> [mailto:nshearer@apple.com <mailto:nshearer@apple.com>] >> > Sent: 07 December 2015 22:40 >> > To: Joerg.Heuer@telekom.de <mailto:Joerg.Heuer@telekom.de> >> > Cc: Telford-Reed, Nick; David_E3@VERIFONE.com; public-webpayments- >> > ig@w3.org <mailto:ig@w3.org> >> > Subject: Re: Web Payments IG Telcon Agenda - 2015-12-07 @ 10:00 AM >> > Eastern Time (US) for 60 minutes >> > >> > Hi everyone, >> > I also could not make the call either because I was called away on >> > travel at the last minute. >> > >> > I also agree with Joerg. The argument seems to be that "payment >> > instrument" is confusing people unfamiliar with the payments >> space, so >> > it should be replaced with something else. It's just that >> "something >> > else" has a very strong and unified definition when it comes to >> EMV. >> > When I think of "payment app" I always think of an applet on the >> SE. >> > >> > Nick. >> > >> > >> > > On Dec 7, 2015, at 10:54 PM, Joerg.Heuer@telekom.de >> <mailto:Joerg.Heuer@telekom.de> wrote: >> > > >> > > Hello Nick, all, >> > > >> > > As I won't be present in the call, let me first express my >> respect >> > > for the >> > work done over the last two weeks. I am really impressed! >> > > >> > > As I can't tell so myself, please take this mail as a clear 'No' >> to >> > > calling the >> > payment instrument an 'app'. >> > > >> > > In the mobile space apps are just so much tied to individual >> > > programs which >> > have a UI towards the user! While this might be one way in which >> > things might be done in the end, it should be made clear, that >> e.g. an >> > applet sitting on a Secure Element can as well be such a 'payment >> > instrument' and that it won't require another app and UI in order >> to be usable. >> > > >> > > Thanks, >> > > >> > > Jörg >> > > >> > > -----Original Message----- >> > > From: Telford-Reed, Nick [mailto:Nick.Telford-Reed@worldpay.com >> <mailto:Nick.Telford-Reed@worldpay.com>] >> > > Sent: Samstag, 5. Dezember 2015 16:49 >> > > To: 'David Ezell'; public-webpayments-ig@w3.org >> <mailto:public-webpayments-ig@w3.org> >> > > Subject: RE: Web Payments IG Telcon Agenda - 2015-12-07 @ 10:00 >> AM >> > > Eastern Time (US) for 60 minutes >> > > >> > > David >> > > >> > > Per my mail >> (http://lists.w3.org/Archives/Public/public-webpayments- >> > ig/2015Dec/0013.html) , can we please table the vocabulary item >> from >> > the working group for Monday's call? >> > > >> > > Nick >> > > >> > > -- >> > > Nick Telford-Reed >> > > e: nick.telford-reed@worldpay.com >> <mailto:nick.telford-reed@worldpay.com> | m: +447799473854 >> <tel:%2B447799473854> | t: +44 203 >> > > 664 >> > > 5069 >> > > >> > > >> > >> -----Original Message----- >> > >> From: David Ezell [mailto:David_E3@VERIFONE.com >> <mailto:David_E3@VERIFONE.com>] >> > >> Sent: 04 December 2015 19:50 >> > >> To: public-webpayments-ig@w3.org >> <mailto:public-webpayments-ig@w3.org> >> > >> Subject: Web Payments IG Telcon Agenda - 2015-12-07 @ 10:00 AM >> > >> Eastern Time (US) for 60 minutes >> > >> >> > >> Agenda for the call: >> > >> >> > >> 1 Confirm agenda. Please send agenda change requests in >> advance. >> > >> >> > >> Appoint scribe. >> > >> See: https://www.w3.org/Payments/IG/wiki/Main_Page#scribes >> > >> >> > >> 2 Review of Task Force Proposals >> > >> >> > >> We have several proposals for Task Forces to pursue >> additional work: >> > >> https://www.w3.org/Payments/IG/wiki/Main_Page/ProposalsQ42015 >> > >> >> > >> *** IMPORTANT *** >> > >> *** Note: for each topic, we are attempting to make a >> > >> (relatively) crisp proposal WRT problems to solve, >> > >> *** deliverables proposed, and a timeline. Authors of these >> > >> proposals are invited to upgrade their >> > >> *** submissions as necessary. >> > >> >> > >> The following proposals are remaining for a "first-pass" >> review: >> > >> * Capabilities Document >> > >> >> > >> >> > https://www.w3.org/Payments/IG/wiki/Main_Page/ProposalsQ42015/Capa >> > >> bilities >> > >> * Interledger Payments >> > >> >> > >> >> > >> https://www.w3.org/Payments/IG/wiki/Main_Page/ProposalsQ42015/Interl >> >> > > >> > >> edger >> > >> >> > >> Updates (time permitting): >> > >> * ISO20022 Harmonization >> > >> >> > >> >> > >> https://www.w3.org/Payments/IG/wiki/Main_Page/ProposalsQ42015/ISO20 >> > >> 022_Harmonization_Task_Force >> > >> * Verifiable Claims >> > >> >> > >> >> > https://www.w3.org/Payments/IG/wiki/Main_Page/ProposalsQ42015/Cred >> > >> entials >> > >> It looks as though the following proposals will end up >> being >> > >> subsumed into Verifiable Claims: >> > >> ** Identity Provider TF Proposal >> > >> >> > >> >> > >> https://www.w3.org/Payments/IG/wiki/Main_Page/ProposalsQ42015/IdP_T >> > >> F >> > >> ** Tokenization >> > >> >> > >> >> > https://www.w3.org/Payments/IG/wiki/Main_Page/ProposalsQ42015/Toke >> > >> nization_TF >> > >> >> > >> ------ >> > >> >> > >> Telcon Information >> > >> =============== >> > >> IRC Channel: >> > >> #wpay >> > >> IG home page: http://www.w3.org/Payments/IG/ >> > >> >> > >> WebEx (voice) see: >> > >> http://www.w3.org/2015/11/wpig.ics >> > >> >> > >> For details on meeting participation see >> > >> >> > >> https://www.w3.org/Payments/IG/wiki/Main_Page#Teleconference_Logisti >> >> > > >> > >> cs >> > > >> > > 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 >> <http://www.dnb.nl>. Worldpay, the >> > logo and any associated brand names are trade marks of the >> Worldpay group. >> > > >> > > >> >> 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 >> <http://www.dnb.nl>. Worldpay, the logo and any associated brand >> names are trade marks of the Worldpay group. >> >> >> >> >> >> -- >> -Shane >> > > > -- > Dave Longley > CTO > Digital Bazaar, Inc. > http://digitalbazaar.com > -- -Shane
Received on Tuesday, 8 December 2015 15:52:07 UTC