From 814bb4b31cb32f1f4bd03d73d272cd4c88dade3e Mon Sep 17 00:00:00 2001 From: Ian Jacobs Date: Tue, 10 Aug 2021 07:36:57 -0500 Subject: [PATCH 1/3] New note with background on current shape of API and setting expectation it will change. --- spec.bs | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/spec.bs b/spec.bs index b8c0876..d0d2b5d 100644 --- a/spec.bs +++ b/spec.bs @@ -369,6 +369,19 @@ below and in [[#index-defined-elsewhere]].
TODO: Bikeshed the name.
+
This specification describes an API implemented + to support a Stripe pilot that began in December 2020. To quickly + provide support for that experiment, the Chrome team added SPC + support atop existing implementations of the Payment Request and + Payment Handler APIs. However, given findings from the pilot and + subsequent use case and requirements discussions, there is now + general agreement that SPC should be usable independent of Payment + Request. To foster more experimentation in a timely fashion we are + moving forward with the API in its current form, but we expect + (without a concrete timeline) that SPC will move away from its + Payment Request origins. For developers, this should improve + feature detection, invocation, and other aspects of the API.
+ # Enrollment # {#sctn-enrollment} To enroll a user for Secure Payment Confirmation, relying parties should call From 53923338ef5349354b6c0d50b5934f2436585b8c Mon Sep 17 00:00:00 2001 From: Ian Jacobs Date: Tue, 10 Aug 2021 10:04:39 -0500 Subject: [PATCH 2/3] shortened after RS feedback --- spec.bs | 20 ++++++++------------ 1 file changed, 8 insertions(+), 12 deletions(-) diff --git a/spec.bs b/spec.bs index d0d2b5d..0270587 100644 --- a/spec.bs +++ b/spec.bs @@ -369,18 +369,14 @@ below and in [[#index-defined-elsewhere]].
TODO: Bikeshed the name.
-
This specification describes an API implemented - to support a Stripe pilot that began in December 2020. To quickly - provide support for that experiment, the Chrome team added SPC - support atop existing implementations of the Payment Request and - Payment Handler APIs. However, given findings from the pilot and - subsequent use case and requirements discussions, there is now - general agreement that SPC should be usable independent of Payment - Request. To foster more experimentation in a timely fashion we are - moving forward with the API in its current form, but we expect - (without a concrete timeline) that SPC will move away from its - Payment Request origins. For developers, this should improve - feature detection, invocation, and other aspects of the API.
+
To quickly support an initial SPC experiment, + this API was designed atop existing implementations of the Payment + Request and Payment Handler APIs. There is now general agreement + that SPC should be usable independent of Payment Request. We + therefore expect (without a concrete timeline) that SPC will move + away from its Payment Request origins. For developers, this should + improve feature detection, invocation, and other aspects of the + API.
# Enrollment # {#sctn-enrollment} From c9a962f92fb618782204046912f053c807e941af Mon Sep 17 00:00:00 2001 From: Ian Jacobs Date: Tue, 10 Aug 2021 11:01:41 -0500 Subject: [PATCH 3/3] More RS feedback --- spec.bs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec.bs b/spec.bs index 0270587..5b08349 100644 --- a/spec.bs +++ b/spec.bs @@ -372,7 +372,7 @@ below and in [[#index-defined-elsewhere]].
To quickly support an initial SPC experiment, this API was designed atop existing implementations of the Payment Request and Payment Handler APIs. There is now general agreement - that SPC should be usable independent of Payment Request. We + to explore a design of SPC independent of Payment Request. We therefore expect (without a concrete timeline) that SPC will move away from its Payment Request origins. For developers, this should improve feature detection, invocation, and other aspects of the