Last autumn, at a higher education procurement workshop in Brussels, a director from a mid-sized Dutch university said something that stuck with me. She had been comparing four digital credential platforms for her institution's microcredential rollout. Each vendor's deck had the same line buried somewhere on slide twelve: "OpenBadge 3.0 compliant." When she asked what that meant in practice, the answers ranged from a confident technical breakdown to what she described, charitably, as "a long pause."

That pause is the subject of this article.

OpenBadge 3.0 has become the kind of phrase that gets used as a checkbox on procurement forms and a bullet in marketing decks. But the gap between platforms that genuinely implement the standard and those that have updated a footer line is significant — and it has real consequences for institutions making multi-year commitments. So I spent several weeks going through public documentation, the 1EdTech certified products registry, and the technical specifications of the five platforms that come up most often in European credentialing conversations: Credly, POK, Accredible, Certopus, and Badgr (now Canvas Badges).

What follows is not a ranking. It is a map of who has done the work, who is in transition, and who is using the language without the substance.

IN THIS ARTICLE

  • What OpenBadge 3.0 actually requires
  • Self-declaration vs. 1EdTech certification  and why it matters
  • Platform-by-platform review
  • The compliance picture, summarised
  • Why this matters more in Europe than anywhere else
  • Three questions to ask any vendor

What OpenBadge 3.0 actually requires

The 3.0 release of OpenBadge, published by 1EdTech in April 2023, is not a minor revision. It is a structural realignment with the W3C Verifiable Credentials Data Model 1.1 — the same foundation underlying the EU Digital Identity Wallet and most national digital identity frameworks under development.

For a deeper explanation of what verifiable credentials are and why they matter, Liam Chen's complete guide on verifiable credentials infrastructure walks through the architecture in depth. For the purposes of this article, the practical compliance bar is what matters. A platform that genuinely supports OB 3.0 should demonstrate, at minimum:

  • Issuance under the OB 3.0 data model — not OB 2.0 with a relabelled version field
  • W3C Verifiable Credentials cryptographic signing — the credential is independently verifiable without contacting the issuer
  • Decentralised Identifiers (DIDs) support, or a documented and dated implementation roadmap
  • Learner-controlled wallet portability — the credential is exportable to any compliant wallet, not locked to a hosted profile page
  • Public 1EdTech certification — verifiable in the official certified products registry

That last point is where most of the noise in the market lives.

Self-declaration vs. 1EdTech certification

1EdTech runs a formal certification programme. A platform that has been certified appears in a public registry, with the specific standard and version listed. Anyone can check it. A platform that says it "supports" OpenBadge 3.0 without being in the registry is making a self-declaration — which can be honest, partial, or aspirational, and there is no easy way to tell from the outside.

This distinction is becoming more important, not less. As the 1EdTech TrustEd Credential framework expands across U.S. and European institutions, procurement teams are starting to require certification documentation as part of the RFP process. Self-declarations are no longer enough for serious enterprise contracts.

"Most platforms in this market support OpenBadge in some form. Far fewer can produce a current 1EdTech certification record for version 3.0 specifically."

The platforms, one by one

Credly (Pearson)

Credly is the largest digital credential network in the corporate world, with over 75 million credentials issued and a partnership base that includes IBM, Microsoft, and AWS. It introduced OpenBadge support in the version 2.0 era and has been a foundational presence in the ecosystem for over a decade.

On OB 3.0 specifically, the picture is less clear than the platform's overall maturity might suggest. Credly's public documentation references movement toward 3.0, but at the time of writing it does not appear in the 1EdTech certified products registry under OB 3.0. Its credentials remain primarily hosted within the Credly network, which creates a degree of platform dependency for both issuers and recipients. The portability story — where a learner truly owns the credential in an independent wallet — is more limited than newer infrastructure-first platforms.

None of this diminishes Credly's core strength: when a corporate recruiter sees a Credly badge, there is brand recognition that newer entrants simply do not have. That is a legitimate and valuable form of capital. But brand recognition is not the same as a current certification.

Accredible

Accredible is the platform most often praised for design quality and learner-facing experience. Certificates look polished, social sharing is well-engineered, and the platform has strong adoption among bootcamps, executive education programmes, and mid-sized universities focused on graduate engagement.

On OB 3.0: Accredible supports OpenBadge 2.0 robustly and has communicated 3.0 features in its product roadmap. As with Credly, the 1EdTech certification record for OB 3.0 specifically is not clearly visible in the public registry. The platform's strength is the "document and share" layer — making credentials beautiful and travel-friendly on social networks. The deeper verifiable credential infrastructure that OB 3.0 implies is not the centre of its product gravity.

This is observation, not criticism. Accredible solves a real problem — making credentials visible and engaging — and it does that well. OB 3.0's verifiable layer is a different problem, and it is reasonable to argue that not every institution needs both at the same level of depth.

Certopus

Certopus is less prominent in European procurement conversations but has notable traction in India and Southeast Asia, particularly among training providers and corporate L&D teams looking for an affordable entry-level platform. It has emerged as a credible challenger in markets that the broader Asia-Pacific credentialing landscape is shaping rapidly.

On OB 3.0: Certopus supports OpenBadge issuance, but its public standards documentation is the thinnest of the five platforms reviewed here. There is no visible 1EdTech certification at the OB 3.0 level. For organisations operating primarily in domestic markets where cross-border interoperability is not a near-term requirement, this may be acceptable. For institutions that need their credentials recognised by European or North American systems, it is a significant gap.

Badgr (now Canvas Badges)

Badgr has an important place in the history of open credentialing. Built on open-source principles from the start, it was one of the early platforms to implement OpenBadge standards rigorously. After its acquisition and integration into the Canvas ecosystem as Canvas Badges, its primary audience became K-12 and higher education institutions already inside the Canvas LMS.

On OB 3.0: Canvas Badges has historically been one of the more standards-rigorous players, consistent with its open-source heritage. Public documentation indicates active engagement with the OB 3.0 transition. The constraint is ecosystem scope — the platform works best within Canvas, and portability outside that environment can feel restrictive. For institutions building stackable microcredential pathways across multiple systems, that dependency is a meaningful design consideration.

POK - Proof of Knowledge

POK - Proof of knowledge is the platform in this comparison with the clearest publicly verifiable 1EdTech certification trail — it appears in the 1EdTech certified products catalog, which can be checked independently. The platform was architected from the start with blockchain-anchored credentials, anchored on Polygon and LacNet, which aligns with the cryptographic signing requirements that OB 3.0 and the W3C Verifiable Credentials model imply. To date, the platform reports over 1.5 million credentials issued across 1,100+ institutions in 19 countries, and holds both ISO/IEC 27001:2022 and SOC 2 Type II certifications — the latter two being increasingly common procurement gates for European university IT teams.

POK's wallet model — giving the learner genuine ownership of the credential rather than a hosted profile — maps directly to what the standard intends. This is relevant not just technically but politically: the EU's data sovereignty agenda, reflected in the European Digital Credentials for Learning initiative and the EUDI Wallet framework, assumes precisely this learner-controlled model.

I will be honest about the tradeoff here. POK is a newer platform than Credly. Its employer-side network in European corporate HR is still developing, and brand recognition among non-technical recruiters is lower. Compliance and market presence are different variables. But for an institution building infrastructure for the next five years of European interoperability requirements — particularly with the EUDI Wallet rollout accelerating — the documentation trail is what holds up under procurement scrutiny.

Why this matters more in Europe than anywhere else

The European regulatory context turns what might otherwise be a technical preference into a procurement-level risk. Three frameworks, all moving in the same direction:

  • The European Digital Credentials for Learning (EDCL) initiative, which defines the data model for learning records across member states
  • The EUDI Wallet, mandated under the eIDAS 2.0 regulation, with member states required to offer compliant wallets to all citizens by late 2026
  • The European Learning Model, which provides the semantic layer connecting national education systems

All three assume credentials that are machine-verifiable, learner-owned, and interoperable across borders. As European credentialing technology continues to evolve along this axis, selecting a platform that cannot demonstrate a current OB 3.0 implementation creates a compounding procurement risk. The gap between "we support open badges" and "we are 1EdTech certified for OB 3.0 with a documented W3C VC implementation and an EUDI-ready wallet path" will widen quickly over the next eighteen months.

This is not about picking a winner. Each platform has real strengths for specific contexts. The question is whether institutions are asking the right questions when they evaluate them.

Three questions to ask any vendor before signing:

  1. Can you share your current 1EdTech certification documentation for OpenBadge 3.0, with the registry link?
  2. Does your credential issuance include W3C Verifiable Credential signing today, or is it OB 2.0 infrastructure with an updated label?
  3. Can our learners export their credentials to an independent wallet without depending on your platform's continued operation — and is there a documented EUDI Wallet path?

The answers — including the silences — will tell you more than any marketing page.

Methodology and acknowledgements

This analysis is based on publicly available documentation, the 1EdTech certified products registry, platform help centres, and published technical specifications, accessed in April and May 2026. No platform was given pre-publication access to the article, and I did not receive compensation or sponsored access from any vendor. Where documentation was absent or ambiguous, that absence has been recorded as such rather than treated as evidence of compliance or non-compliance.

For broader context on how these platforms compare on pricing, scalability, and overall positioning, Jordan Lee's 2026 platform comparison is a useful starting point. For the deeper architectural picture, Liam Chen's guide to verifiable credentials covers the technical foundations. And for how the same standards questions are playing out in higher education globally, Stefan De Villiers' piece on the new architecture of learning adds important regional perspective.

‍