-
Notifications
You must be signed in to change notification settings - Fork 22.6k
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.
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
Integration of Secure Payment Confirmation #30439
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit
mdn-linter
files/en-us/web/api/securepaymentconfirmationrequest/index.md|37|
files/en-us/web/api/securepaymentconfirmationrequest/index.md|42|
files/en-us/web/api/securepaymentconfirmationrequest/index.md|45|
files/en-us/web/api/securepaymentconfirmationrequest/index.md|50|
files/en-us/web/api/securepaymentconfirmationrequest/index.md|56|
files/en-us/web/api/securepaymentconfirmationrequest/index.md|60 col 1|
@@ -34,11 +34,14 @@ Payment handlers are identified by **payment method identifiers**, which are str | |||
|
|||
### Standardized payment method identifiers | |||
|
|||
There is currently only one registered [standardized payment method identifier](https://www.w3.org/TR/payment-method-id/#registry) (more may be added in the future): | |||
- `secure-payment-confirmation` | |||
- : The [standardized payment method dentifier](https://www.w3.org/TR/payment-method-id/#registry) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mdn-linter] reported by reviewdog 🐶
- : The [standardized payment method dentifier](https://www.w3.org/TR/payment-method-id/#registry) | |
- : The [standardized payment method dentifier](https://www.w3.org/TR/payment-method-id/#registry) |
There is currently only one registered [standardized payment method identifier](https://www.w3.org/TR/payment-method-id/#registry) (more may be added in the future): | ||
- `secure-payment-confirmation` | ||
- : The [standardized payment method dentifier](https://www.w3.org/TR/payment-method-id/#registry) | ||
for [Secure Payment Confirmation](https://w3c.github.io/secure-payment-confirmation) is "secure-payment-confirmation". The Payment Request data for this payment is defined by the [SecurePaymentConfirmationRequest dictionary](/en-US/docs/Web/API/SecurePaymentConfirmationRequest). For more information see [Using Payment Request API for Secure Payment Confirmation](/en-US/docs/Web/API/Payment_Request_API/Using_with_Secure_Payment_Confirmation). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mdn-linter] reported by reviewdog 🐶
for [Secure Payment Confirmation](https://w3c.github.io/secure-payment-confirmation) is "secure-payment-confirmation". The Payment Request data for this payment is defined by the [SecurePaymentConfirmationRequest dictionary](/en-US/docs/Web/API/SecurePaymentConfirmationRequest). For more information see [Using Payment Request API for Secure Payment Confirmation](/en-US/docs/Web/API/Payment_Request_API/Using_with_Secure_Payment_Confirmation). | |
for [Secure Payment Confirmation](https://w3c.github.io/secure-payment-confirmation) is "secure-payment-confirmation". The Payment Request data for this payment is defined by the [SecurePaymentConfirmationRequest dictionary](/en-US/docs/Web/API/SecurePaymentConfirmationRequest). For more information see [Using Payment Request API for Secure Payment Confirmation](/en-US/docs/Web/API/Payment_Request_API/Using_with_Secure_Payment_Confirmation). |
files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md
Outdated
Show resolved
Hide resolved
files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md
Outdated
Show resolved
Hide resolved
- `challenge` | ||
- : A random [challenge](/en-US/docs/Web/API/CredentialsContainer/create#challenge) that the relying party generates on the server side | ||
to prevent replay attacks. | ||
|
||
- `rpId` | ||
- : The [Relying Party Identifier](/en-US/docs/Web/API/CredentialsContainer/get#rpid) of the credentials. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mdn-linter] reported by reviewdog 🐶
- `challenge` | |
- : A random [challenge](/en-US/docs/Web/API/CredentialsContainer/create#challenge) that the relying party generates on the server side | |
to prevent replay attacks. | |
- `rpId` | |
- : The [Relying Party Identifier](/en-US/docs/Web/API/CredentialsContainer/get#rpid) of the credentials. | |
- `challenge` | |
- : A random [challenge](/en-US/docs/Web/API/CredentialsContainer/create#challenge) that the relying party generates on the server side | |
to prevent replay attacks. |
- `credentialIds` | ||
- : The list of credential identifiers for the given instrument. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mdn-linter] reported by reviewdog 🐶
- `credentialIds` | |
- : The list of credential identifiers for the given instrument. | |
- `rpId` | |
- : The [Relying Party Identifier](/en-US/docs/Web/API/CredentialsContainer/get#rpid) of the credentials. |
- `instrument` | ||
- : The description of the instrument name and icon to display during | ||
registration and to be signed along with the transaction details. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mdn-linter] reported by reviewdog 🐶
- `instrument` | |
- : The description of the instrument name and icon to display during | |
registration and to be signed along with the transaction details. | |
- `credentialIds` | |
- : The list of credential identifiers for the given instrument. |
- `timeout` | ||
- : The number of milliseconds before the request to sign the transaction | ||
details times out. At most 1 hour. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mdn-linter] reported by reviewdog 🐶
- `timeout` | |
- : The number of milliseconds before the request to sign the transaction | |
details times out. At most 1 hour. | |
- `instrument` | |
- : The description of the instrument name and icon to display during | |
registration and to be signed along with the transaction details. |
- `payeeName` | ||
- : The display name of the payee that this SPC call is for (e.g., the | ||
merchant). Optional, may be provided alongside or instead of | ||
payeeOrigin. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mdn-linter] reported by reviewdog 🐶
- `payeeName` | |
- : The display name of the payee that this SPC call is for (e.g., the | |
merchant). Optional, may be provided alongside or instead of | |
payeeOrigin. | |
- `timeout` | |
- : The number of milliseconds before the request to sign the transaction | |
details times out. At most 1 hour. |
@@ -0,0 +1,63 @@ | |||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[markdownlint] reported by reviewdog 🐶
MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: ---]
- `payeeOrigin` | ||
- : The [=/origin=] of the payee that this SPC call is for (e.g., the | ||
merchant). Optional, may be provided alongside or instead of | ||
payeeName. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mdn-linter] reported by reviewdog 🐶
- `payeeOrigin` | |
- : The [=/origin=] of the payee that this SPC call is for (e.g., the | |
merchant). Optional, may be provided alongside or instead of | |
payeeName. | |
- `payeeName` | |
- : The display name of the payee that this SPC call is for (e.g., the | |
merchant). Optional, may be provided alongside or instead of | |
payeeOrigin. |
- `extensions` | ||
- : Any [WebAuthn extensions](/en-US/docs/Web/API/Web_Authentication_API/WebAuthn_extensions) that should be used for the passed credential(s). The caller does not need to specify the [payment extension](/en-US/docs/Web/API/Web_Authentication_API/WebAuthn_extensions#payment); it is added automatically. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mdn-linter] reported by reviewdog 🐶
- `extensions` | |
- : Any [WebAuthn extensions](/en-US/docs/Web/API/Web_Authentication_API/WebAuthn_extensions) that should be used for the passed credential(s). The caller does not need to specify the [payment extension](/en-US/docs/Web/API/Web_Authentication_API/WebAuthn_extensions#payment); it is added automatically. | |
- `payeeOrigin` | |
- : The [=/origin=] of the payee that this SPC call is for (e.g., the | |
merchant). Optional, may be provided alongside or instead of | |
payeeName. |
- `locale` | ||
- : An optional list of well-formed {{RFC(5646, "Tags for Identifying Languages (also known as BCP 47)")}} language tags, in descending | ||
order of priority, that identify the local preferences of the | ||
website, i.e. a language priority list {{RFC(4647, "Matching of Language Tags")}}, which the user agent can use to perform [language negotiation](/en-US/docs/Web/HTTP/Content_negotiation) and locale-affected formatting with the caller. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mdn-linter] reported by reviewdog 🐶
- `locale` | |
- : An optional list of well-formed {{RFC(5646, "Tags for Identifying Languages (also known as BCP 47)")}} language tags, in descending | |
order of priority, that identify the local preferences of the | |
website, i.e. a language priority list {{RFC(4647, "Matching of Language Tags")}}, which the user agent can use to perform [language negotiation](/en-US/docs/Web/HTTP/Content_negotiation) and locale-affected formatting with the caller. | |
- `extensions` | |
- : Any [WebAuthn extensions](/en-US/docs/Web/API/Web_Authentication_API/WebAuthn_extensions) that should be used for the passed credential(s). The caller does not need to specify the [payment extension](/en-US/docs/Web/API/Web_Authentication_API/WebAuthn_extensions#payment); it is added automatically. |
NOTE: The locale is distinct from | ||
language or direction metadata associated with specific input | ||
members, in that it represents the caller's requested localized | ||
experience rather than assertion about a specific string value. | ||
See [SPC internationalization Considerations](https://w3c.github.io/secure-payment-confirmation/#sctn-i18n-considerations) for more discussion. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mdn-linter] reported by reviewdog 🐶
NOTE: The locale is distinct from | |
language or direction metadata associated with specific input | |
members, in that it represents the caller's requested localized | |
experience rather than assertion about a specific string value. | |
See [SPC internationalization Considerations](https://w3c.github.io/secure-payment-confirmation/#sctn-i18n-considerations) for more discussion. | |
- `locale` | |
- : An optional list of well-formed {{RFC(5646, "Tags for Identifying Languages (also known as BCP 47)")}} language tags, in descending | |
order of priority, that identify the local preferences of the | |
website, i.e. a language priority list {{RFC(4647, "Matching of Language Tags")}}, which the user agent can use to perform [language negotiation](/en-US/docs/Web/HTTP/Content_negotiation) and locale-affected formatting with the caller. |
- `showOptOut` | ||
- : Whether the user should be given a chance to opt-out during the | ||
[transaction confirmation UX](https://w3c.github.io/secure-payment-confirmation/#sctn-transaction-confirmation-ux). Optional, default false. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mdn-linter] reported by reviewdog 🐶
- `showOptOut` | |
- : Whether the user should be given a chance to opt-out during the | |
[transaction confirmation UX](https://w3c.github.io/secure-payment-confirmation/#sctn-transaction-confirmation-ux). Optional, default false. | |
NOTE: The locale is distinct from | |
language or direction metadata associated with specific input | |
members, in that it represents the caller's requested localized | |
experience rather than assertion about a specific string value. | |
See [SPC internationalization Considerations](https://w3c.github.io/secure-payment-confirmation/#sctn-i18n-considerations) for more discussion. |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…confirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
||
Secure Payment Confirmation (SPC), available through the Payment Request API, provides a mechanism for strong customer authentication during checkout, thereby protecting against online payment fraud. | ||
|
||
To protect against online payment fraud, it is common to authenticate the account holder. Strong authentication lowers the risk of fraud, but increases the likelihood that friction during checkout will lead to shopping cart abandonment. Banks, merchants, payment services providers, and other entities in a payments ecosystem therefore consider a number of factors when deciding what type and strength of authentication to use for each transaction, including the amount, the items being purchased, the user's payment history, which party bears liability in the case of fraud, and regulatory requirements (such as [European Payment Services Directive 2](https://en.wikipedia.org/wiki/Payment_Services_Directive#Revised_Directive_on_Payment_Services_(PSD2)) requirements for strong customer authentication and evidence of user consent). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mdn-linter] reported by reviewdog 🐶
To protect against online payment fraud, it is common to authenticate the account holder. Strong authentication lowers the risk of fraud, but increases the likelihood that friction during checkout will lead to shopping cart abandonment. Banks, merchants, payment services providers, and other entities in a payments ecosystem therefore consider a number of factors when deciding what type and strength of authentication to use for each transaction, including the amount, the items being purchased, the user's payment history, which party bears liability in the case of fraud, and regulatory requirements (such as [European Payment Services Directive 2](https://en.wikipedia.org/wiki/Payment_Services_Directive#Revised_Directive_on_Payment_Services_(PSD2)) requirements for strong customer authentication and evidence of user consent). | |
To protect against online payment fraud, it is common to authenticate the account holder. Strong authentication lowers the risk of fraud, but increases the likelihood that friction during checkout will lead to shopping cart abandonment. Banks, merchants, payment services providers, and other entities in a payments ecosystem therefore consider a number of factors when deciding what type and strength of authentication to use for each transaction, including the amount, the items being purchased, the user's payment history, which party bears liability in the case of fraud, and regulatory requirements (such as [European Payment Services Directive 2](<https://en.wikipedia.org/wiki/Payment_Services_Directive#Revised_Directive_on_Payment_Services_(PSD2)>) requirements for strong customer authentication and evidence of user consent). |
…confirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…confirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…confirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…confirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…confirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…confirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: wbamberg <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* Alphabetical order * Data types provided * {{optional_inline}} added
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@wbamberg, thanks for all the great suggestions. I think I have integrated them (including a directory name change). @stephenmcgruer, there was a question about whether there is a default value for "timeout." I looked at the WebAuthn spec [1] which does not specify a default. Should we say nothing? Should we say the timeout is implementation dependent? Something else? Thanks! [1] https://www.w3.org/TR/webauthn-2/#dom-publickeycredentialcreationoptions-timeout |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the updates, @ianbjacobs , I reckon this is great. I'll merge this now and if we get an answer about the timeout
default value, we can file a follow-up.
WHOHOO! Thank you @wbamberg, it's been a pleasure. I really appreciate all the time you devoted to making this happen! |
* Create securepaymentconfirmation * Added secure-payment-confirmation PMI; deprecated basic-card * Create Using PR API for SPC * Add spacing * Add files via upload * Add bits for SPC to supportedMethods and data * Fix indent * Add payment extension * Editorial / typography fixes * Formatting fix * Update index.md * Update index.md * Update files/en-us/web/api/payment_request_api/concepts/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update files/en-us/web/api/payment_request_api/concepts/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update index.md * Update index.md * Update index.md * Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update index.md * Update index.md * Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update index.md * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update index.md * Update index.md * Update index.md * Update index.md * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Add H1 * Removed h1 * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md * Rename dialog file * Fix lint errors * Delete files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/chrome-tx-dialog.json * Add tx dialog image * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/web_authentication_api/webauthn_extensions/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/payment_request_api/concepts/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md Co-authored-by: wbamberg <[email protected]> * Pull link to PMI registry out of SPC definition. * Adopted proposal including link update * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/payment_request_api/usingwithsecurepaymentconfirmation/index.md Co-authored-by: wbamberg <[email protected]> * Rename dir * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/web_authentication_api/webauthn_extensions/index.md Co-authored-by: wbamberg <[email protected]> * updated supportedMethods * Update files/en-us/web/api/paymentrequest/paymentrequest/index.md Co-authored-by: wbamberg <[email protected]> * Update files/en-us/web/api/paymentrequest/paymentrequest/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update instance properties * Alphabetical order * Data types provided * {{optional_inline}} added * Editorial. * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Use lc in directory name * Update files/en-us/web/api/securepaymentconfirmationrequest/index.md * Update Payment Request API sidebar --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: wbamberg <[email protected]>
There is a suggested default in the WebAuthn spec - https://www.w3.org/TR/webauthn-2/#ref-for-dom-publickeycredentialcreationoptions-timeout . So could reference that, or could say its implementation dependent (which it is). |
I now see that the Web Authentication documentation on MDN about timeout is here: So another option is to reference that definition. However, that definition does not indicate a default. My preference at this point is to refer to the Web Authentication specification. Stephen, should we also refer to the Web Authentication specification from the SPC definition of timeout? |
I would happily review a PR to do so. :) |
So let it be written, so let it be done: |
Description
This pull request supersedes pull request 28705 based on discussion for how best to structure the integration of Secure Payment Confirmation (SPC).
Motivation
SPC is already shipping in several browsers and should be documented on MDN.
Additional details
Related issues and pull requests
Relates to #421.
cc @wbamberg, @stephenmcgruer, @mountainhippo