The CHAPI protocol allows your digital wallet to receive Verifiable Credentials from an independent third-party issuer - or present Verifiable Credentials to an independent third-party verifier - in a way that establishes trust and preserves privacy.
CHAPI is for open for everyone
CHAPI is an open protocol designed to solve the “NASCAR Problem” - too often, users are presented with a fixed set of options for authentication with third-party sites. The CHAPI protocol provides mediation between any CHAPI-enabled web application and a third-party site. Just register your web app with your browser, and off you go!
Both CHAPI and Verifiable Credentials are results of open collaboration through World Wide Web Consortium (W3C). You can find more information and join the discussion at the W3C Credentials Community Group.
How does CHAPI work?
A Credential Handler is an event handler for credential request and storage events. Web app developers can use CHAPI to provide their users with Credential Handlers that run in the browser. These Credential Handlers can respond when users visit other websites that present, request, or store Verifiable Credentials.
How do I build CHAPI into my website or application?
Examples and developer docs:
How do I integrate my application into the CHAPI Playground?
Interested in making your Verifier/Issuer/Wallet available for experimentation? See the Integration Guide and FAQ for the CHAPI Playground.
Contributing
Contributions are welcome and encouraged! Please follow best practices for contributing to open-source code on GitHub.
License
This site content is open-source; content in this Repository is licensed by contributors under the BSD 3-Clause