Frequently Asked Questions (FAQs)

General

TradeVeris is a digital trust platform that connects identities, credentials and data across global trade and beyond. Its Identity & Access Management suite ensures secure, role-based access for people and organisations. The Connected Identity & Credential Suite adds verified claims like compliance and due diligence. And with Trade Flow Orchestration, businesses can automate document exchange and data sharing with full traceability and trust.

TradeVeris is built for openness, control and compliance. Unlike closed platforms, it’s accessible through any trusted wallet – from eIDAS to Google or Apple – and supports interoperable credentials like vLEI, LPID, and even signed PDFs. There is no lock-in: users own their data, credentials stay in their wallet, and documents can be stored in decentralised environments. TradeVeris is fully compliant with global standards, making it ready for today’s regulations and tomorrow’s innovations.

Identity & Access Management (IAM)

No – TradeVeris delivers a single wallet experience with both identity ecosystems integrated. If you only work with one ecosystem – either vLEI or LPID – you can use any GLEIF-compliant or eIDAS-compliant wallet respectively.

Yes – integrate via SAML or OIDC using your existing IdP, such as Okta or Entra.

You can use TradeVeris-integrated vLEI features alongside your preferred eIDAS-compatible wallet provider. A personal wallet typically runs on a mobile device, while an organisational wallet is usually cloud-based.

DC-API lets partner portals request credential presentations without implementing wallet protocols, making integration faster and the user experience smoother.

No. We integrate with your IdP (SAML/OIDC) and enrich authentication/authorisation with verifiable credentials.

TradeVeris orchestrates the checks and issues credentials reflecting outcomes. Sensitive evidence does not need to reside in your systems.

Add our verification widget/API call where you need higher assurance. Everything else stays the same.

Connected Identity & Credential Suite

Traditional processes rely on PDFs, emails, and manual checks, which are slow and error‑prone. Credential Enrichment uses verifiable credentials – cryptographically signed, instantly checkable, and reusable, so clearance is faster, fraud risk drops, and data sharing is privacy‑centric.

Yes. It delivers IMO FAL data and related attestations in standardised, machine‑verifiable formats, aligning with the Maritime Single Window (MSW) mandate and the EU’s EMSWe framework. This helps ports meet regulatory obligations while reducing duplication and manual effort.

TradeVeris provides APIs, widgets, and ready‑to‑use templates for PCS, gate systems, and compliance portals. While local endpoints (e.g., customs or PCS) may require configuration, Credential Enrichment minimises complexity by using open standards like OID4VCI/OID4VP and trust registries such as EBSI.

Selective disclosure means sharing only the attributes required for a specific purpose – such as DG class without the full manifest or crew nationality without document scans. Every presentation is consent‑based, logged, and auditable for compliance.

Organisational and personal wallets are device‑bound, protected by biometric unlock and FIDO2/WebAuthn, and every credential is cryptographically signed. This ensures strong identity assurance and prevents impersonation or credential.

Trade Flow Orchestration & Trusted Data Sharing

The orchestration layer is the policy-driven engine that connects identities, documents, and events across the trade lifecycle. It doesn’t just store documents – it automates actions based on triggers, enforces compliance, and ensures every step is verifiable.

 

Core Capabilities

  • Event Automation
  • Cross-Document Logic
  • Compliance Hooks
  • Policy Enforcement
  • Identity Binding
  • Integration Ready

Why It Matters

Instead of manual handoffs or fragmented systems, TradeVeris provides a single orchestration layer that makes trade flows predictable, compliant and auditable – while keeping sensitive data under your control.

Yes. We layer on top with APIs/webhooks and verification widgets – no heavy protocol work required.

Yes – via QTSP partners. We embed QES/QSeal and return evidence packages for audit/non‑repudiation.

We explicitly separate legal (e.g., eBL title transfer) from operational (e.g., eCMR enrichment) and persist both under GAIA‑X–aligned decentralised storage with optional ledger anchoring.

No. The data lives in decentralised storage and is referenced by verifiable credentials. That keeps wallets light and policies enforceable across systems and data spaces.

When executed under recognised frameworks (eIDAS QES/QSeal or equivalent), digital signatures can have the same legal effect as handwritten signatures. TradeVeris integrates QTSP partners and audit trails to meet these standards. (This is informational, not legal advice.)

Gaia‑X does not itself confer legal enforceability. Compliance depends on applicable laws (e.g., METLR, national legislation) and system reliability. Gaia‑X can host METLR‑compliant workflows, but enforceability requires meeting statutory requirements. (This is informational, not legal advice.)

Trusted Data Sharing

No. You can run entirely on Gaia‑X–aligned federated services or your own cloud. DLT anchoring is optional for tamper‑evidence of logs or hashes.

Only when a policy says so – and then under scoped tokens (time, purpose, subset, watermark). You can also enable in‑place analytics patterns to avoid bulk transfer.

Yes. We integrate with your object stores or federated nodes. The platform references data via pointers; credentials and policies govern access.

No. Trade is a key vertical, but the same controls fit legal disclosures, regulatory data, insurance packs, finance/invoicing, and eGovernment exchanges.

Every request, decision, and delivery is logged with identity, role, purpose, timestamp, policy ID, dataset pointer, and (optionally) a hash anchor. You can export packaged evidence for audits.

We are wallet‑agnostic. vLEI works now; LPID/EUDI as wallets roll out. DC‑API helps portals request verifiable presentations without implementing wallet protocols.

Contact us