BlockID
Verify the participant.
For banks and regulated financial institutions that need to verify a participant once, to the standard their supervisor expects, and reuse the proof instead of re-running KYC and KYB at every counterparty.
Identity verification, duplicated, everywhere.
Every regulated institution treats identity verification as a hurdle a customer or counterparty must clear before doing anything else. The same individual or entity is verified again at the bank, again at the EMI, again at the PSP, again at each digital asset platform. Each verification is a separate workflow with its own data, audit trail and regulatory ownership.
This creates three structural costs. Duplicated verification work that no party can recover. Slower onboarding that compounds across the customer journey. Static KYC data that ages without either party knowing it has aged.
Institutions operating across multiple products and jurisdictions feel this most acutely. Duplication multiplies and audit cost compounds. Fragmented KYC is a structural cost of fragmented infrastructure, not a procurement problem.
The verification network for regulated onboarding and ongoing due diligence.
01 · Identity Compliance
BlockID
Know who you are dealing with.
02 · Transaction Compliance
BlockTravel
Clear every payment before it moves.
BlockID is a distributed KYC and KYB verification network for regulated financial institutions. Verify a participant once, and reuse that proof across the network, instead of every institution and every product re-running the same check.
Every verification produces a tamper-evident attestation that the participating institution can reuse the next time the same individual or entity needs to be checked. The audit trail stays intact, the standards stay attached, and nobody re-runs the check from scratch.
The network runs on distributed ledger technology, the infrastructure behind web3, because it lets several institutions rely on one record without any of them owning the data. The verification itself is performed to the standard a bank already operates to under FCA, MAS or equivalent supervision. Nothing about the technology changes the obligation; it changes how often the work has to be repeated.
Verification as architecture, not as ceremony.
Reusable verification
One verification per individual or entity, referenced by every participating institution. Same verification, multiple downstream uses.
Auditable attestation
Every verification produces a tamper-evident attestation record: when, by whom, under which standards. Auditable across the participating network.
Privacy-preserving disclosure
Selective attribute disclosure. Counterparties see what they need to see; everything else stays private. Aligned with GDPR data minimisation principles.
Cross-jurisdiction portability
Verifications carry the regulatory framework they were performed under. An FCA-grade KYC reads as FCA-grade everywhere; a MAS-grade KYC reads as MAS-grade everywhere.
API-first architecture
REST and event-driven APIs. Drop into existing onboarding flows, KYC platforms or compliance pipelines without re-architecture.
What BlockID is built on.
- DABA
- MiCA
- FATF Travel Rule
- GDPR
- FCA
- MAS
- OpenAPI 3.0
- Zero-knowledge Proof
- mTLS
- Immutable audit logging
- OAuth2
The standards above are not aspiration. They define how BlockID is built and how it must operate. Where a framework is in progress, we say so.
API-first, sandbox-evaluated, production-ready.
BlockID exposes a REST API and an event subscription layer. Onboarding integrations require five endpoints: initiate verification, attach evidence, poll status, retrieve attestation, and revoke.
Webhook events fire on verification completion, attestation expiry and revocation. The sandbox environment mirrors production with synthetic counterparties for unassisted evaluation.
Where BlockID does the load-bearing work.
Network Compliance Oracle
Real-time compliance signals attached to verified participants and every leg of a payment.
Zero Knowledge Data Checks
Counterparties confirm what they need without disclosing what they don’t. Selective attribute proof, not document handoff.
Financial Crime Prevention
Pre-execution participant verification and movement compliance, across every leg.
Also from Block Infrastructure.
Bring BlockID into your onboarding stack.
Design partners get early access to BlockID, a direct line to the build team, a say in what gets built next, and preferential commercial terms once BlockID moves out of design partner stage. We ask for genuine integration intent, a structured feedback loop with named technical and compliance counterparts, and a mutual non-disclosure agreement.