Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Note on API shape #99

Merged
merged 3 commits into from
Aug 10, 2021
Merged

Note on API shape #99

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
814bb4b
New note with background on current shape of API and setting expectat…
ianbjacobs Aug 10, 2021
5392333
shortened after RS feedback
ianbjacobs Aug 10, 2021
c9a962f
More RS feedback
ianbjacobs Aug 10, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions spec.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -369,6 +369,19 @@ below and in [[#index-defined-elsewhere]].

<div class="note">TODO: Bikeshed the name.</div>

<div class="note">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.</div>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a lot of information... Could it be simplified into this?

Suggested change
<div class="note">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.</div>
<div class="note">This specification describes an API implemented
atop existing implementations of the Payment Request. We expect
(without a concrete timeline) that SPC will move away from its
Payment Request implementation to align better with WebAuthn.
For developers, this should improve feature detection, invocation,
and other aspects of the API.</div>

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rsolomakhin, I think the rationale / history is useful. I don't mind shortening it. Let me edit a bit...


# Enrollment # {#sctn-enrollment}

To enroll a user for Secure Payment Confirmation, relying parties should call
Expand Down