Trade Flow Orchestration & Trusted Data Sharing

Move goods and share data with confidence. Digitalise trade flows
with identity-bound documents, clear provenance and policy-driven automation
– plus secure data sharing for tomorrow’s connected ecosystems

Move goods and share data with confidence.
Digitise trade flows with identity-bound documents,
clear provenance and policy-driven automation
– plus secure data sharing for tomorrow’s
connected ecosystems

Trade isn’t just about moving goods anymore – it is about connecting identities, documents and data under enforceable policies. The classic Buy–Ship–Pay model still anchors global trade, but today’s reality demands verifiable trust at every step – from contracting to delivery to settlement to audit.

What we Deliver

Document Orchestration

eCMR (road), eBL (maritime), eFTI‑aligned payloads – with templates, lifecycle states, versioning, and notifications.
Identity‑bound signing & sealing: sign with vLEI roles (OOR/ECR) and LPID attributes; enable QES/QSeal via QTSP partners for legal enforceability.
Embedded evidence: timestamps, credential references, revocation status.

Provenance That Stands Up in Disputes

Legal provenance (Chain of Title): maintain endorsements/transfers/surrender for eBL without changing the content (title transfer events are legal, not operational edits).
Operational provenance (Version & Enrichment): for eCMR, record the living history – signatures, photos, IoT, geostamps – across the journey.
Anchored in GAIA-X–compliant decentralised storage for tamper-evidence and auditability.

Trusted Data Sharing (Beyond Trade, Too)

Share sensitive data from decentralised or federated storage; reference them inside Verifiable Credentials instead of storing the data in wallets.
Verify who is requesting (LPID/vLEI), what rights they have (roles, delegations), and where/when they can use it (policies, expiries), before data flows.
Integrate with data spaces using IDSA Dataspace Protocol and optional Decentralised Claims bridges for machine‑to‑machine trust. Ideal for ports, logistics, legal, government, or any scenario requiring selective, auditable data exchange.

Policy & Workflow Engine

Visual builder for steps, approvals, hand‑offs, conditional logic (credential status, risk rules, geofencing/time windows), SLA tracking, escalations, and exception handling.
Real‑time dashboards for shipment status, exceptions, and signature/compliance views; exportable audit reports.

Interoperability & Connectors

Works with Port Community Systems, TMS, ERP, carrier systems; webhooks/events for status sync and RPA triggers.
Wallet‑agnostic: EUDI Business Wallets, organisational wallets (vLEI), and common device wallets; DC‑API to request presentations in existing web apps – no wallet protocol plumbing required.

Provenance explained

Legal Provenance = “Who owns the title?”

For eBL and similar title documents, the content is static after issuance. What changes is who controls the title (endorsements, pledges, transfers, surrender). We track those legal events as a chain of title – cryptographically signed, timestamped, and auditable – without mutating the document itself.

Operational Provenance = “What actually happened in the journey?”

For eCMR, the document evolves: load/unload confirmations, signatures, photos, GPS/IOT readings, customs annotations. We maintain a versioned enrichment history so you can reconstruct every operational step if a claim or audit arises.

Where It Lives

Provenance events are stored in GAIA‑X–aligned decentralised storage with optional blockchain anchoring for immutability. Legal (chain‑of‑title) and operational (enrichment/versioning) histories remain separable yet cross‑referenced, ensuring clarity for courts, banks, insurers, terminals and regulators.

How It Works

Verify & Bind
Parties present vLEI (with roles) or LPID from their chosen wallet. We verify and bind identities to documents and steps – no change to your existing IdP/SSO.
Orchestrate the Flow
Use policies to govern who can initiate, approve, endorse or release: e.g., “Only ECR role can endorse eBL transfer,” or “Driver must present PID/LPID within a geo‑fenced window at gate.”
Sign & Seal (When Needed)
Apply QES/QSeal with QTSP partners for legal enforceability; every step emits verifiable evidence (timestamps, credential refs).
Share Data, Not Copies
Share links to decentralised content under policy – VCs reference the data; wallets verify rights; connectors enforce decisions in data spaces.
Prove What Happened
Legal and operational provenance is tamper‑evident and exportable for audits, claims, and dispute resolution.

Identity Readiness

vLEI ecosystem: available now – GLEIF-backed, globally interoperable.
LPID/EUDI wallets: emerging – we track eIDAS2 and EUBW rollout; ready to adopt when available.

Why TradeVeris

Anchor trust end‑to‑end
Identities, documents, data and decisions – verifiable at every step.
Wallet‑agnostic & future‑ready
Works with EUDI Business Wallets and organisational wallets; avoids vendor lock‑in.
Made for real operations
Policy engine, SLA tracking, exception flows and clean connectors for PCS/TMS/ERP.
Provenance clarity
Separate legal chain‑of‑title from operational versioning – crucial for eBL vs eCMR.
Beyond trade
Reuse the same trusted data‑sharing stack for legal and eGovernment workloads.

Use Cases

Cross-Border Road Made Simple: Secure Documents, Smart Data Sharing

The Consignor creates and signs an eCMR in TradeVeris, binding it to their vLEI identity.
The Carrier authenticates with LPID/vLEI at pickup, enriches the eCMR with photos and geostamps, and continues the journey.
When customs stops the truck, the Carrier presents a verifiable credential and TradeVeris releases only the required eFTI fields, for that purpose and time window – no full document exposure, fully logged.
At the Warehouse, the Carrier updates the eCMR with delivery details; the Warehouse confirms receipt.
Under DAP/DDP, risk transfers and TradeVeris issues an eBoE to the Buyer.
If the Buyer requires inspection, the Warehouse grants time‑boxed, read‑only access, then the Buyer accepts the eBoE with their vLEI.
An optional Bank Aval guarantees payment.
Funds are released; TradeVeris exports a verifiable audit pack covering identities, policies, signatures, and events.
Through it all, the eCMR remains with the Consignor – partners get governed access via Trusted Data Sharing, not uncontrolled copies.

Benefits at a Glance

Consignor: Control documents, automate risk transfer, stay audit-ready.
Carrier: Easy eCMR access, quick updates, faster customs clearance.
Warehouse: Confirm receipt securely, enable scoped inspection access.
Buyer: Real-time delivery visibility, controlled inspection, enforceable acceptance.
Customs: Purpose-limited eFTI data, faster checks, full audit trail.
Bank: Verified Aval issuance, guaranteed settlement, compliance evidence.

Ocean Transport with eBL – From Purchase to Delivery

A Buyer sources goods from an overseas Seller under CIF terms. The Carrier issues a negotiable eBL after loading, binding identities with vLEI/LPID and applying QSeal/QES for legal enforceability. TradeVeris orchestrates the entire flow:

Contract & Identity Binding: Roles and policies set upfront for endorsements, compliance, and SLA windows.
Issuance & Chain of Title: eBL content remains immutable; endorsements (Seller → Bank → Buyer) are logged as signed title events.
Event Automation: Arrival triggers customs clearance and readiness checks; Buyer endorsement enables electronic surrender; acceptance triggers settlement.
Compliance Hooks: Customs and regulators receive only purpose-limited data (eFTI, security filings) under policy – never full documents.
Delivery & Surrender: Buyer presents the eBL electronically; Carrier releases goods to the rightful holder.