BlockID
Verify the participant.
For institutions running KYC and KYB across multiple products and jurisdictions.
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, audit cost compounds. Fragmented KYC is a structural cost of fragmented infrastructure, not a procurement problem.
The identity trust layer of the Block Infrastructure architecture.
01 — Identity Trust
BlockID
Verify the participant.
02 — Payment Control
BlockPay
Govern the transaction.
03 — Digital Asset Transfer Compliance
BlockTravel
Enable compliant movement.
04 — Settlement Certainty
BlockSettle
Settle with confidence.
BlockID is the identity trust layer of the Block Infrastructure architecture — the entry point of every flow. It feeds verified-participant context into BlockPay, where transaction governance applies; BlockTravel, where Travel Rule and sanctions screening attach to digital asset movement; and BlockSettle, where compliance-conditional settlement requires a verified counterparty. Verification is done once. The architecture references it everywhere downstream.
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, network-wide compliance signals attached to verified participants and digital asset movement.
Zero Knowledge Data Checks
Counterparties confirm what they need without disclosing what they don’t. Selective attribute proof, not document handoff.
Data Monetisation
KYC verifications as a reusable, auditable data asset. Settlement of usage rights without surfacing the underlying data.
Fraud Prevention
Pre-execution participant verification, transaction governance and movement compliance — coordinated.
TCSP / Introduced Business
Verified participant attestation shared between TCSPs and onboarding institutions. Introduced-business onboarding without re-verification.
BlockID does not work alone.
BlockPay
Pre-execution compliance and orchestration for fiat payment flows. References BlockID for participant verification.
BlockTravel
Travel Rule, sanctions screening and policy enforcement for digital asset transfers. References BlockID for both originator and beneficiary verification.
BlockSettle
Atomic and conditional settlement. Requires BlockID-verified counterparties for compliance-conditional flows.
Bring BlockID into your onboarding stack.
Design partners get early access to BlockID, a direct line to the build team, influence on the V1 roadmap, and preferential commercial terms when 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.