Read receipts

# Read receipts

Canonical: https://docs.flowrelay.app/operate/receipts/
Markdown: https://docs.flowrelay.app/operate/receipts.md

A receipt is FlowRelay's durable proof artifact for an accepted event and its Shopify Flow handoff attempt.

## How to use this page
Use this order when you are checking what happened to an event.
1. Open Event history and choose the event you want to inspect.
2. Check the receipt outcome, timestamp, endpoint snapshot, authentication result, validation result, and retention state.
3. Read the handoff status to see whether FlowRelay handed the trigger to Shopify Flow.
4. Use the receipt's recovery code and replay availability to decide whether to wait, fix setup, replay, or share diagnostics.
5. When an agent is helping, have it use the same safe receipt facts instead of asking for raw payloads or headers.

## How to read a receipt
Start with the outcome, then read the safe facts that explain what FlowRelay can prove.


- Receipt field: Outcome; Meaning: The current FlowRelay boundary result, such as Delivered, failed, no workflow, rejected, or duplicate suppressed.
- Receipt field: Endpoint snapshot; Meaning: The endpoint configuration FlowRelay used for the original event.
- Receipt field: Auth and validation; Meaning: Whether the request passed authentication, required paths, mapping, and event type checks.
- Receipt field: Handoff status; Meaning: Whether FlowRelay handed the trigger to Shopify Flow.
- Receipt field: Retention and replay; Meaning: Whether retained event material is still available for a deliberate replay.

## Delivered boundary
Delivered means FlowRelay handed the trigger to Shopify Flow. It does not mean Shopify Flow branches matched, app calls ran, fulfillment changed, emails sent, or later systems completed.


## Use receipts with agents
Authorized agents use receipt facts and diagnostics rather than asking humans for raw payloads, full headers, secrets, tokens, or private screenshots.


## Handoff Boundary
Delivered means FlowRelay handed the trigger to Shopify Flow. It does not mean downstream Shopify Flow branches, app calls, fulfillment changes, emails, or later systems completed.

## Related
- [Event history](https://docs.flowrelay.app/operate/event-history.md)
- [Replay an event](https://docs.flowrelay.app/recover/replay.md)
- [Share diagnostics](https://docs.flowrelay.app/recover/diagnostics.md)

## Safety Boundary
Do not include raw payloads, endpoint secrets, auth headers, HMAC values, Shopify tokens, Shopify sessions, database URLs, customer data, merchant incidents, or copied private logs in public examples.