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
Credential protocol
Running pilots now

The passport for financial trust.

PASSID turns open banking signals into portable, cryptographically-signed credentials. Users carry the proof. Institutions verify in one call. Decisions stay with you.

PASSID Credential
Active
statusACTIVE
verified_signals6 of 6
freshness48h
revocableYES
provenanceVERIFIED
stability_band (claim)B
POST /v1/verify
POSTapi.passid.io/v1/verify
{ "passid_code": "7F3C·9X2M·AB4K",
  "institution": "inst_partner" }
200 OK Fast
"valid"true"credential_status""active",
"stability_band""B""freshness_hours"48,
"proof""groth16_verified",
"sanctions""clear"
Zero-Knowledge Proof
Groth16 BN254 Ed25519 zk-SNARK Verified ✓
Swipe to reveal
Built for financial institutions and platforms
Banks Fintechs Payroll Platforms Gig Platforms Remittance Providers Compliance Teams Developers Plaid Partnership Banks Fintechs Payroll Platforms Gig Platforms Remittance Providers Compliance Teams Developers Plaid Partnership
PASSID SYSTEM

How PASSID Works

PASSID transforms fragmented financial history into portable, verifiable credentials that banks, fintech apps, wallets, and lenders can trust across borders.

PASSID Credential Infrastructure
source → credential → trust → verify
STEP 01
🏦
Financial Sources
Bank accounts, mobile money, payroll records, savings activity, insurance, and verified payment rails.
Input Layer
STEP 02
🔐
Credential Issuance
Raw records are normalized into signed, portable financial credentials instead of exposed documents.
Verifiable
STEP 03
🧠
PASSID Trust Layer
Credentialing, identity resolution, fraud checks, corridor logic, and zero-knowledge privacy controls run here.
Decision Engine
STEP 04
Verification API
Fintechs, lenders, employers, and platforms query PASSID to verify trust without ingesting raw data.
API Output
Banks → Credentials
Signals → PASSID Credential
PASSID → Verification
What PASSID is
Portable financial credentials.
A verification protocol.
User-controlled financial identity.
What PASSID is not
Not a lend score.
Not a credit bureau.
Not a lending decision engine.
The Problem

Financial identity doesn't travel.

When you cross a border, your credit history stays behind. Migrants are often the most financially disciplined people in the world — but they are treated as ghosts by the financial system.


PASSID changes the primitive. Instead of asking what the bureau says, we ask what verified financial behaviour says.


No credit bureau dependency
Works across global corridors
No raw financial data transmitted to lenders
Fair lending monitoring built in by default
📋
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, seasonal work — traditional models penalise what they cannot categorise.
🔒
Privacy vs access trade-off
No one should hand over raw bank 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.
Solutions

Solutions for people building trust across borders — and institutions that need a better way to verify it.

Choose a solution path to see exactly how PASSID works for that audience, why it matters, and where they enter the product.

Dedicated pages User and institution paths Clear next steps
How It Works

From signal to credential in seconds.

Five steps. One API call. Under 200 milliseconds.

1
Connect open banking
User links their bank via PSD2, account aggregator APIs, or mobile money. Designed to integrate with open banking, account aggregators, and mobile money providers.
🏢 Open banking · Account aggregators · Mobile money
2
Signal verification & claim generation
PASSID core derives verified claim inputs from open banking and wallet signals, applies policy-safe signal models, and packages only the claim outputs needed for credential issuance.
⚙️ passid-core
3
Zero-knowledge proof issued
Groth16 zk-SNARK over BN254 generates a cryptographic proof. Ed25519 signature binds it. No raw PII leaves our system.
🔒 passid-issuer · ZKP
4
Lender calls verify API
A single POST returns credential status, verified claim summaries, freshness, provenance, and proof status. No bureau query needed.
📡 POST /v1/verify
5
Institution routes into its decision workflow
The institution uses verified credential claims as policy inputs inside its own decision workflow. Their policies, their liability. Typical time-to-verification under 200ms.
📡 Verification complete
200 OK — /v1/verify
200 OKFast
{
"valid"true,
"passid""pid_7f3c9x2mab4k",
"credential_status""active",
"freshness_hours"48,
"claims": {
"income_stability""stable",
"cash_buffer""high",
"income_volatility""low",
"sanctions""clear",
"fraud_signal""none"
},
"stability_band""B",
"provenance""verified",
"proof""groth16_verified",
"algorithm""Ed25519",
"corridor""UK→US",
"expires_at""2026-03-11T09:14Z"
}
The Wallet Flow

The user is always in control.

PASSID is not a data API. It is a credential protocol. Institutions request. Users consent. Proofs are presented. No raw data moves — ever.

01
🏛️
Verification Request
Institution sends a structured request to PASSID specifying which credential claims it needs — corridor, signal types, freshness window. No access to underlying data.
Institution → PASSID
02
📱
User Consent
User receives the request in their PASSID Wallet. They review exactly which claims are being requested and approve or decline — with full selective disclosure control.
PASSID Wallet
03
🔒
Proof Presentation
Wallet returns a zero-knowledge Presentation containing only the approved claims — cryptographically bound, timestamped, and signed. No raw bank data. No PII.
ZKP Presentation
04
Institution Verifies
One API call. Institution calls POST /v1/verify and receives proof status, claim values, freshness, and provenance. Their decision engine takes it from there.
Institution decides
☝️
PASSID does not decide. It verifies.
The institution’s own models, policies, and decision workflow make every final decision. PASSID provides verified, signed, portable credential claims — nothing more. The liability and the decision remain entirely with the institution.
Products

Three services. One protocol.

PASSID is credential infrastructure, not a lender dashboard. Institutions integrate once and verify portable credentials across corridors.

⚙️
passid-core
Transforms financial signals into verifiable credential claims with provenance and freshness metadata.
Open product page ›
🔒
passid-issuer
Issues signed financial credentials with claims, freshness, provenance, expiry, and revocation.
Open issuer page ›
📡
passid-verifier
Verify credential validity, proof, freshness, and claim integrity in a single request.
Open verifier API ›
🧪
Verifier Console Sandbox
Internal QA tooling for integration teams. Sandbox console to test credential flows, inspect signal payloads, and validate proof responses before going live.
Open sandbox page ›
🛡️
Compliance Suite
OFAC, EU, and UN sanctions screening on every verification. PEP check, AML scoring, bias DI monitoring (≥0.80 enforced), and full audit log export.
Open security page ›
🌐
Global Corridors
10 active corridors across 4 continents. Each has dedicated signal context, bank integrations, and currency-normalised income analysis. New corridors quarterly.
Open corridors page ›
Active Corridors

The world's highest-volume remittance routes.

Each corridor has dedicated open banking integrations, currency-normalised income analysis, and corridor-specific risk calibration.

🇬🇧🇺🇸
UK → US
Bank partner · Monzo · HSBC
🇮🇳🇺🇸
IN → US
Bank partner · ICICI · SBI
🇰🇪🇺🇸
KE → US
Mobile money partner · Equity · KCB
🇳🇬🇬🇧
NG → UK
Bank partner · Access · Kuda
🇸🇳🇺🇸
SN → US
Orange Money · Wave
🇲🇽🇺🇸
MX → US
BBVA · Banamex · SPEI
🇵🇭🇺🇸
PH → US
GCash · Maya · BDO
🇧🇩🇬🇧
BD → UK
bKash · Dutch-Bangla
🇵🇰🇺🇸
PK → US
JazzCash · Easypaisa
🇬🇭🇺🇸
GH → US
MTN MoMo · GCB
0Credential protocol
1Issuer infrastructure ready
0Verifier API
0Raw financial data shared
Technology

Built like infrastructure.
Not like a dashboard.

PASSID uses Plaid for secure account connectivity and transforms verified financial signals into portable, verifiable credentials.

Every architectural decision serves institutional trust — not demo aesthetics.

01
Zero-Knowledge Proofs
Groth16 zk-SNARKs over BN254. Proves creditworthiness without revealing financial data. Ed25519 signature binds every credential to its issuer.
02
Freshness + Revocation
7-day credential expiry enforced by protocol. Instant revocation endpoint. Lenders always verify current financial state, never stale data.
03
AML + Sanctions Screening
Every verification runs OFAC, EU, and UN lists automatically. PEP identification included. All decisions logged to immutable audit trail.
04
Bias Monitoring
Disparate impact ratio tracked across gender, nationality, and corridor. DI ≥ 0.80 enforced. Model drift alerts at PSI > 0.10.
05
No Raw PII Transmitted
Lenders receive proven claims, not data. Bank statements, transaction history, and personal details never leave PASSID's secure compute environment.
🏢
Signal Sources
PSD2 · Account aggregators · Mobile money
INPUT
Encrypted data ingestion
⚙️
passid-core
5-pillar signal model · AML · Bias check
COMPUTE
Groth16 proof generation
🔒
passid-issuer
ZKP sign · Ed25519 bind · Revocation
ISSUE
Signed portable credential
📡
passid-verifier
REST API · claim verification · audit-ready
VERIFY
JSON credential response
🏛️
Lender System
Decision engine · No PII stored
DECIDE
Performance

Numbers that convince credit committees.

Model trained on 1.4 million migrant financial profiles. Validated against bureau outcomes across 6 corridors.

0
Default signal window
0
Key actors: issuer, holder, verifier, institution
0
Verifier API
0
Raw data disclosed to lenders
0
Core services: core, issuer, verifier
0
Key actors: issuer, holder, verifier, institution
0
Portable credential format
0
Verified claim domains in model
For Developers

Integrate in hours, not months.

PASSID is API-first. One endpoint, standard JSON, SDK in your preferred language. Your team can be verifying portable credentials the same afternoon.

1
Get your API key
Start in sandbox. Full test environment with mock credentials, simulated corridors, and edge cases built in.
2
Call the verify endpoint
POST the PASSID code from your applicant. Receive structured JSON with claim summaries, freshness, and proof status.
3
Plug into your decision engine
Map verified claims into your existing policies. No restructuring required. Works alongside any existing decision stack.
PythonNode.jsRubyJavaGoREST APIWebhooks
📚 API Docs 🧪 Sandbox 💬 Contact
quickstart.py
# pip install passid
import passid

client = passid.Client(
api_key="sk_live_..."
)

# Verify a PASSID credential
result = client.verify(
passid_code="7F3C·9X2M·AB4K",
institution_id="inst_partner"
)

# Route verified claims into your own model
if result.valid and result.proof == "groth16_verified":
route_to_decision_engine(result.signals)

# result.signals, result.stability_band,
# result.freshness_hours, result.expires_at
Compliance & Security

Built for regulated financial institutions.

Every design decision serves the same goal: making PASSID the most trusted infrastructure your compliance team has ever reviewed.

🛡️
AML & Sanctions
Automated screening on every verification. No manual checks required.
OFAC SDN list
EU Consolidated list
UN Security Council list
PEP identification
🔒
Privacy by Design
Zero-knowledge proofs ensure no raw PII ever reaches the lender.
No raw bank statements transmitted
No PII stored by lenders
GDPR-compatible architecture
Right to revoke credential
⚖️
Fair Lending
Disparate impact monitoring on every scoring run. Non-negotiable.
DI ratio ≥ 0.80 enforced
Gender, nationality, corridor tracking
Model drift alerts (PSI > 0.10)
Full fairness audit export
What people say

Built for teams building portable financial trust.

"Portable credentials give institutions a cleaner way to verify financial trust without receiving raw financial data."
JM
Risk & Compliance Team
Institution perspective
"Proofs, signatures, freshness, and revocation are what make credential infrastructure usable in regulated environments."
SC
Verification & Security Team
Technical reviewer perspective
"A verifier API should be simple: validate the credential, check proof and freshness, and return claims the institution can use in its own workflow."
MO
Developer Experience Team
Platform builder perspective
Pilot Program

Start verifying
in 5 days.

We are running a structured pilot. Your team gets sandbox access, full documentation, a dedicated integration engineer, and direct access to the founders. You verify PASSID credentials and route verified claims into your own models and policies.

Request pilot access
Or email hello@passid.io
The pilot flow
01
Applicant connects open banking accountDay 1
02
Signal extraction + ZKP credential issuedDay 1
03
Applicant shares 16-character PASSID codeDay 2
04
Lender calls POST /v1/verifyDay 2
05
Verified claims route into your decision engineDay 2
06
Results review, calibration, go liveDay 5
Live identity graph
A 3D financial identity graph for borderless trust
PASSID maps verified accounts, remittance rails, savings behavior, salary flows, and institution attestations into one portable trust layer. Instead of restarting from zero, users carry machine-readable proof across markets.
PASSID Identity Mesh
ZK attestations Multi-rail data Cross-border ready
Signal composition
Income stability
0.88
Cashflow discipline
0.81
Payment reliability
0.93
Fraud integrity
0.96
Compliance gate
0.90

From raw history to portable trust

Each node represents a verified behavior source. PASSID turns fragmented financial footprints into a single graph that lenders, banks, and platforms can reason over instantly — without exposing raw personal data.

Interactive zero-knowledge flow
Verify without revealing everything
This demo shows how PASSID can prove eligibility, payment reliability, and behavioral consistency while minimizing raw data exposure. Trigger the sequence to simulate a verifiable credential verification request.

Interactive ZK verification animation

Instead of sending statements, screenshots, and fragmented PDFs, the user submits a compact proof package. PASSID verifies origin, evaluates rules, and returns a yes-or-no decision with policy metadata attached.

01/inputAwaiting encrypted credential bundle
02/proofAttestation not generated
03/policyEligibility rules idle
04/outputNo verification response yet
Bank history
Income proof
Policy engine
ZK attestation
Score threshold
Issuer signature
passid proof core
Standby
No proof generated yet
Scroll storytelling

Global credit should move with the person, not stay trapped in one country.

As users scroll, PASSID walks through the core market failure: valuable financial behavior exists, but legacy credit systems cannot ingest it across geographies, employment models, or institutions. The result is friction for users and missed revenue for institutions.

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 proof status 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 proof package
Instantverification for onboarding and credit access
Step 03 · Activation

Banks, fintechs, and platforms unlock approval growth without blind risk.

PASSID gives institutions a decision-ready trust layer: verifiable, privacy-aware, and extensible via API. That means higher conversion on thin-file customers and cleaner, faster product expansion into underserved global segments.

Newcustomer segments become addressable
Lowermanual review overhead and KYC friction
Portableidentity persists across borders and rails
Developer preview
Plug PASSID into onboarding, credential verification, and cross-border trust workflows
A developer-first layer for retrieving portable verified claims, requesting ZK-backed attestations, and embedding identity proofs directly into product workflows.
Retrieve PASSID credentialGET /v1/credential
Create proof requestPOST /v1/proofs
Verify attestationPOST /v1/verify
Listen for updatesPOST /v1/webhooks
Retrieve PASSID credential
GET /v1/credential?user_id=usr_8472
curl https://api.passid.io/v1/credential?user_id=usr_8472 \
  -H "Authorization: Bearer sk_live_passid" \
  -H "PASSID-Version: 2026-03-05"
Example response
{
  "valid": true,
  "credential_status": "active",
  "claims": {
    "income_stability": "high",
    "cashflow_discipline": "moderate",
    "payment_reliability": "strong"
  },
  "stability_band": "A",
  "confidence": "high",
  "freshness_hours": 48,
  "proof": "verified",
  "signature": "ed25519_verified"
}
Low latencyVerification-ready responses designed for real onboarding flows.
Portable trustOne schema for cross-border financial identity and verifiable proofs.
Policy awareSupport institution-specific controls, governance, and audit trails.