Shareable proof

A readable link to share an incident, not your data.

This example shows how a CashFlowCanary incident can be shared with a merchant, agency or technical team in read-only mode, with filtered proof and controlled lifetime.

Masked link example

The real link is generated inside the client area for a specific incident. Here, the token is deliberately replaced by a non-usable demonstration marker.

Format

https://cashflowcanary.com/incidents/share/[masked-token]

Visible content

Verdict, affected step, likely cause, filtered proof, useful timeline and resolution status.

Excluded content

End-customer identity, payment credentials, address, customer email, detailed cart contents, cookies, tokens and full payloads.

Control

Expiration and revocation from the cockpit, non-indexable page and no-cache response.

Client reading

The link aligns teams on the next action.

Sharing avoids confusing screenshots: everyone sees the same incident, priority and resolution state, without access to the full cockpit.

  • Readable proof for a merchant
  • Actionable diagnosis for an agency
  • Access limited to the shared incident
Abstract CashFlowCanary public proof link example

Why a public link exists

When an incident affects checkout, the team often needs to share proof with a decision-maker, merchant or external developer. The public link avoids creating an account for every reader and limits access to the single incident.

What the reader can do

  • Read the verdict and priority.
  • Understand the affected funnel step.
  • See the filtered signals behind the alert.
  • Follow resolution when the journey turns green again.

What the reader cannot do

  • Modify a site, plan, payment or configuration.
  • Access the full cockpit or other incidents.
  • See end-customer data, sensitive configuration or complete raw traces.
  • Use the link after expiration or revocation.