Product Platform

Product suite

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

✓ ES256 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

passid-data-access

Financial Data Access

Permissioned access to underlying financial data when a claims-only response is not sufficient for the institution workflow.

✓ Account, balance, liability, and transaction scopes

✓ Purpose and duration recorded with consent

✓ Scope-by-scope access enforcement

✓ Customer revocation controls

passid-institution

Institution Workspace

A managed operating surface for customer verification, applications, cases, consent, compliance review, integrations, and audit evidence.

✓ Customer and application operations

✓ Review queues and case management

✓ API keys, webhooks, and usage

✓ Consent and audit exports

passid-pay · sandbox live

PassID Pay

Payment and payout orchestration built around verified identities, consented destinations, institution controls, and portable transaction evidence. Interactive sandbox available. Production payment rails remain limited to approved use cases and licensed providers.

✓ Institution payment authorization

✓ Recipient consent and destination confirmation

✓ Institution policy controls

✓ Sandbox live — no funds moved

Hosted integration example

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.

FLOW 1

Connect account

The customer starts in the institution application and clicks Connect with PassID.

connect launched

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

FLOW 3

Use connection_id

The institution receives a connection_id and retrieves only the approved scopes through server-side APIs.

scopes enforced

BOUNDARY

Institution decides

PASSID verifies claims. The institution applies its own policy, review, and decision workflow.

institution decides

⚠

Data boundary: Credentials and Verify return signed claim summaries, not raw financial feeds. Financial Data Access returns underlying data only when the customer explicitly approves those scopes. In every model, the institution makes the final decision.

PassID Connect

The "Connect with PassID"
button, designed for any institution type.

Customer clicks. PassID handles authentication, identity verification, and consent. You receive a connection_id that unlocks only the scopes the customer approved.

PassID Connect — interactive flow demo

Open full demo

Two API calls. Customer does the rest.

Your backend creates a connection request and gets back a hosted URL. Redirect your customer there — PassID handles sign-in, identity verification, and consent entirely. You're redirected back with a connection_id. Done.

Data scopes you can request

identity.read income.read accounts.read balances.read transactions.read verification_status.read liabilities.read

No manual PassID code entry — customer initiates directly from your site or app

PassID hosts the entire sign-in and consent UI — zero frontend work from you

Customer approves on their device — bank credentials are never shared with your institution, and every approval is audited

Idempotency keys, revocable 90-day access, and real-time webhook events on every connection

Open Sandbox Dashboard Integration Guide Learn more

Designed for any institution type

Banks & credit unions Investment platforms Lending & insurance Rental platforms Gig economy Marketplaces

            
            
            
            passid-connect.http — 2 backend calls, 0 frontend work
          
// Step 1 — Your backend creates the hosted session (server-side)
POST /v1/connect/sessions
Authorization: Bearer live_institution_key
{ "scopes": ["identity.read","income.read","accounts.read"],
  "return_url": "https://yourapp.com/callback",
  "purpose": "Verify identity to open account" }
→ { "hosted_url": "https://app.passid.io/connect/authorize?..." }
// Step 2 — Redirect customer to hosted_url
// PassID handles: sign-in · verification · consent UI
// Customer approves → PassID calls your return_url:
?session_id=pcs_live_...&connection_id=conn_live_...&status=approved
// Step 3 — Verify callback, then fetch authorized data
GET /v1/connect/sessions/:session_id
GET /v1/connect/connections/:id/identity
→ { identity, income, accounts, balances, transactions… }

            Webhook events delivered to your endpoint
            REAL-TIME
          
              connect.session.approved
              connection_id, approved_at, scopes
            
              connection.created
              connection_id, client_id
            
              connect.session.declined
              request_id, declined_at
            
              connection.revoked
              connection_id, revoked_by

Publishable key

pk_test_···

Frontend · safe to expose

Secret key

sk_test_···

Server-side only · never expose

Customer-initiated

The customer clicks "Connect with PassID" on your page. No staff involvement, no manual code entry. The entire flow is customer-driven — from your app all the way back.

PassID hosts the UI

PassID owns sign-in, identity verification, and the full consent experience. You build nothing for the flow itself — no UI work, no form handling, no credential management on your end.

Instant data access

The connection_id in your callback unlocks identity, income, accounts, balances, and transactions with a single GET request. Customer revokes any time from their PassID wallet.

Verified signal categories

Credential claim categories for the three core flows.

💵

Income Stability

Multi-source income verification. Avg surplus. Volatility index. Cross-currency normalisation.

🏦

Remittance Track Record

24-month payment streak. Corridor consistency. On-time remittance ratio.

🏠

Rent & Utility Payment

Housing payment history. Utility streak. Behavioural consistency signals.

⏳

Platform Tenure

Months on platform. Employment continuity. Multi-platform income diversification.

📊

Debt Service Coverage

DSCR computed from live cashflow. Stress-tested against corridor-specific scenarios.

🪪

Identity & AML

Sanctions / PEP check. Adverse media scan. Synthetic identity detection. Velocity signals.

Credential signal graph

A financial signal graph for portable verification

PASSID maps verified accounts, remittance rails, savings behavior, salary flows, and institution attestations into signed credential claims. Instead of restarting from zero, users can present a verifier-ready token across markets.

Signal composition

Income stability

✓

Cashflow discipline

✓

Payment reliability

✓

Fraud integrity

✓

Compliance gate

✓

From raw history to portable trust

Each node represents a verified behavior source. PASSID turns fragmented financial footprints into claim objects that lenders, banks, and platforms can review without receiving raw personal data.

One trust platform.
Your integration model.

Institution request. Hosted PassID consent. Approved connection.

The "Connect with PassID"
button, designed for any institution type.

Two API calls. Customer does the rest.

Credential claim categories for the three core flows.

Signal composition

From raw history to portable trust

Choose your PASSID integration.

Institution request. Hosted PassID consent. Approved connection.

The "Connect with PassID"button, designed for any institution type.

Two API calls. Customer does the rest.

Credential claim categories for the three core flows.

Signal composition

From raw history to portable trust

Choose your PASSID integration.

The "Connect with PassID"
button, designed for any institution type.