CertifyMe / Infrastructure

Digital Credential Infrastructure

The Infrastructure Behind Trusted Digital Credentials

CertifyMe provides the infrastructure to create, issue, manage, verify and share digital credentials across the systems organisations already use.

A governed credential layer for approved achievements—not a replacement for the systems that record them.

01 / Source systems
SISLMSHRISTrainingAssessmentMembershipAPIs
CertifyMeDigital Credential Infrastructure 01—06
CreateIssueVerifyManageShare
SkillsLearner / achievement recordsDownstream intelligence
Approved achievements move through a governed credential lifecycle; extensions are optional.

01 / The infrastructure

What Is Digital Credential Infrastructure?

Digital credential infrastructure turns an organisation-approved achievement into a credential that can be issued, maintained, checked and shared. It connects the source of the achievement to the credential lifecycle without asking organisations to replace the systems they already rely on.

That matters because a document alone is difficult to update, verify consistently or interpret across systems. Structured credentials carry defined claims and issuer provenance; governance keeps those claims tied to the organisation’s award policies.

What the infrastructure handles

Credential creation and issuance workflows, hosted credential access, standards-based representation, verification pathways, status management, and optional links from achievements to reviewed skills or learner records.

02 / The credential lifecycle

The Credential Lifecycle

Each step has a distinct role. The issuing organisation remains accountable for what the achievement means.

  1. 01

    Create

    Define the achievement, issuer, recipient claims and relevant criteria.

  2. 02

    Issue

    Release credentials through manual, bulk or scoped system workflows.

  3. 03

    Verify

    Check issuer provenance, credential integrity and status using the applicable method.

  4. 04

    Manage

    Maintain credential records and lifecycle state, including expiry or revocation where applicable.

  5. 05

    Share

    Give recipients a digital credential representation they can access and share.

Issuance options and workflow scope

Credential workflows may support individual awards, bulk issuance and API-based issuance. The appropriate route depends on the source system, approved fields, permissions, award rules and agreed integration scope; a named system is not a promise of a prebuilt connector.

03 / A clear foundation. Optional extensions.

Six-Layer Architecture

The first three layers establish access, interoperability and trust. Skills, learner records and workforce context extend that foundation when useful.

01

Credential Access & Sharing

Credential pages, unique URLs and QR-based access help recipients find and share an issued achievement.

Explore more
Access, issuance and administration details

Supported capabilities include reusable credential templates, organisation branding, manual and bulk issuance, API-based issuance, credential IDs, QR access and hosted credential pages. A QR code is a route to a record, not a cryptographic security mechanism.

02

Standards & Interoperability

Represent achievements in structured formats designed for exchange beyond a single visual document.

Explore more
03

Verification & Trust

Make issuer provenance, integrity and current status checkable through the relevant verification pathway.

Explore more
04

Skill Taxonomy Mapping

Connect reviewed learning outcomes to skills using a shared vocabulary, with organisational judgement retained.

Explore solution
05

Comprehensive Learner Record

Bring achievements together across a learner journey; this complements rather than replaces an authoritative transcript.

Explore solution
06

Workforce Intelligence & Opportunity

Optionally relate structured skills and achievement evidence to separately sourced labour-market context.

Explore solution

04 / Connect to existing systems

How CertifyMe Connects to Existing Systems

CertifyMe sits alongside source systems. Organisations identify authoritative records, permitted fields and award events; the agreed workflow passes only what is needed to create and manage credentials.

How a source connection is scoped

Discovery establishes the source of truth, data contract, access permissions, validation rules, exceptions and exchange method. Connections may use APIs, files or agreed workflows depending on the system and project scope.

Your systems
SISLMSHRISTrainingAssessmentMembershipAPIs
Approved records
selected fields + award event
Agreed connection
API / file / workflow
CertifyMe
Credential lifecycle
Digital credentialsVerificationSharing

Connection methods and availability are confirmed for each implementation. Examples are source-system categories, not a list of prebuilt native connectors.

05 / Standards & interoperability

Standards & Interoperability

Standards describe the credential’s data and claims—not merely how a certificate looks. They support interoperability, while verification still depends on the relevant trust and status resources.

Achievement specification

Open Badges 3.0

An achievement-focused specification for structured claims about an issuer, recipient and achievement, with criteria and supporting evidence where provided.

Certification and implementation

CertifyMe supports Open Badges 3.0 as a certified issuer. Certification is scoped to the issuer capability; it is not a claim that every downstream verifier, wallet or service is certified.

View CertifyMe’s 1EdTech certification listing ↗
Credential data model

W3C Verifiable Credentials

A W3C model for machine-readable claims and cryptographic proof. Open Badges 3.0 is an achievement specification that can use this model.

What interoperability does—and does not—mean

W3C is a standards model, not a vendor certification. Portability and ongoing checks depend on the credential format and on accessible issuer-key and status resources used by the verifier.

06 / Verification & trust

Verification & Trust

Credential integrity or issuer provenance does not independently establish that the person presenting a credential is its recipient.

01

Who issued it?

Issuer provenance is checked against the issuer information and applicable trust material.

02

Has it changed?

A signature or proof can support integrity checking of the credential data or signed document.

03

Who is presenting it?

Recipient identity is a separate question requiring an appropriate identity-association or authentication method.

Verification methods and boundaries

Credential ID or QR: directs a verifier to a credential record; lookup alone is not cryptographic integrity proof.

Identity reference or OTP: may associate a credential with an approved recipient reference or show control of a registered contact, depending on configuration.

Signed PDF or structured credential: can help check document integrity or issuer proof. A successful check does not by itself confirm the presenter’s real-world identity.

Continuity: ongoing verification can rely on accessible issuer keys and applicable status or revocation resources.

07 / The issuer owns the meaning

Credential Governance

Governance defines which system is authoritative, which achievements qualify, what data may be used, who approves issuance and who stewards the credential after award.

CertifyMe provides the credential infrastructure around those decisions. It does not replace the organisation’s award authority, policies or responsibility for its claims.

Governance questions to settle
  • Which source is authoritative for achievement and recipient details?
  • Which criteria, evidence and fields belong in the credential?
  • Who approves issuance and handles corrections or revocation?
  • Which key and status resources must remain available for verification?

08 / Beyond the credential

Extend the achievement only where it adds value.

Skills, records and workforce context are downstream options—not prerequisites for issuing or verifying a digital credential.

09 / Implementation

Scope the right route before connecting systems.

Implementation starts with your goals and governance, then defines a practical architecture around existing source systems and agreed data boundaries.

  1. 01

    Discover

    Identify the achievement, owners, source systems and intended recipients.

  2. 02

    Design

    Agree claims, workflow, data scope, responsibilities and verification needs.

  3. 03

    Configure & connect

    Configure credential workflows and scope any required integration or custom work.

  4. 04

    Validate & steward

    Test agreed flows, assign lifecycle responsibilities and plan rollout.

What determines integration scope?

Authoritative source records, permitted data, system access, API or file availability, validation and exception handling, security requirements, award approval rules and acceptance criteria. No connector is assumed before its availability and scope are confirmed.

CertifyMe / Digital Credential Infrastructure

Build Your Digital Credential Infrastructure

Bring your achievement sources, governance requirements and integration context. Start with the credential lifecycle; extend it as your needs call for.

Build Your Digital Credential Infrastructure