OdyCust/ GUIDE
УКР

Public invoices and transactions

Read a published document and understand what it establishes.

Open a direct link

The separate OdyCust Share viewer shows one invoice at /invoice/<id> or transaction at /tx/<id>. The document must have been explicitly published. A private record UUID or hash does not disclose it to others.

Check network, full address, asset, exact amount, hash and capture time. You can change language and print the document. Reading a published document requires no console sign-in.

OdyCust Share remains a static site and reads published documents from public routes of the same backend that serves the console, without sending account credentials. A supported network/hash link changes to its canonical document address only after the API returns a valid publication.

The public contract supports Sepolia, but does not yet support publications for Hoodi, Bitcoin Testnet3/Testnet4 or Shasta. Support for those networks in wallets or transfers does not extend Share. Changing the network name or substituting a different hash cannot make a document eligible for publication.

What is disclosed

Publication contains a frozen, reduced snapshot. Private counterparty names, internal relationships, member data and signing material are excluded. Displayed addresses and amounts are available to anyone opening the published document.

The snapshot does not refresh after invoice cancellation or changed network history. It does not establish current payment or finality. A public custody transaction can remain unknown even after accounting settlement.

Publishing and revoking

Backend publication requires a human with explicit publication and source-read rights plus step-up verification. Publication controls are not implemented in the current console; obtaining a link depends on a configured integration.

Publication expiry is bounded to 90 days. One immutable publication is retained per document. Revocation is terminal; downloaded or printed copies can remain with recipients.

A link will not open

The static page can load even when a document is unavailable. An unpublished, expired, revoked or ambiguous document, or a document whose public reading is disabled for its organization or installation, returns the same 404 from the public API. This does not reveal a private source or organization settings.

Before reading a published document, Share checks the service connection. A failed check shows Service temporarily unavailable in place of the document. It also hides a document that was already open. Choose Try again or keep the tab visible: repeated checks wait 5, 10, 20 and then 30 seconds. Checks pause in hidden tabs; returning to the tab or restoring the network resumes the check.

After the connection recovers, Share reads the publication again. If it has been revoked or expired, the document will not reappear: the page shows 404. A successful connection check does not update the publication’s frozen contents or establish payment or finality.

If the API process responds but the document read itself is unavailable, the page shows 503 with an option to retry the read. This differs from the connection-failure screen and from 404. Do not replace the document with blockchain-search data.

Related reading

OdyCust · User documentation2026-10-13

Search documentation

Search stays within this guide. It does not request console data.