Do people need a SwanShare account to verify a credential?

No. Verification is public and free — anyone can check a credential with just its verification ID or the credential file, without an account and without trusting SwanShare.

What actually stops someone forging a credential?

Each credential is signed with your organization's private key using RSA-PSS. Without that key a valid signature can't be produced, and changing even one character breaks the SHA-256 fingerprint — so tampering is always detectable.

Is this really on a blockchain?

Every credential's fingerprint is written to a tamper-evident, hash-chained ledger with proof-of-work. You can additionally anchor batches to a public blockchain (EVM) or OpenTimestamps. We're upfront that the built-in ledger is the default and public-chain anchoring is opt-in.

Can I revoke a credential after issuing it?

Yes. Revoke it in the dashboard and public verification reflects the revoked status immediately and honestly.

Which standards do you support?

Credentials export as W3C Verifiable Credentials and Open Badges 3.0, so they work with other wallets and verifiers — not just SwanShare.

How do e-signatures work?

Upload a multi-page PDF, place signature/date/text fields for each signer, and send tokenized links (no account needed to sign). When everyone signs, the document is sealed with a certificate of completion and anchored to the ledger.

Can anyone verify a sealed document without logging in?

Yes. Go to Verify → Signed document on the homepage (or /verify-document), upload the signed PDF, and SwanShare checks the fingerprint, issuer signature, and ledger anchor — no account required.

Verify a Signed Document

Verify a document

Upload the Signed PDF — the final file with all signatures and a Certificate of Completion page at the end. The original unsigned upload will not verify.

← Back to SwanShare · Verify a credential