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 ●
Security & compliance
Production access available
US financial account verification uses Stripe Financial Connections, with identity verification through Didit. Institution pilots and cross-border coverage are scoped separately.

Built for regulated financial institutions.

Designed for institution security and compliance review. Credential verification responses contain scoped claims and verification metadata rather than raw bank statement packets.

Financial source connectivity via Stripe Financial Connections Financial signal intake without raw statement sharing PASSID verification protocol for regulated institutions Financial source connectivity via Stripe Financial Connections Financial signal intake without raw statement sharing PASSID verification protocol for regulated institutions
🛡️
Security controls for review
Security, availability, and confidentiality controls are documented for institution review. Ask us for the current independent audit status.
📋
Documented practices
Review access controls, incident response, data handling, and operational procedures with the PASSID team during onboarding.
🇪🇺
Data minimization
Financial source data is processed into derived signals and claims. Credential verification responses are scoped and exclude raw balances and transactions. A DPA is available on request.
⚖️
Institution governance
Institutions can review claim performance, exceptions, and outcomes against their own policies during an evaluation.
Swipe to reveal

Scoped sharing by design.

Selective disclosure
Credential presentations are designed to expose scoped claim results and verification metadata instead of raw statements.
ES256 signing
Every credential is signed by PASSID's issuer key. Institutions verify the signature before trusting any claim. Tamper-evident from issuance to presentation.
📱 User-controlled sharing
Applicants approve scoped sharing and can revoke access. PASSID holds the credential issuer signing key; verifier checks reflect current credential status.
Data minimisation
Source financial data is processed to produce credential claims. Verifier responses are scoped to claims and metadata rather than transaction feeds.
Audit records
Verification, consent, and credential lifecycle events are logged for institution review and export.
Protected transport and storage
Public services use HTTPS. Sensitive KYB documents and provider credentials are encrypted before storage. Regional deployment options are planned for enterprise customers.

Found a vulnerability?

Report security issues to security@passid.io. We aim to acknowledge reports within 24 hours.

Scope
API endpoints, credential issuance, verification logic, wallet app, webhook delivery, and authentication.
Response targets
We aim to acknowledge reports within 24 hours, assess severity promptly, and communicate remediation plans to affected parties.
Follow-up
We coordinate with reporters on reproducible findings and share confirmed remediation details when appropriate.

Operational reliability.

PASSID is designed for institution verification workflows, with paid-plan reliability terms documented in customer agreements.

Target
Target uptime
Negotiated per institution — specified in your onboarding agreement, not a universal published SLA.
Pilot target
API latency target
Target latency for verifier API paths, monitored during operations.
Current
Deployment topology
Production uses a single application replica today. Redundancy requirements are scoped during institution review.
Scoped
Data residency
Regional deployment requirements are evaluated with each institution before any residency commitment is made.

Built for regulated markets.

PASSID provides credential verification infrastructure. All eligibility decisions and adverse action determinations remain with the institution. The verification output is structured to support institutions' own regulatory obligations.

FCRA § 615 — Adverse action support
PASSID verification responses include structured verified claim context — identity, income, sanctions status, and fraud checks — to help institutions construct FCRA-compliant adverse action notices. The institution issues the notice and applies its own policy. PASSID supplies the verified claim context.
GDPR Art. 22 — Explanation artefacts
Verification outputs include explainability artefacts to help institutions meet their GDPR Art. 22 obligations for automated decision-making. PASSID itself does not make the automated decision — your institution does, using verified claims as input.
FCA CONC — Verified claim inputs
Income verification, cashflow behavior signals, and sanctions screening outputs are documented and explainable — structured so institutions can use them as part of their own FCA Consumer Credit sourcebook eligibility assessments.
ECOA / Fair lending monitoring
Disparate impact can be tracked per corridor as part of model governance. Institutions receive audit artefacts for their own fair lending programmes.
PASSID
Thank you — we'll be in touch.