GC Supplier Trust

Tamper-proof, click-to-verify Government of Canada supplier status.

GC Supplier Trust lets suppliers embed a GC supplier badge that anyone can verify in one click. Procurement signs one snapshot of supplier-status data, and suppliers generate their own credentials from it, so Procurement never has to manually issue credentials.

The gap

Proving GC supplier status today is manual, and easy to fake.

01

Manual checks

Buyers search contract history, ask Procurement directly, or wait for Procurement to issue a manual verification.

02

Copyable claims

A “GC supplier” logo on a website is just an image. Anyone can copy it onto a look-alike site.

03

No machine signal

Procurement platforms and AI agents have nothing machine-readable to check.

04

Issuance workload

A conventional credential programme would have PSPC enrol and issue supplier by supplier.

How it works

Four steps, and no per-supplier issuance.

Self-service: zero PSPC touchpoints per credential

Copy-proof: fails verification on any other domain

Quantum-ready: Ed25519 + ML-DSA-65 (NIST FIPS 204)

  1. 01

    Procurement signs a snapshot

    On a set schedule, supplier-status data, minus suppliers on the ineligibility list, becomes a Merkle tree. Procurement automatically signs its root with classical and post-quantum signatures.

  2. 02

    The supplier self-generates

    In a self-service dashboard, the supplier finds its own record and gets a credential holding its inclusion proof without PSPC involvement.

  3. 03

    The badge goes live

    The supplier adds the script tag to their website. The credential is verified against and bound to that domain.

  4. 04

    Anyone verifies

    Click the badge, scan its QR code, call the API or ask an AI agent. The checks run in the verifier’s browser, with no issuer server in the path.

Video demo

Features

From a supplier’s record to a verified badge.

Find your record

A supplier opens the self-service dashboard and searches by company name or business number. The dashboard reads the snapshot Procurement signed, so a supplier can only find a record that is already there. No account needed.

  • The website field is locked to the official domain in the source record, not typed in by the user.
  • That makes open self-service safe: a credential generated for another company only works on that company’s own website.
  • Suppliers on the ineligibility list are left out of the snapshot, so they can’t generate a credential.
Self-service dashboard: the supplier searches the signed snapshot and its website field is locked to the domain in the source record

Generate and embed

The dashboard builds the supplier’s inclusion proof from the snapshot, packages it as a signed credential, and records it in a public transparency log. The supplier gets one line of HTML for its website and a QR code for printed material.

  • No PSPC action is needed for any individual supplier.
  • Credentials can be given a dynamic expiry time, so a supplier that loses good standing can’t renew.
  • Every credential issued is visible in the transparency log.
Dashboard showing the one-line badge embed code and a QR code for scan-to-verify

The badge verifies itself

When a visitor opens the supplier’s site, the badge checks its credential right in the visitor’s browser and shows “GC Verified Supplier” only if every check passes. No server call to an issuer is needed to decide.

  • Works on any website with a single script tag, in English or French.
  • Visitors can also scan the QR code or call the verification API.
A demo supplier website with a green “GC Verified Supplier” badge in its trust bar

One-click evidence

Clicking the badge opens the evidence trail: eight checks that a buyer or procurement officer can read for themselves.

  • The credential is well formed and has not expired.
  • The supplier is included in the snapshot, and the snapshot is signed by Procurement’s pinned public key.
  • The claims match the signed record exactly, and the credential’s own hybrid Ed25519 + ML-DSA-65 signature is valid.
  • The badge is running on the domain in the record, and the credential appears in the transparency log.
Verifier page reading “northern-birch.demo is a verified GC supplier”, with all eight evidence-trail checks passing

Copies fail

Because each credential is bound to the supplier’s official domain, copying the badge onto a look-alike website turns it red. The verifier names the domain the credential belongs to, so the mismatch is obvious.

  • Automated attack tests also reject domain substitution at issuance and credentials from a rogue snapshot.
  • Edited claims, such as an earlier “supplier since” date, and extended expiry dates fail too.

On the supplier’s own domain: verified

Trust bar on the real domain showing the green GC Verified Supplier badge

The same badge copied onto a look-alike site: rejected

The same trust bar on a look-alike domain showing a red Verification Failed badge

AI agents

The same checks are available as a Model Context Protocol tool, so an AI agent gets a structured verdict and the full evidence trail instead of scraping a web page.

  • An agent only needs a supplier’s website address to ask, and it gets back a clear yes or no it can act on, with no account or special setup.
{
  "verdict": "VERIFIED",
  "domain": "northern-birch.demo",
  "gcSupplierSince": "2024-03-15",
  "latencyMs": 130,
  "evidenceTrail": [ 8 checks, all passed ]
}

What’s new

Compared with conventional credentials.

DimensionTraditional solutionsGC Supplier Trust
IssuanceAn issuer enrols and signs each subjectProcurement signs one snapshot and suppliers serve themselves, so each credential costs effectively nothing
VerificationDepends on issuer, status-list or registry serversRuns in the browser or AI agent, with no issuer server in the path
Copy protectionLogos and portable credentials can be re-shown elsewhereBound to the supplier’s domain, so a copied badge fails
CryptographyClassical signaturesHybrid Ed25519 and NIST FIPS 204 ML-DSA-65 signatures, and both must verify
AI agentsNo procurement-specific interfaceMCP tool returns a structured, machine-readable verdict

Issuance

Traditional solutions

An issuer enrols and signs each subject

GC Supplier Trust

Procurement signs one snapshot and suppliers serve themselves, so each credential costs effectively nothing

Verification

Traditional solutions

Depends on issuer, status-list or registry servers

GC Supplier Trust

Runs in the browser or AI agent, with no issuer server in the path

Copy protection

Traditional solutions

Logos and portable credentials can be re-shown elsewhere

GC Supplier Trust

Bound to the supplier’s domain, so a copied badge fails

Cryptography

Traditional solutions

Classical signatures

GC Supplier Trust

Hybrid Ed25519 and NIST FIPS 204 ML-DSA-65 signatures, and both must verify

AI agents

Traditional solutions

No procurement-specific interface

GC Supplier Trust

MCP tool returns a structured, machine-readable verdict

Interested in testing GC Supplier Trust?

Federal departments and agencies can test it through Innovative Solutions Canada. For a live demo or any questions, please contact 1280 Labs at info@1280labs.ca.

Conditionally qualified under the Innovative Solutions Canada Testing Stream (EN578-26ISC1, TS13) for supplier verification and decentralized credentialing.

1280 Labs globe logo
1280 labs
© 2026 1280 Labs. All rights reserved.
Third party logos and images appear courtesy of their respective trademarks.
Linkedin Icon