Re: Web Payments Working Group in 2018

Concur, and Capital One looks forward to contributing to these efforts.

On 1/24/18, 4:27 PM, "Peter Saint-Andre" <stpeter@mozilla.com> wrote:

    +1 - these are excellent goals.
    
    On 1/24/18 2:06 PM, Bhattacharjee, Manash wrote:
    > Hi Nick/Chairs
    > 
    >  
    > 
    > Sounds like a progressive set of objectives for the Working Group to aim
    > for in 2018. Mastercard team will continue to collaborate with the
    > members of the group on making a significant contribution.
    > 
    >  
    > 
    > Regards
    > 
    > Manash
    > 
    >  
    > 
    > *Manash Bhattacharjee*
    > 
    > Director Products
    > 
    > Digital Payments
    > 
    >  
    > 
    > Mastercard
    > 
    > 114 5th Avenue | New York, NY  
    > 
    > Mobile +1 914 325 9792
    > 
    > id:image001.png@01D30606.D87A9900 <http://www.mastercard.com/>
    > 
    >  
    > 
    > *From: *"Telford-Reed, Nick" <Nick.Telford-Reed@worldpay.com>
    > *Date: *Wednesday, January 24, 2018 at 5:46 PM
    > *To: *Payments WG Public <public-payments-wg@w3.org>
    > *Subject: *Web Payments Working Group in 2018
    > *Resent-From: *<public-payments-wg@w3.org>
    > *Resent-Date: *Wednesday, January 24, 2018 at 5:46 PM
    > 
    >  
    > 
    > Adrian, Ian and I have been discussing a vision for the Working Group's
    > activity over the coming 12 months which we’re keen to share with you
    > and discuss on the mailing list and the 25 January teleconference.
    > 
    >  
    > 
    > The big themes for 2018 are payment request and payment handler
    > adoption, security, and payment method innovation.
    > 
    >  
    > 
    > As ever, we’d love to hear your views – please let us know how you’d
    > like to see the group focused in 2018.
    > 
    >  
    > 
    > ===============
    > 
    > Payment Request Adoption
    > 
    >  
    > 
    > Implementation of Payment Request API and deployment in software
    > libraries continues. We are keen to gain more experience and work on
    > merchant adoption. From a specification perspective, we anticipate that
    > Payment Request API and Payment Method Identifiers will advance to
    > Recommendation mid-year.
    > 
    >  
    > 
    > ===============
    > 
    > Payment Handler Adoption
    > 
    >  
    > 
    > We’re really keen to see increased deployment experience of our
    > specifications, especially payment handler and its related specs, as we
    > feel that third-party web apps is a key enabler of the vision of a
    > payments ecosystem for the open web. We hope to see more browser
    > implementation of Payment Handler API in 2018 as well as greater
    > experimentation on the payment handler side of the API. Ideally, that
    > specification will advance to Candidate Recommendation later in the year.
    > 
    >  
    > 
    > ===============
    > 
    > Security
    > 
    >  
    > 
    > We have a tremendous opportunity to enhance security through Payment
    > Request API. We hope to rapidly advance work around enhancements to the
    > feature set, for example in Encryption, Tokenisation and 3D Secure.
    > 
    >  
    > 
    > We also look forward to working more closely with the Web Authentication
    > Working Group, as their specification plays an important role in
    > reducing payment fraud and enhancing Web security generally.
    > 
    >  
    > 
    > ===============
    > 
    > Payment Method Innovation
    > 
    >  
    > 
    > We'd also like to see progress around credit transfers and start new
    > discussions on topics such as Interledger and cryptocurrency
    > integration. We look forward to seeing new payment method specifications
    > emerge.
    > 
    >  
    > 
    >  
    > 
    > Thanks
    > 
    > Nick (on behalf of the chairs)
    > 
    >  
    > 
    >  
    > 
    >  
    > 
    >  
    > 
    > 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.
    > 
    >  
    > 
    > 
    > 
    > CONFIDENTIALITY NOTICE This e-mail message and any attachments are only
    > for the use of the intended recipient and may contain information that
    > is privileged, confidential or exempt from disclosure under applicable
    > law. If you are not the intended recipient, any disclosure, distribution
    > or other use of this e-mail message or attachments is prohibited. If you
    > have received this e-mail message in error, please delete and notify the
    > sender immediately. Thank you.
    
    

________________________________________________________

The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.

Received on Wednesday, 24 January 2018 21:37:51 UTC