SCROLL
PASSID Credentials  ·  PASSID Verify  ·  Institution-controlled decisioning ● PassID Connect  ·  Customer-permissioned data access  ·  Hosted consent UI ● Signed claims  ·  Scoped tokens  ·  Audit metadata ● Multiple integration models  ·  One consent and audit layer ● PASSID Credentials  ·  PASSID Verify  ·  Institution-controlled decisioning ● PassID Connect  ·  Customer-permissioned data access  ·  Hosted consent UI ● Signed claims  ·  Scoped tokens  ·  Audit metadata ● Multiple integration models  ·  One consent and audit layer ●
For banks, lenders & institution teams

Verified financial evidence. Your institution decides.

Review applicant identity and financial claims with their consent. Get signed evidence, freshness checks, and an audit trail for your onboarding workflow.

Request an institution demo View sample verification

No account needed to explore the sample. Financial connections currently support US accounts. See coverage →

PassID
09:41
Verifier 24 Identity 8 Income 6 Assets 5 Cash Flow 5
PASSID
/api/v1/bridge/verify
income_verified
TRUE
VerifiedData minimised
identity_verified
TRUE
VerifiedUser-controlled
credential_freshness
48h
VerifiedData minimised
raw_bank_feed
NOT SENT
InstitutionNo raw data
Audit trailInstitution keyIdempotencyWebhookTimestampedExportable
CredentialsSecurely verified
YouIn control
InstitutionsTrusted & verified
PermissionsYou decide

You choose the data boundary. PASSID enforces the approved scopes; your institution owns policy and final decisions.

Built on trusted infrastructure
Stripe
Didit
One financial history

One financial history. Multiple proofs.

Every PASSID credential is built from the same signed, user-permissioned history — organized into five proof categories institutions can request independently, and nothing more.

🪪
Identity
Verified identity and sanctions status, without a raw ID scan.
💰
Income
Multi-source income stability, band, and consistency.
🏦
Assets
Balance resilience and savings behavior over time.
📊
Cash Flow
Spending discipline and payment reliability signals.
💼
Employment
Tenure, continuity, and employer-verified signals.
How PASSID works

Four steps from user consent to institution verification.

Users connect financial sources, PASSID creates signed credential claims, users share scoped tokens, and institutions verify the claims inside their own systems.

PASSID Credential Infrastructure
connect account → issue credential → verify credential
STEP 01
🏦
User connects financial sources
The user connects supported financial sources with consent. PASSID reads the signals needed to create claims.
Flow 01
STEP 02
🔐
PASSID creates signed claims
PASSID normalizes user-permissioned signals into a signed, portable credential with freshness and revocation metadata.
Flow 02
STEP 03
🧠
User shares a scoped token
The applicant chooses what to share and hands the institution a scoped PASSID token.
Consent
STEP 04
⚡
Institution verifies and decides
The institution verifies signed claims, freshness, revocation, and audit metadata without receiving raw financial data feeds.
Flow 03
Banks → Credentials
Signals → PASSID Credential
PASSID → Verification
Evaluate one review workflow

Give your review team evidence they can check.

Start with an onboarding workflow that requires identity and financial evidence. Your team reviews consented claims, checks their freshness, and keeps the final decision in your existing process.

01
Choose the evidence your review team needs
02
Let applicants approve the claims they share
03
Check signatures, freshness, and revocation
04
Measure review time and missing evidence in a pilot
Banks & lenders Fintechs & platforms Students Migrants Gig workers Cross-border See all solutions →
Choose your integration

One platform. Different ways to integrate.

Start with the workflow and data boundary your institution needs. Products can run independently or combine behind one customer consent and audit trail.

↗
Hosted experience
PassID Connect

PASSID hosts customer authentication, institution disclosure, scope review, consent, and return to your application.

Best whenYou want the fastest integration and PASSID to own the customer authorization UI.
 ↗
Embedded integration
APIs & SDKs

Keep your existing customer experience while using PASSID sessions, consent controls, webhooks, and server-side APIs.

Best whenYour institution owns the frontend and needs infrastructure-level integration.
 ↗
Claims-only evidence
Credentials & Verify

Issue or verify portable signed claims with freshness, revocation, signature status, and audit metadata—without a raw financial feed.

ReturnsOnly approved credential claims and verification metadata.
 ↗
Permissioned data
Financial Data Access

Request approved account, balance, liability, or transaction scopes when your workflow requires underlying financial data.

ReturnsOnly the specific data scopes and duration the customer approved.
 ↗
Operations
Institution Workspace

Manage customers, applications, consent, cases, reviews, API keys, webhooks, billing, and audit evidence in one workspace.

Best whenOperations and compliance teams need a managed control surface.
 ↗
Sandbox live · No live funds
PassID Pay

Payment and payout orchestration built around verified identities, consented destinations, institution controls, and portable transaction evidence.

AvailabilityInteractive sandbox available. Production payment rails remain limited to approved use cases and licensed providers.
Technology

Built like infrastructure.
Not like a dashboard.

PASSID is built for open-banking style financial data connections and transforms verified financial signals into portable, verifiable credentials.

Every architectural decision serves verifier trust: signed claims, freshness, revocation, and auditability.

01
Proof Metadata
Credential responses include proof type, issuer signature status, freshness, provenance, and revocation metadata for verifier policy checks.
02
Freshness + Revocation
Credential expiry and revocation endpoints let institutions check whether a presented credential is still usable at verification time.
03
AML + Sanctions Screening
Verification workflows can include OFAC, EU, and UN list checks, PEP identification, and audit records for institution review.
04
Governance Review Support
Pilot partners can review claim performance, exception rates, revocation behaviour, and corridor-level outcomes using institution-defined governance criteria during the live-access review process.
05
Minimal Verifier Payloads
Verifiers receive scoped claim summaries and verification metadata rather than financial statements or transaction feeds.
🏢
Signal Sources
PSD2 · Account aggregators · Mobile money
INPUT
Encrypted data ingestion
⚙️
passid-core
5-pillar signal model · AML · Bias check
COMPUTE
Credential proof package
🔒
passid-issuer
Issuer signature · Proof metadata · Revocation
ISSUE
Signed portable credential
📡
passid-verifier
REST API · claim verification · audit-ready
VERIFY
Signed claims + audit metadata
🏛️
Institution System
Policy workflow · Scope-enforced outputs
DECIDE
Compliance & Security

Built for regulated financial institutions.

Every design decision serves the same goal: making credential verification easier for compliance, risk, and engineering teams to review.

🛡️
AML & Sanctions
Screening outputs can be included in credential verification workflows for institution review.
OFAC SDN list
EU Consolidated list
UN Security Council list
PEP identification
🔒
Privacy by Design
Verifier payloads are designed around scoped claims rather than raw statements.
No raw financial statements in verifier response
Claim-level consent
GDPR-aligned architecture
Right to revoke credential
⚖️
Governance Review
Pilot partners can review claim performance and outcome distribution using their own institution-defined governance criteria.
Claim accuracy review
Exception rate review
Model drift monitoring
Pilot outcome reporting
Institution evaluation

Start with one workflow. Agree on what success means.

Bring the evidence requirements for one onboarding or review process. We can walk through a sample verification, confirm supported sources, and scope a sandbox evaluation with your operations and technical teams. Pilot scope, fees, and production requirements are agreed separately.

Discuss your evaluation
Or email hello@passid.io to discuss your use case.
What to agree before a pilot
01
One workflow and its current review timeBaseline
02
Required claims and supported sourcesCoverage
03
Consent, revocation, and audit reviewControls
04
Sandbox verification with your teamIntegration
05
Completion, review time, and exceptionsMeasures
06
Commercial terms and live-access reviewNext step
PASSID
Thank you — we'll be in touch.