-
-
Notifications
You must be signed in to change notification settings - Fork 167
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
Support for Secure Payment Confirmation #267
Comments
Yeah, looks completely doable, and the architects built it to be so compatible by design. |
I have also stumbled on this issue. Any new considerations regarding possible override option or workaround? |
I haven't paid too much attention to SPC. If someone is interested in doing a PoC Draft PR to show how we would implement this in a clean way I'd be interested in reviewing it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Secure Payment Confirmation builds on top of WebAuthN and uses the Payment Request API to allow payments to be authenticated.
I've been able to adapt the demo application to use SPC but unfortunately the verification of the assertion fails because the type is no longer
webauthn.get
butpayment.get
(see AuthenticatorResponse).Is it possible to override this verification or add support for additional client data types?
The text was updated successfully, but these errors were encountered: