Skip to content

SPC_to_CR

ianbjacobs edited this page Apr 4, 2022 · 15 revisions

Plan for advancing SPC to Candidate Recommendation

Status

This is a draft with no consensus. The author is creating a plan for discussion at the WPWG's May meeting.

Goal

  • Advance Secure Payment Confirmation (SPC) to Candidate Recommendation.

Issues

Dependencies

  • See W3C Process Transitioning to Candidate Recommendation
  • Our Charter indicates a dependency on EMVCo. We have coordinated with the EMVCo 3DS Working Group, leading to the integration of SPC into 3DS version 2.3. In addition, we are addressing issues they raised based on implementation experience.
  • Our Charter indicates a dependency on Open Banking groups. We have been meeting with these groups during the development of SPC.
  • Ensure in sync with Web Authentication WG; see WebAuthn liaison issues

Requirements

  • Evaluate requirements and determine if they have been met or why not.

Horizontal review

Completed

Features at risk

  • None at this time.

Document how implementation experience will be shown

  • Stripe experiment
  • Adyen / Airbnb experiment
  • Modirum experience
  • Question: Second browser engine

Timeline

  • 4-30 April:
  • 3-5 May: WPWG meeting. Anticipate coordination discussions on privacy, Web Authentication issues. Review plans for each issue.
  • 6-19 May: Incorporate changes to specification for any resolved issues.
  • 19 May - 10 June:
    • Call for additional horizontal review of SPC of changes since 7 September 2021.
    • Develop plan for how implementation experience will be shown
    • Identify any features at risk
  • 10 June - 1 July: Resolve remaining horizontal issues.
  • 7 July - 14 July: Call for Consensus to WPWG to advance to Candidate Recommendation
  • 8 August: Begin process of handling any formal objections.
  • 12-16 September: TPAC 2022. Address formal objections if not yet done.
  • Announce decision regarding proposal to go to CR
  • Request transition to advance to CR.
Clone this wiki locally