SCROLL
UK→US  ·  IN→US  ·  KE→US  ·  Portable credential protocol Groth16 + Ed25519 Verifier API UK→US  ·  IN→US  ·  KE→US  ·  Portable credential protocol Groth16 + Ed25519 Verifier API
passid-issuer · credential issuance
Running pilots now

Bind verified claims into portable financial credentials.

The issuer layer packages approved claim objects into a portable PASSID credential with signature, expiry, optional zero-knowledge proof bindings, and revocation references.

Credential issuance
Portable by design. Revocable by policy. Verifiable everywhere.
The issuer does one job: convert verified claim objects into a signed credential artifact that a holder can later present to any compatible institution. Institutions verify the credential; they do not trust a screenshot or PDF.
🔏

Ed25519 signatures

Credential envelopes are signed with issuer keys so verifiers can check authenticity and schema integrity.

Expiry + freshness windows

Credentials carry bounded validity periods and freshness metadata so institutions never rely on stale financial states.

Revocation support

Revocation references let institutions invalidate credentials when source conditions, sanctions state, or policy rules change.

{
  "credential_id": "pid_7f3c9x2mab4k",
  "issuer": "passid-issuer",
  "claims": {
    "income_stability": "stable",
    "cash_buffer": "high",
    "sanctions_clear": true
  },
  "signature": "ed25519",
  "proof_binding": "groth16_optional",
  "expires_at": "2026-03-11T09:14:00Z",
  "revocable": true
}
Issuers create the credential. Holders control presentation. Verifiers later validate proof, signature, freshness, and revocation before making institutional decisions.
architecture diagram
How passid-issuer creates the portable credential.
PASSID Issuer takes verified claim bundles, signs them, binds policy metadata, and creates a credential a holder can later present to any compatible verifier.
input
Verified claims
Structured claims from passid-core or another trusted issuer source.
issue
passid-issuer
Signs, timestamps, and binds expiry, freshness, and revocation.
holder
Wallet / code
The holder carries a portable credential or presentation code.
example object

Issued PASSID credential

{
  "credential_id": "pid_7f3c9x2mab4k",
  "issuer": "passid-issuer",
  "holder_binding": "wallet_presentation",
  "claims": {
    "income_stability": "stable",
    "cash_buffer": "high",
    "sanctions_clear": true
  },
  "signature": "ed25519",
  "proof_binding": "groth16_optional",
  "expires_at": "2026-03-11T09:14:00Z",
  "revocable": true
}
what this is / is not

The issuer creates the credential — not the decision.

What this is

  • Credential issuance and signature binding
  • Expiry, freshness, and revocation controls
  • Portable presentation format for holders
  • Foundation for verifier interoperability

What this is not

  • Not an institution’s decision workflow
  • Not an approval service
  • Not a raw-data wallet dump
  • Not a proprietary score marketplace