{"repo":"w3c/secure-payment-confirmation","free":true,"listed":false,"github":"https://github.com/w3c/secure-payment-confirmation","clone":"git clone https://github.com/w3c/secure-payment-confirmation.git","description":"Secure Payment Confirmation (SPC)","language":"Bikeshed","stars":142,"topics":["webauthn","payment-request","payment-handler","3ds","public-key"],"license":null,"category":"auth-billing-email","readme_excerpt":"Secure Payment Confirmation Secure Payment Confirmation (SPC) is a Web API to support streamlined authentication during a payment transaction. It is designed to scale authentication across merchants, to be used within a wide range of authentication protocols, and to produce cryptographic evidence that the user has confirmed transaction details. The W3C Web Payments Working Group is developing SPC. Links: - Explainer - Specification (spec.bs) - Use Cases - Requirements - Tests FAQ Q. Who can validate the SPC response besides the actual Relying Party (RP)? An SPC challenge bundles transaction details with transaction-specific dynamic data from the Relying Party. An SPC response includes a signature over that challenge. Validation in SPC refers to the verification of that signature using the credential public key. A Relying Party can choose to share the credential public key with another party (e.g., a card network or payment service provider) via out-of-band communication to enable that party to validate the SPC assertion. Acknowledgements Contributors: Adrian Hope-Bailie (Coil) Benjamin Tidor (Stripe) Danyao Wang (Google) Christiaan Brand (Google) Rouslan Solomakhin (Google) Nick Burris (Google) Gerhard Oosthuizen (Entersekt)","default_branch":null,"files":null,"tree":[],"storefront":"/r/w3c","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/w3c/secure-payment-confirmation/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}