Clarify that RP can use its own credentials even if extension not specified #272
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…sion not specified.
| @@ -112,7 +112,7 @@ Note: This use case intends to capture the "in-transaction registration" use cas | |||
|
|
|||
| #### EMV® Secure Remote Commerce (SRC) System as Relying Party | |||
|
|
|||
| * Alice checkouts on a merchant web site with SRC, which triggers the SRC Digital Card Facilitator (DCF) to be displayed. The SRC DCF asks whether she wants to use biometric authentication to streamline payment. She agrees and SRC DCF redirects her to her bank where she goes through an ID&V process with her bank for the credit card she wishes to use. | |||
| * Alice checkouts on a merchant web site with SRC, which triggers the SRC Digital Card Facilitator (DCF) to be displayed. The SRC DCF asks whether she wants to use biometric authentication to streamline payment. She agrees and SRC DCF redirects her to her bank where she goes through an Identification and Verification process with her bank for the credit card she wishes to use. | |||
There was a problem hiding this comment.
Do we need to spell out ID&V every time? Perhaps it could just go into https://w3c.github.io/secure-payment-confirmation/#sctn-terminology if needed (or be defined only the first time its used).
| If the result is `false`, remove |id| from | ||
| |data|["{{SecurePaymentConfirmationRequest/credentialIds}}"]. | ||
| 1. If the |data|["{{SecurePaymentConfirmationRequest/rpId}}"] is | ||
| not in the current origin, run the [=steps to silently determine if a |
There was a problem hiding this comment.
Yeah, so we don't just say things like "is not in the current origin" in specs 🤣 . We try to make them a bit more like code. I think this should be:
At the top of this method, change to:
The [=steps to validate payment method data=] for this payment method, for an
input {{PaymentRequest}} |request| and {{SecurePaymentConfirmationRequest}} |data|, are:
(adding 'request', to get it in scope for looking up. This is a bit hand-wavy as Payment Request doesn't currently pass it in to the 'Steps to check if a payment can be made', but we can fix that later, not a big deal I think)
Then:
1. If the |data|["{{SecurePaymentConfirmationRequest/rpId}}"] is
not the [=origin=] of the [=relevant settings object=] of |request|,
run the [=steps to silently determine if a
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make clear that an RP should be able to use its own credentials even if payment extension not specified.
Preview | Diff