RE: Call for Consensus to Deprecate Basic Card Note - RESPONSE REQUESTED BY 26 AUGUST

  1.  Support the proposal

From: Jean Carlo Emer <jcemer@stripe.com>
Sent: Monday, August 16, 2021 17:03
To: Stephen McGruer <smcgruer@google.com>
Cc: Ian Jacobs <ij@w3.org>; Web Payments Working Group <public-payments-wg@w3.org>
Subject: Re: Call for Consensus to Deprecate Basic Card Note - RESPONSE REQUESTED BY 26 AUGUST

1. Support the proposal.
--

Jean Carlo Emer

Engineering | Stripe


On Mon, Aug 16, 2021 at 4:57 PM Stephen McGruer <smcgruer@google.com<mailto:smcgruer@google.com>> wrote:
1. Support the proposal.

On Mon, 16 Aug 2021 at 10:31, Ian Jacobs <ij@w3.org<mailto:ij@w3.org>> wrote:
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://www.w3.org/TR/payment-method-basic-card/<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fpayment-method-basic-card%2F&data=04%7C01%7Cgoosthuizen%40entersekt.com%7C08c369ea3ae34a1bdbbf08d960c704d4%7C19c3aeac7d8a4c9e80b99f9510adc7f7%7C1%7C0%7C637647230185579685%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=H4%2FBZf3EyjsiCIlNAPczFfgVzBFFd%2F%2F7b70inIM4Jp8%3D&reserved=0>
[2] https://github.com/w3c/payment-method-basic-card/issues/72
[3] https://www.w3.org/Payments/card-network-ids<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FPayments%2Fcard-network-ids&data=04%7C01%7Cgoosthuizen%40entersekt.com%7C08c369ea3ae34a1bdbbf08d960c704d4%7C19c3aeac7d8a4c9e80b99f9510adc7f7%7C1%7C0%7C637647230185584673%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=B42cZrF2TJaGHikaz3W9Ja%2FSc8%2FRAWIS7Pi9nsFZG%2FE%3D&reserved=0>
[4] https://www.w3.org/TR/payment-method-id/#registry<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fpayment-method-id%2F%23registry&data=04%7C01%7Cgoosthuizen%40entersekt.com%7C08c369ea3ae34a1bdbbf08d960c704d4%7C19c3aeac7d8a4c9e80b99f9510adc7f7%7C1%7C0%7C637647230185589649%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=XRql1Z7pjcWJdeWkF2VkEQvrW8vSCecyku8Lhg3bnDI%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://www.w3.org/2020/Process-20200915/#Consensus<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2020%2FProcess-20200915%2F%23Consensus&data=04%7C01%7Cgoosthuizen%40entersekt.com%7C08c369ea3ae34a1bdbbf08d960c704d4%7C19c3aeac7d8a4c9e80b99f9510adc7f7%7C1%7C0%7C637647230185594627%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=XVLY963UOJ47z0cI4rD4FGt1SNWQUMeRLrZI3GLyrEw%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<mailto:ij@w3.org>>
https://www.w3.org/People/Jacobs/<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FPeople%2FJacobs%2F&data=04%7C01%7Cgoosthuizen%40entersekt.com%7C08c369ea3ae34a1bdbbf08d960c704d4%7C19c3aeac7d8a4c9e80b99f9510adc7f7%7C1%7C0%7C637647230185594627%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=9CPg5Ojd8WFf9%2FrFZ9t2hOLX9D5MwHpzPdPr7VjF2Vg%3D&reserved=0>
Tel: +1 718 260 9447<tel:+1%20718-260-9447>






--
smcgruer * he / him