A receipt someone outside your company can check

Why this part is worth having

If you already record who approved what, keep doing that. The record in your own books proves something to you. A credential signed with a key you publish proves it to anyone, without trusting your books or ours.

• Checked offline. The verifier is one file. It needs Python and the cryptography package, and it makes no network call.
• Bound to the exact action. Give it the original action and it refuses a credential whose action was changed after approval.
• Your key, an open format. A company can issue these under its own key. The format is open, and the key you publish is the one a counterparty checks.
• A stop signal. A public revocation list says when an approval or an agent has since been stopped. The verifier does not fetch it for you, so check it too.

See a real one

A person at FLOCORE approved one real request on 20 October 2026. The specimen page holds the credential, the published key and the exact action, and your browser checks it with nothing sent anywhere.

Get it

• humanseal_verify.py, the verifier. Run: python humanseal_verify.py credential.txt --key jwks.json --action action.json. It exits 0 when valid and 1 when refused.
• The read-me, with what it refuses and what it does not do.
• A worked example: an agent prepares a VAT return, a person approves it, and a counterparty verifies it offline. Change the payable amount after approval and it is refused.
• Our own issuer key is at fo.flocore.tech/.well-known/jwks.json, and the credential type is described at fo.flocore.tech/vct/human-seal-approval/v1.

What is not true yet

• No outside organisation has completed onboarding, and no authority or auditor has been asked to accept these credentials.
• A credential is a bearer token: key binding is not implemented, so whoever holds one can show it.
• The credential format (SD-JWT VC) is an IETF draft, not a final standard, so it may change.
• The verifier is open to review but has had no independent audit. The browser verifier now checks these credentials too, against a key you paste; it does not fetch the key or check the revocation list.
• A signed approval supports record-keeping and oversight duties. It does not by itself make a system compliant with any law. See the limitations page.