Skip to content
EcoCitizenZ
HomeCatalogParent Passport TiersECZ-ID Business Passport™ — Verified
Parent Passport TierVerified

ECZ-ID Business Passport™ — Verified

Resolver-verifiable identity + child passport access

Who it is for: Operators ready to activate child passports, badge provisioning, and integration access.

In plain terms

The Verified tier is the operating tier for businesses ready to attach child passports, packages, and add-ons.

The real-world problem

What this removes

Most child passports and packages require a Verified or Assured parent. Operators stuck at Declared cannot activate the credential estate they need.

Ambiguity removed

Removes ambiguity about whether the parent identity has been independently verified to the operating tier required for child activation.

What it binds / includes

Scope of accountability

Binds the organisation to a verified operator record that supports child passport, package, add-on, and badge activation in TrustOps.

Parent requirement: Establishes the parent identity spine at this tier.

  • · Everything in Declared
  • · Child passport activation
  • · Badge provisioning
  • · Insurability readiness
  • · Integration API access
  • · Authority delegation

Stack contributions

What PulseGuard™, LedgerCore™, and Resolver contribute

PulseGuard™

PulseGuard™ contributes present-state monitoring such as liveness, freshness, revocation or suspension state, and posture changes where supported by the activated passport/package.

LedgerCore™

LedgerCore™ records decisive lifecycle and evidence events where supported, such as issuance, activation, authority changes, child passport creation, revocation, bundle activation, badge state changes, or receipt references.

Resolver

Resolver shows current state for this product where supported — including active/suspended status, parent linkage, attached child passports/packages/add-ons, and the most recent receipt references. Current proof must be checked in Resolver.

Badge / mandate plate

Where this product has an ECZ-ID badge or mandate plate, the badge is an embeddable visual pointer to the Resolver state. The badge is not proof by itself; the Resolver check is the proof surface.

Insurability Readiness™ impact

Verified is generally the working tier for readiness signals composed from an active stack.

Boundary of claim

What this product does not claim

  • · Does not certify the operator is lawful in every jurisdiction.
  • · Does not replace counterparty due diligence.

Guided flow

Six steps from need to resolved state

  1. 01

    Understand the need

    Decide what commercial friction you are trying to remove. Developer Gateway documents the model. It does not determine eligibility, issue credentials, or create entitlements.

  2. 02

    Confirm parent requirement

    Every child passport, package, and add-on attaches to an active ECZ-ID Business Passport™. Verified or Assured may be required (per TrustOps).

  3. 03

    Review what this product does

    Check what is bound, what is included, and what it does not claim. No safety, certification, approval, or partnership claim is made on this page.

  4. 04

    Continue to TrustOps

    Acquisition, activation, payment, and lifecycle happen in TrustOps. Developer Gateway only routes the handoff.

  5. 05

    Return to Developer Gateway

    After TrustOps, return here for next-step docs and related guidance. Developer Gateway still does not prove current state.

  6. 06

    Check current proof in Resolver

    Current proof must be checked in the public Resolver. Copied metadata, screenshots, or website claims do not replace Resolver.

TrustOps midpoint

Acquisition, setup, payment, and lifecycle happen in TrustOps

Developer Gateway only routes. It does not host checkout, change canonical state, issue credentials, or replace Resolver proof. TrustOps owns the operational state for this product.

Choose the Verified Business Passport tier

TrustOps URL: https://trustops.ecocitizenz.com/start

Return path

Come back here for next-step docs

After TrustOps completes acquisition or activation, return to Developer Gateway for related docs and guided next steps. Developer Gateway still does not prove current state. Current proof remains in Resolver.

Resolver proof

Current proof must be checked in Resolver

Copied metadata, screenshots, badges on third-party websites, or any claim made on Developer Gateway do not replace Resolver. The Resolver is the sole public proof surface for ECZ-ID.

Open Resolver ↗

Resolver URL: https://resolver.ecocitizenz.org

Recommendation

Find your recommended starting point

Enter your website URL. TrustOps will use it to recommend a starting point. Developer Gateway sends the URL only; TrustOps handles the recommendation, setup, payment, and lifecycle controls.

Developer Gateway does not host checkout, change canonical state, issue credentials, or replace Resolver proof. Current proof must be checked in Resolver.

ECZ-ID separates setup, verification state, and public proof. Developer Gateway documents setup paths and verifier guidance. TrustOps handles setup. Resolver remains the public proof surface. Re-check before reliance. Local policy decides.