CertifyMe has an active Open Badges 3.0 Issuer listing in the public 1EdTech certification registry. The listing checked on 4 October 2026 records certification on 11 May 2026, registration IMSO4ce2026W1, including API Service Consumer (Write). This is useful evidence of a specified interoperability role—not a blanket guarantee about security, identity or every receiving system.
Certified achievement and learner-record roles
Alongside Open Badges 3.0 issuance, the registry lists CertifyMe’s active CLR 2.0 Issuer and Displayer roles, certified 24 August 2026, registration IMSR2ce2026W1. These roles support structured individual achievements and connected learner records, with exchange dependent on compatible receiving systems.
The registry states that CertifyMe has not yet been vetted for privacy and security. OB3 certification must not be represented as a SOC 2 report, ISO certification or independent security audit. Request those documents separately and check dates, legal entity, system scope and customer responsibilities.
What Open Badges 3.0 changes
The 1EdTech specification describes achievement credentials in a W3C Verifiable Credentials context. The achievement, issuer, recipient, criteria, evidence and securing mechanism matter more than the badge image. The W3C VC Data Model 2.0 is a Recommendation dated 15 May 2025.
OB2 already described structured achievement data and verification options; it was not merely a proprietary image format. OB3 aligns achievement credentials with the VC model and related proof and exchange requirements. Do not interpret this change as compulsory blockchain, a DID for every issuer or automatic selective disclosure. These depend on the supported implementation and securing mechanism.
| Procurement question | What certification helps establish | What still needs testing |
|---|---|---|
| Is the issuing role listed? | A public, role-specific conformance record | Product/version and contracted functionality |
| Can recipients export a credential? | A standards context for achievement data | Actual export format and receiving wallet support |
| Can proof be checked elsewhere? | Structured credential and supported proof requirements | Verifier support, issuer keys and resource availability |
| Can status changes be checked? | A specification context for status handling | Current endpoint, propagation, caches and unavailable-resource policy |
| Does the award prove competence? | No independent assessment conclusion | Issuer authority, criteria and assessment evidence |
Portability retains operational dependencies
A downloadable credential can reduce dependence on a single display page, but verification may still require issuer-key resolution, status information or accessible evidence. A missing service should be reported as an unresolved check, not silently treated as valid. Wallets must support the particular format and proof type; “W3C compatible” is not enough to promise universal compatibility.
Before rollout, inspect an authorized test award in the intended receiver, test an altered record and a status exception, and request a written continuity plan for contract termination. Do not promise instantaneous revocation across every cache or independent real-world recipient identity merely because a subject identifier is signed.
Compare vendors using current evidence
CertifyMe’s listing does not make it the only standards-based platform. For example, Accredible’s January 2026 announcement documents OB3 and W3C VC export and ingestion. Look up each vendor’s precise certified role in the registry, and ask for a current sample. An unconfirmed feature is not an absent feature.
For definitions, use the institutional OB3 guide; this article focuses on CertifyMe’s public certification evidence. For connected records, use the CLR governance guide. Request a standards-focused demonstration covering your institution’s issuance and receiver requirements.
Frequently Asked Questions
What is CertifyMe certified for in Open Badges 3.0?
The public 1EdTech listing checked on 4 October 2026 shows an active Open Badges 3.0 Issuer certification, dated 11 May 2026, registration IMSO4ce2026W1, with API Service Consumer (Write).
Does 1EdTech certification constitute a security audit?
No. It concerns specified interoperability roles. The CertifyMe registry entry states that privacy and security vetting has not yet been completed.
Are DIDs, blockchain and selective disclosure compulsory for every OB3 credential?
No. Inspect the applicable specification and implementation. Identifier choices, securing mechanisms and disclosure capabilities must be evaluated separately.
Can every wallet verify an exported badge after an issuer goes offline?
No universal guarantee applies. Receiver support, issuer keys, status resources and evidence availability may remain dependencies.
