SCROLL
UK→US  ·  IN→US  ·  KE→US  ·  Portable credential protocol Signed Credentials Verifier API UK→US  ·  IN→US  ·  KE→US  ·  Portable credential protocol Signed Credentials Verifier API
About PASSID
Production access available

We believe financial history should cross borders.

PASSID was founded to solve a simple injustice: 280 million migrants work, pay rent, and send money home — but are invisible to credit. We're building the infrastructure to change that.

1.4 billion people are still invisible to financial trust.

They have income. They pay rent. They send money reliably across borders. But they have no bureau history in the destination country, so local institutions lack a fast way to verify their track record. PASSID helps translate that financial behavior into consented, portable credential claims.

280M
migrants worldwide, most without destination credit history
$800B
in annual remittance flows demonstrating payment reliability
10
corridors live, covering the world's highest-volume migrant finance routes
The Problem

Financial identity doesn't travel.

When people cross a border, their credit history often stays behind. Disciplined financial behavior becomes hard for local institutions to verify quickly and fairly.


PASSID changes the primitive. Instead of relying only on a bureau file, institutions can verify signed financial behavior claims with user consent.


No credit bureau dependency required
Designed for cross-border credential verification
No raw transaction feed in the verifier response
Fairness and governance review included in pilot validation
📋
History resets at the border
Three years of responsible banking in Lagos means nothing in London. Moving resets the clock to zero.
💸
Non-traditional income ignored
Gig economy, remittance, and seasonal work are often penalized when models cannot categorize them cleanly.
🔒
Privacy vs access trade-off
No one should hand over raw financial statements to prove creditworthiness. There is a better way.
Manual verification is slow
Repeated document checks add days and cost. Portable credential verification removes that friction.
The market problem

Verified credentials should travel with the person, not reset at every border.

1.4 billion mobile money users and hundreds of millions of cross-border workers carry real financial track records. Legacy credit systems cannot read them. The result: invisible borrowers for institutions — and locked-out users who have already proved themselves.

Portable trust pipeline issuer · holder · verifier
01
Signals become claimsIncome consistency, balance resilience, sanctions status, and freshness are translated into portable credential claims.
02
Claims become credentialsPASSID signs and packages those claims into a revocable, presentation-ready credential.
03
Institutions verify, then decideOne verification call returns signature status, audit metadata, and structured claim summaries - institutions keep their own policies and liability.
Step 01 · Arrival

A strong borrower lands in a new market and becomes invisible.

International students, migrant professionals, and globally mobile workers often arrive with savings history, repayment discipline, and active bank relationships — but traditional scoring systems fail to recognize any of it.

0local bureau history on day one
3+financial systems already used abroad
Weekslost to manual onboarding and documentation
Step 02 · Translation

PASSID converts fragmented signals into portable verified trust signals.

Instead of relying only on a domestic bureau file, institutions receive normalized behavior signals: income consistency, balance resilience, remittance patterns, savings cadence, and verified institutional attestations.

5core risk pillars structured for decisions
1portable credential and verifier response
APIverification for onboarding and credit access workflows
Step 03 · Verification

Banks, fintechs, and platforms verify financial trust without requesting raw data.

PASSID gives institutions a credential verification layer: signed claims, freshness windows, revocation state, and audit metadata — all without receiving financial statements or raw transaction feeds. Institutions apply their own onboarding and compliance policies.

Newcustomer segments become addressable
Lowermanual review overhead and KYC friction
Portableidentity persists across borders and rails

How we build.

Infrastructure, not product
We are a protocol. We don't lend, we don't underwrite, we don't decide. We verify. The liability stays with the institution. Our job is to make verification fast, private, and trustworthy.
Privacy by default
Every architectural decision starts with: "can we minimize what the verifier receives?" Credential presentations are designed around scoped claims instead of raw financial records.
The user owns their credential
PASSID credentials belong to the user. They consent to each presentation. They can revoke at any time. No institution receives anything without explicit approval.
Fairness as a constraint
Disparate impact and approval-rate patterns can be monitored per corridor during live-access reviews, with institution policies and governance kept in the loop.
What PASSID is / is not

Credential infrastructure. Not a lender or bureau.

PASSID is
Credential infrastructure
Token-based verification
Signed claims
User-permissioned
Institution-controlled decisioning
PASSID is not
A credit bureau
A lender
A bank
A public scoring product or bureau file
A replacement for institution-controlled decisioning
A raw transaction feed
Why PASSID

Not a bureau bridge. A behavior protocol.

Existing solutions often port a bureau file, connect raw data, or verify a single income source. PASSID packages user-permissioned financial history into reusable, cryptographically signed credentials. Institutions verify scoped claims, then apply their own policy.

Bureau portability
Moving a foreign credit file

A corridor-dependent model built around an existing bureau record.

  • Requires an existing credit bureau file in the origin country
  • Gig, informal, and non-traditional income not captured
  • Institution receives a translated bureau report or raw-data workflow
  • Requires bilateral bureau partnership per corridor
  • Limited to corridors where partner bureaus exist
PASSID protocol
Verifying real financial behavior

A reusable credential model built around permissioned financial signals.

  • Works from day one using user-permissioned financial signals, not only bureau history
  • Cashflow, savings, gig income, and remittance all become verified signals
  • Institution receives structured credential claims without raw financial data exposure
  • Single API integration — no bureau partnerships required
  • Extends across corridors as supported financial signal sources become available
👤
Works from zero history
A migrant arriving on day one with no local credit file can present verified financial signals from supported origin-country sources as a signed credential.
💸
Behavior, not history
PASSID reads cashflow, savings discipline, income regularity, and spending patterns — not a repayment record that only exists if someone was previously banked in the right country.
🔒
Claims-only when you need it
Credentials and Verify return claim summaries and freshness metadata without financial statements or transaction lists. Data Access is a separate, explicitly scoped integration.
One verifier API for production rollouts
No bilateral bureau agreements. No corridor-specific bureau integrations. One API call supports credential verification for each corridor configured during pilot onboarding.
Pilot validation

Evidence institutions review before rollout.

PASSID is built for production rollouts where institutions can test credential verification, review claim accuracy, and validate integration before production use.

📊
Claim accuracy validationHow accurately credential claims reflect underlying financial signals, tested against synthetic and real pilot data.
Completion rate by segmentVerification completion across user segments — students, migrants, gig workers, thin-file applicants.
📋
Manual review reductionReduction in manual document review where credential claims replace statement checks during pilot testing.
🔒
Data boundary reviewConfirmation that every product returns only its approved scopes; claims-only integrations exclude raw transaction data.

Join us.

We're a small, technical team solving hard infrastructure problems with real social impact. If that sounds like your thing, we'd like to hear from you.

Senior Backend Engineer
London / Remote  ·  Full-time
Credential signing systems, credential protocols, supported financial source APIs. Rust or Go preferred.
Apply ›
ML / Risk Engineer
London / Remote  ·  Full-time
Signal model development. Survival analysis. Fair lending measurement. Python + SQL.
Apply ›
Partnerships Lead
London  ·  Full-time
Drive lender and fintech partnerships. Financial services background. FCA-regulated environment.
Apply ›
PASSID
Thank you — we'll be in touch.