After 25 years of refinement for healthcare and government, SDC4 is the data substrate that makes verifiable settlement possible
SDC provides VSL: two SDC-compatible agents exchange data and conditionally release value or state, with cryptographic verification and no trusted intermediary.
Two parties want to exchange data and conditionally release value or state. Today that requires a trusted intermediary, because neither side can independently prove the exchange was correct.
Settlement is buyer-native across finance, logistics, healthcare, and the federal sector, yet every exchange still leans on a trusted intermediary. Without verifiable data semantics and bound provenance, no counterparty can settle directly with confidence.
VSL is a fourth layer on top of the SDC data substrate. It verifies three things at once, then emits a settlement record.
VSL confirms that the data conformed to its bound schema before settlement. The check is cryptographic, so the result can be verified without re-running the validation and without exposing the data.
Bound schema → Conformance check → Settlement proof (data conformed)
Ontology URIs remove interpretation errors, and each component carries its own provenance chain. VSL confirms the action was authorized by that chain across every domain involved.
mc-abc123 → authorized by provenance chain
Programmable settlement logic releases value or state only when both conditions hold: the data conformed and the action was authorized. Neither party can release unilaterally.
Conformed + authorized → release value or state
Audit trails, attestations, and participations are already part of SDC4. VSL combines the three checks into a tamper-evident, machine-verifiable settlement record any third party can audit.
Three checks → tamper-evident settlement record
We did not design SDC4 to settle transactions. We designed it to solve the data problems that settlement depends on: schema conformance, semantic clarity, bound provenance, and durable audit. VSL is what those properties make possible.
The building blocks VSL composes from the SDC substrate: a settlement event, its verification checks, the record it produces, and the confidential audit that follows.
Two SDC-compatible agents agree on a bound schema and a conditional release. The settlement event begins when one counterparty presents data and the action it intends to settle.
VSL verifies three things at once: the data conformed to its bound schema, the action was authorized by its provenance chain, and the conditional release was triggered by both.
The output is a tamper-evident, machine-verifiable settlement record. It captures the outcome and its three proofs so the result stands on its own, independent of either party.
Any third party can audit a settlement record without seeing the underlying data, a zero-knowledge property. Auditors confirm correctness; the data itself stays confidential.
From legacy EDI to verifiable settlement: how existing transaction sets map onto the Verifiable Settlement Layer
How legacy EDI modernization positions enterprises for verifiable settlement. The same Purchase Order moves from X12 to an SDC4 component to a conditional settlement.
The full architecture: settlement events, the three verification checks, the settlement record, confidential third-party audit, and the 10-year roadmap.
Verifiable settlement across the domains where settlement is already buyer-native
Purchase Orders, Invoices, and Ship Notices verified against their bound schemas. The conditional settlement releases payment only when every condition is met, with no intermediary.
Credentials carry SDC4 schema validation and a provenance chain. Medical records, educational certificates, and employment history settle between counterparties without exposing the data itself.
FHIR resources validated with SDC4 settle claims between payer and provider. Each settlement record proves the claim conformed and was authorized, audited without revealing patient data.
Property records, business licenses, and permits settle between agencies as tamper-evident records. Cross-agency exchange proceeds without a central clearing authority.
Carrier invoices and proof-of-delivery data settle against the agreed schema. The settlement record confirms conformance and authorization, so freight charges release without dispute cycles.
Counterparties exchange validated data and settle value or state directly. Provenance travels with the data, and a third party can audit the settlement record without seeing the contents.
From first deployments to invisible infrastructure: how SDC4 and VSL become the default settlement substrate
VSL goes live on the SDC4 substrate. The first enterprises settle supply chain and credential exchanges with verifiable settlement records.
Finance, logistics, and healthcare counterparties adopt VSL for direct settlement. Shared schemas make settlement records portable across organizations. Network effects accelerate.
Verifiable settlement on SDC4 becomes the default for high-value exchange. New systems expect it. Settlement that cannot be independently verified is treated as technical debt.
SDC4 and VSL are infrastructure. Like TCP/IP, operators do not think about them; settlement just works. The verifiable settlement layer that high-value exchange needed all along.
We built the substrate that settlement quietly depends on, because it just works.
Invisible, verifiable, and everywhere high-value data is exchanged.