Documentation
This is the documentation for Proudpass: certificates, badges, letters and the verification that makes them worth something.
Four things shape how it works, and knowing them up front explains most of the rest.
Issuing and publishing are separate. Issuing writes the record and renders the document and costs nothing. Publishing makes it public, consumes a credit, sends the recipient's email and fires the webhook. So a two-hundred-row spreadsheet can be prepared, reviewed and corrected before anything leaves the building, and a mistake caught at that stage costs nothing at all.
Nothing an account does invalidates a credential already issued. Suspending an organisation stops sign-in and stops issuing. Every credential already published keeps resolving. That is a promise, not an implementation detail, and the verification path is written so it cannot be accidentally broken.
Verification is free, needs no account, and is never metered. Anyone can check a credential. A verifier account exists, but it buys watching — being told when something changes — not checking.
A credential can be checked without trusting us. Each is published as an Open Badges 3.0
Verifiable Credential signed under the issuer's own did:web, and as an Open Badges 2.0 hosted
assertion. Any conformant verifier can check one with none of our code involved.