{"id":15057926,"url":"https://github.com/w3c/secure-payment-confirmation","last_synced_at":"2025-04-04T20:06:36.796Z","repository":{"id":37533431,"uuid":"282221535","full_name":"w3c/secure-payment-confirmation","owner":"w3c","description":"Secure Payment Confirmation (SPC)","archived":false,"fork":false,"pushed_at":"2025-03-11T19:13:10.000Z","size":3707,"stargazers_count":120,"open_issues_count":29,"forks_count":43,"subscribers_count":33,"default_branch":"main","last_synced_at":"2025-03-28T19:05:48.154Z","etag":null,"topics":["3ds","payment-handler","payment-request","public-key","webauthn"],"latest_commit_sha":null,"homepage":"https://w3c.github.io/secure-payment-confirmation/","language":"Bikeshed","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/w3c.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE.md","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":"security-privacy-questionnaire.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2020-07-24T13:03:59.000Z","updated_at":"2025-03-21T01:53:53.000Z","dependencies_parsed_at":"2023-02-16T11:15:27.827Z","dependency_job_id":"2c763924-fa34-437a-aaac-4193a7a759d3","html_url":"https://github.com/w3c/secure-payment-confirmation","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/w3c%2Fsecure-payment-confirmation","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/w3c%2Fsecure-payment-confirmation/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/w3c%2Fsecure-payment-confirmation/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/w3c%2Fsecure-payment-confirmation/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/w3c","download_url":"https://codeload.github.com/w3c/secure-payment-confirmation/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247242669,"owners_count":20907133,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["3ds","payment-handler","payment-request","public-key","webauthn"],"created_at":"2024-09-24T22:14:14.069Z","updated_at":"2025-04-04T20:06:36.759Z","avatar_url":"https://github.com/w3c.png","language":"Bikeshed","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Secure Payment Confirmation\n\nSecure Payment Confirmation (SPC) is a Web API to support streamlined\nauthentication during a payment transaction. It is designed to scale\nauthentication across merchants, to be used within a wide range of\nauthentication protocols, and to produce cryptographic evidence that the user\nhas confirmed transaction details. The [W3C Web Payments Working\nGroup](https://www.w3.org/Payments/WG/) is developing SPC.\n\nLinks:\n\n- [Explainer](explainer.md)\n- [Specification](https://w3c.github.io/secure-payment-confirmation/) ([spec.bs](spec.bs))\n- [Use Cases](scope.md#user-stories)\n- [Requirements](requirements.md)\n- [Tests](https://wpt.fyi/results/secure-payment-confirmation?label=master\u0026label=experimental\u0026aligned)\n\n![Screenshot](payment.png)\n\n## FAQ\n\n### Q. Who can validate the SPC response besides the actual Relying Party (RP)?\n\nAn 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.\n\n## Acknowledgements\n\nContributors:\n\n* Adrian Hope-Bailie (Coil)\n* Benjamin Tidor (Stripe)\n* Danyao Wang (Google)\n* Christiaan Brand (Google)\n* Rouslan Solomakhin (Google)\n* Nick Burris (Google)\n* Gerhard Oosthuizen (Entersekt)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fw3c%2Fsecure-payment-confirmation","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fw3c%2Fsecure-payment-confirmation","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fw3c%2Fsecure-payment-confirmation/lists"}