What recipients get
The claim page, adding to LinkedIn, downloads, and the privacy control you hold on their behalf.
Every award has a public page at incredify.net/b/<id>. That URL is the credential as far as the outside world is concerned — it's what goes on a résumé, in an email signature, or into a LinkedIn profile.
On the claim page
- The badge artwork, its name, and your organization — with a verified-domain mark once your organization has confirmed its email domain and Incredify has reviewed that the name fits it.
- Who it was issued to and when.
- Description, criteria, and skills — what the credential means and what was done to earn it.
- Evidence, when attached, with links opening safely in a new tab.
- A Digitally signed label (on a valid badge), a Verify button, and your
did:webissuer identifier in the footer. - For a valid badge, a box titled Using this badge elsewhere with the page's address (the credential URL, with a Copy link button) and the credential ID, which is the last part of that address.
What recipients can do
- Add to LinkedIn
- Opens LinkedIn's certification form pre-filled with the badge name, your organization, the issue month and year, the credential ID, and a link back to the claim page. The recipient checks it and saves; LinkedIn may ask for anything it did not receive.
- Verify
- Runs a live cryptographic check in front of whoever is looking. See How verification works.
- Download badge
- A PNG with the signed credential baked into the image file itself. The image carries the signed credential, so anyone with the file can check it against the issuer's public key, which Incredify publishes at incredify.net. There is no embed code and no wallet link, and we cannot say which wallets or application systems accept the files.
- Download JSON-LD
- The Open Badges 3.0 credential as a JSON-LD file, as a data file. We cannot say which systems or wallets accept it. Awards issued from 12 November 2026 carry their own embedded proof (Data Integrity,
eddsa-rdfc-2022), so the file can be checked on its own. Earlier awards do not; their signed form is the downloadable badge image, or the token at/api/assertions/<assertion-id>/credential.jwt.
Search engines
Every badge page tells search engines not to list it, and badge pages are left out of our sitemap. There is no setting for this; it applies to every award. Search engines can still choose to ignore the instruction, so it is not a guarantee.
Not listed is not private
This page is public to anyone with the link. Search engines are told not to list it. The link has to work for anyone, or the badge couldn't be shared or verified, which is the whole point of a credential. If someone needs an award to not exist, revoke it.
Recipient email addresses are encrypted at rest
Addresses are stored encrypted, not as plain text. This is why searching Recipients by email requires the full, exact address — see Reporting.
Related
Still stuck?
Email us at hello@incredify.net — a human will answer.