- From: POUILLARD, ANNE <anne.pouillard@worldline.com>
- Date: Tue, 24 Aug 2021 09:17:13 +0000
- To: Ian Jacobs <ij@w3.org>, Web Payments Working Group <public-payments-wg@w3.org>
1. Support the proposal. Anne -----Message d'origine----- De : Ian Jacobs <ij@w3.org> Envoyé : lundi 16 août 2021 16:30 À : Web Payments Working Group <public-payments-wg@w3.org> Objet : Call for Consensus to Deprecate Basic Card Note - RESPONSE REQUESTED BY 26 AUGUST Caution! External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe. Dear Web Payments Working Group, The Basic Card Specification [1] suffers from several issues: - It is only implemented in Chrome today, and Google is planning to remove support. - It does not have built-in a mechanism for incremental requests for address components creating privacy concerns [2]. - There has been little adoption by merchants. - For security reasons, as we have long discussed, there is a preference not to circulate "raw" card information on the network. This is a Call for Consensus to deprecate Payment Method: Basic Card [1]. The impact of deprecation will be: 1) To republish the document with clear signals that it should no longer be implemented or used. 2) The Working Group will no longer maintain the "Card Network Identifiers Approved for use with Payment Request API". 3) The 'basic-card' standardized Payment Method Identifier will be removed from the registry of identifiers [4]. PLEASE RESPOND to the proposal by 26 August 2021 (14h00 UTC). For example, if you support the proposal, respond to this list with "1. Support the proposal." For the co-Chairs, Ian Jacobs [1] https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww..w3.org%2FTR%2Fpayment-method-basic-card%2F&data=04%7C01%7C%7Cc9547da8e76f4f2c225908d960c28ece%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C637647211018896330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=iUKMylGuzOx9JC3xuSTqmh6KCNuRZxSfiOB1bHXvmH8%3D&reserved=0 [2] https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fpayment-method-basic-card%2Fissues%2F72&data=04%7C01%7C%7Cc9547da8e76f4f2c225908d960c28ece%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C637647211018896330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=7VRGgbsoIZwE8BG2k4kxiU0nWybntt6NcbrpOzQXjRE%3D&reserved=0 [3] https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww..w3.org%2FPayments%2Fcard-network-ids&data=04%7C01%7C%7Cc9547da8e76f4f2c225908d960c28ece%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C637647211018896330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=HVJv7CwtN41E7xtHlvDzEsBlCoMhhLo7FYuDRqPS7bQ%3D&reserved=0 [4] https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww..w3.org%2FTR%2Fpayment-method-id%2F%23registry&data=04%7C01%7C%7Cc9547da8e76f4f2c225908d960c28ece%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C637647211018896330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=v8kEtCCMzA74YiMnYLP775Gas2XugcbW0wZ%2F06iRj2c%3D&reserved=0 =========================================== PROPOSAL That the Web Payments Working Group request that the W3C Director deprecate the Payment Method: Basic Card Note. Please indicate one of the following in your response: 1. Support the proposal. 2. Request some changes, but support the proposal even if suggested changes are not taken into account. 3. Request some changes, and do not support the proposal unless the changes are taken into account. 4. Do not support the proposal (please provide rationale). 5. Support the consensus of the Web Payments Working Group. 6. Abstain. =========================================== FORMAL OBJECTIONS * If you wish your LACK of support to publish to be conveyed to the Director and reviewed, please include the phrase "FORMAL OBJECTION" in your response and be sure to include substantive arguments or rationale. * The W3C Director takes Formal Objections seriously, and therefore they typically require significant time and effort to address. * Silence will be taken to mean there is no Formal Objection. * If there are Formal Objections, the Chairs plan to contact the individual(s) who made them to see whether there are changes that would address the concern and increase consensus. For more information, see: https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2020%2FProcess-20200915%2F%23Consensus&data=04%7C01%7C%7Cc9547da8e76f4f2c225908d960c28ece%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C637647211018896330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=92Qvo9NMvK3V5JMGNbigqc6qQS0KWHVhKfhZru0NInQ%3D&reserved=0 =========================================== NEXT STEPS Transition Request Following a Working Group Decision to Deprecate * In the case where this Call for Consensus results in a decision to deprecate, the Chairs plan to request approval from the W3C Director to deprecate the Note (including review of any Formal Objections). -- Ian Jacobs <ij@w3.org> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FPeople%2FJacobs%2F&data=04%7C01%7C%7Cc9547da8e76f4f2c225908d960c28ece%7Cfda9decfe89243ac9d9f1a493f9f98d0%7C0%7C0%7C637647211018896330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=UZwQ69wW%2FiF0YkoTRjuQn78cTmqlPOpF8L4KyVaK72o%3D&reserved=0 Tel: +1 718 260 9447 Worldline and Ingenico are registered trademarks and trade names owned by the Worldline Group. This e-mail and any documents attached are confidential and intended solely for the addressee. If you are not the intended recipient of this e-mail, you are not authorized to copy, disclose, use or retain it. Please notify the sender immediately and delete this e-mail (including any attachments) from your systems. As e-mails may be intercepted, amended or lost, they are not secure. Worldline and its subsidiaries therefore cannot accept liability for any errors in their content. Although the Worldline Group endeavours to maintain a virus-free network, we do not warrant that this e-mail is virus-free and do not accept liability for any damages or losses resulting from any transmitted virus if any. The risks are deemed to be accepted by anyone who communicates with Worldline or its subsidiaries by e-mail.
Received on Tuesday, 24 August 2021 09:40:54 UTC