Public invoices and transactions
Read a published document and understand what it establishes.
Open a direct link
The separate Custody 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.
The static page reads the dedicated public API directly, without sending account credentials. A supported network/hash link changes to its canonical document address only after the API returns a valid 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 returns 404 from the public API, and the viewer shows that it is missing without revealing whether a private source exists. API 503 or a failed read shows unavailability; try later. Do not replace the document with blockchain-search data.