Digital Counterparty Infrastructure (DCI) for client estates checked as counterparties
ECZ-ID DCI gives an organisation on-demand, current counterparty resolution and binding state for its digital surfaces, under a Verified or Assured Business Passport. Two add-ons extend a context plan: Live-Trust (on-demand re-checks of DCI bindings, with their freshness) and Procurement (counterparty and procurement evidence context and a supplier request-to-resolve workflow).
In an MSP client estate
Why Digital Counterparty Infrastructure (DCI) matters for a managed estate
Who it is for
The MSP problem it addresses
The client problem it addresses
When to attach it to a client
What the MSP receives
- A DCI context plan for the client organisation, and the add-ons where the client needs them.
What the client receives
- Current counterparty resolution and binding state for its digital surfaces, re-checkable by others.
How it fits the recurring Machine Trust service
Options, prices and state
Each option, as TrustOps lists it
Bought in TrustOps per plan, monthly or annual prepaid. The Business Passport tier a plan needs is priced separately and shown before payment, unless the organisation already holds it; an add-on extends a context plan in force. Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.
Digital Counterparty Infrastructure (DCI)
ECZ-ID DCI, VERIFIED context plan
ECZ-ID DCI, ASSURED context plan
ECZ-ID DCI Live-Trust Add-on
ECZ-ID DCI Procurement Add-on
States and prices from the TrustOps catalogue snapshot of 2026-10-14; TrustOps shows the current state. Buying a capability changes what you can operate. It never changes what the public record proves, and no paid tier is a verification outcome.
What you get
In TrustOps' own words
ECZ-ID DCI, VERIFIED context plan
On-demand, current counterparty resolution and binding state for your organisation’s digital surfaces, under a Verified Business Passport. It never claims more bindings than Core has verified, and it is not a certificate, TPRM replacement or legal shield.
ECZ-ID DCI, ASSURED context plan
The same DCI base under an Assured Business Passport: the higher-reliance Business Passport context. It never claims more bindings than Core has verified, and it is not a certificate, TPRM replacement or legal shield.
ECZ-ID DCI Live-Trust Add-on
The DCI-specific re-validation layer: on-demand re-checks of your DCI bindings, with their freshness and degradation state, run on the PulseGuard present-state evaluation machinery. It is not Watch (notifications) and not a second PulseGuard proposition.
ECZ-ID DCI Procurement Add-on
Structured counterparty and procurement evidence context, freshness and expiry handling, and supplier request-to-resolve workflow around DCI. It is not a generic document vault, and no procurement-suite integration is claimed.
How it works
In plain English
- 1Hold, or take, a Verified or Assured Business Passport.
- 2Choose the Verified or Assured context plan; add Live-Trust or Procurement if needed.
- 3Bindings count once Core verifies them; counterparties re-check the state at the Resolver.
Inputs
- A Verified or Assured Business Passport.
- The organisation's digital surfaces and their bindings.
Outputs and evidence
- Counterparty resolution and binding state; a surface counts once Core verifies its binding.
With your existing stack
Boundaries
What it does not do
- It never claims more bindings than Core has verified; payment never makes anything bound, verified or assured.
- It is not a certificate, a third-party risk management replacement or a legal shield.
TrustOps terms for ECZ-ID DCI, VERIFIED context plan
- Credentialing, not certification.
- Payment is not proof.
- The Business Passport tier it needs is priced separately and shown before payment, unless the organisation already holds it.
- A monthly plan cancels at the end of its period.
What buying it never changes
- the ECZ-ID of any Passport
- any regulatory status (evidence is prepared and shared, never an approval or a compliance determination)
- any child Passport assurance
Proof and integration
Resolver and Developer Gateway
Resolver relationship
Developer Gateway route
In the MSP journey
What comes before and after
Usually comes before
Related
Questions
Digital Counterparty Infrastructure (DCI): questions MSPs ask
Does DCI need a Business Passport tier?
Does buying DCI verify a client's surfaces?
Next step