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 Connect
Production access available

PassID Connect.
Customer-controlled authorization.

PassID Connect lets institutions request verified identity and financial claims through a customer-launched, hosted consent flow. The institution creates the request, the customer authorizes in PassID, and approved scopes return through a connection_id.

passid-connect
PassID Connect

A hosted authorization flow for verified customer data access. Customers click Connect with PassID inside your application, authenticate in PassID, review permissions, and return with an approved connection.

✓  Hosted UI or redirect authorization
✓  Scoped consent and access duration
✓  connection_id for approved data
✓  Dashboard status and audit trail
passid-issuer
Issue Credential

Compiles user-permissioned signals into a signed, user-held credential with freshness, expiry, and revocation metadata.

✓  W3C VC / DID standard
✓  Ed25519 signing
✓  Signature and proof metadata
✓  On-device key storage
passid-verifier
Verifier API

One API call to verify a PASSID token. Returns signed claim summaries, signature status, freshness, revocation status, and audit metadata. It does not return raw financial data feeds.

✓  Verifier response shape
✓  REST + webhook delivery
✓  Sanctions / PEP / AML checks
✓  Audit-ready metadata

Institution request. Hosted PassID consent. Approved connection.

The institution backend creates a scoped request, the customer launches PassID from the institution app, and PassID returns a connection_id only after customer approval. Credentials and verifier APIs support this flow behind the scenes.

01
FLOW 1
Connect account
The customer starts in the institution application and clicks Connect with PassID.
connect launched
02
FLOW 2
Authorize in PassID
PassID hosts sign-in or optional code entry, shows the verified institution, scopes, purpose, and duration, then records consent.
customer approved
03
FLOW 3
Use connection_id
The institution receives a connection_id and retrieves only the approved scopes through server-side APIs.
scopes enforced
04
BOUNDARY
Institution decides
PASSID verifies claims. The institution applies its own policy, review, and decision workflow.
institution decides
What PASSID is not: not a credit bureau, not a bank, not an institution decision workflow, and not a raw transaction store for verifier access. PASSID verifies signed claims; institutions decide.

Credential claim categories for the three core flows.

$
Income Stability
Multi-source income verification. Avg surplus. Volatility index. Cross-currency normalisation.
BANK
Remittance Track Record
24-month payment streak. Corridor consistency. On-time remittance ratio.
HOME
Rent & Utility Payment
Housing payment history. Utility streak. Behavioural consistency signals.
TIME
Platform Tenure
Months on platform. Employment continuity. Multi-platform income diversification.
DATA
Debt Service Coverage
DSCR computed from live cashflow. Stress-tested against corridor-specific scenarios.
AML
Identity & AML
Sanctions / PEP check. Adverse media scan. Synthetic identity detection. Velocity signals.

Test PassID Connect.

Use the sandbox to create a hosted request, launch PassID authorization, approve consent, and fetch scoped data before production review.

PASSID
Thank you — we'll be in touch.