Questions about Proof of Travel.

Proof of Travel (PoT) is a neutral verification protocol that produces independent, deterministic, cryptographically anchored proofs of travel lifecycle events — issuance, departure, arrival, reconciliation, refund. It is not a booking system, not a settlement system, and not a replacement for IATA or ARC reconciliation.

PoT is operated by Travel Information Network (TIN). The protocol itself is designed to be neutral and independently verifiable, and the optional AERO incentive layer is intended to support broader decentralisation over time.

Only a hash and a small set of structural metadata. No PNRs, ticket numbers, names, dates of birth, or itineraries appear on the public ledger. The protocol is GDPR-aligned by design and uses data minimisation as a core principle.

A consumer takes the public anchor (transaction hash and block reference) and a deterministic re-derivation of the inputs, recomputes the commitment hash, and confirms it matches what is on chain. There is no trusted third party in the verification path.

No proof is generated. Conservatism is a deliberate design choice — silence is preferred to a false positive. The absence of a proof is itself a useful operational signal in audit and dispute contexts.

Three integration paths are common: a read-only operational signal feed, a reference API for retrieving proofs, and an optional embedded verifier widget. None of these modify your existing booking, ticketing, or settlement systems.

The protocol is designed for GDPR alignment. Personal data is never written to the public ledger, and the off-chain components follow data minimisation and purpose-limitation principles. Detailed compliance documentation is available on request.

TIN is implementing ISO/IEC 27001 in stages, with formal certification scoped to the operational components of the verification protocol. Status updates are provided on request to enterprise integrators and auditors.

AERO is an optional incentive and decentralisation layer that sits alongside — but is not part of — the core verification protocol. The verification protocol is fully functional without AERO. AERO exists to support broader decentralisation goals over time.

Polygon — a public, EVM-compatible network. We chose Polygon for low transaction cost and high throughput while remaining tooling-compatible with the broader Ethereum ecosystem. The choice of public infrastructure is deliberate: it ensures anchors are independently verifiable without requiring trust in the protocol operator.

Yes. Issuance, departure, and reconciliation proofs are designed to be admissible inputs to chargeback defence workflows. We can introduce you to acquirers and insurers already familiar with the proof format.

Write to info@proofoftravel.io with a brief note about your role and use case. We'll respond with the relevant whitepaper, integration guide, and proposed next steps.