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-core · claim engine
Running pilots now

Translate fragmented banking signals into portable credential claims.

PASSID Core is the signal translation layer. It ingests corridor-aware open banking inputs and converts them into normalized, verifiable financial behavior claims with provenance and freshness. It does not issue lending decisions.

What passid-core does
Transforms signals into verifiable credential claims.
PASSID Core turns institution-specific raw inputs into corridor-normalized claim outputs that issuers can bind into credentials. Institutions later verify those claims through PASSID Verifier and make their own decisions.

Cross-corridor normalization

Normalizes cashflow patterns, income cadence, remittance behavior, and liquidity resilience across supported origin and destination systems.

Claim generation

Outputs structured credential claims such as income stability, cash buffer class, obligations reliability, sanctions status, and freshness metadata.

Provenance + freshness

Every claim is generated with source lineage, model/schema version, and a bounded freshness window suitable for verifier policies.

PASSID is not a lend score. PASSID Core generates portable claims that can be bound into credentials. It never replaces the institution’s own decision engine.
{
  "service": "passid-core",
  "schema_version": "1.0.0",
  "claims_generated": [
    "income_stability",
    "cash_buffer",
    "income_recency",
    "remittance_pattern",
    "sanctions_clear"
  ],
  "provenance": {
    "corridor": "NG→UK",
    "sources": ["open_banking", "wallet", "sanctions_lists"],
    "freshness_hours": 48
  }
}
Input layer

Open banking, account aggregators, mobile money rails, sanctions lists, and corridor-specific normalization rules.

Output layer

Portable claim objects ready for issuer signing, presentation requests, and downstream verification.

architecture diagram
How passid-core fits into the protocol.
PASSID Core translates hidden, corridor-aware financial behavior into structured claims that an issuer can sign into a portable credential. It does not own the lending decision.
input
Signal sources
Open banking, wallets, sanctions lists, corridor context.
translate
passid-core
Normalizes behavior into claim objects with provenance and freshness.
next step
Issuer layer
An issuer binds those claims into a signed, portable credential.
example object

Claim object produced by passid-core

{
  "service": "passid-core",
  "claim_bundle_id": "cb_01hpassidcore",
  "claims": {
    "income_stability": "stable",
    "cash_buffer_class": "high",
    "remittance_pattern": "consistent",
    "cross_border_continuity": "verified"
  },
  "provenance": {
    "corridor": "NG→UK",
    "sources": ["open_banking", "wallet", "sanctions_lists"],
    "freshness_hours": 48
  },
  "decision_owner": "institution"
}
what this is / is not

PASSID Core stays in the credential lane.

What this is

  • Claim generation for portable credentials
  • Corridor-aware signal translation
  • Provenance + freshness metadata
  • Input to an issuer and verifier protocol

What this is not

  • Not a lend score sold to lenders
  • Not a bureau substitute
  • Not a lending decision engine
  • Not a raw-data export product