Value receipts
Value receipts are shareable, customer-facing documents that summarize the real-world impact your AI agent delivered over a specific time period — hours saved, meetings booked, costs avoided, and more. They answer the question: what did I actually get?
Each value receipt pulls from the delivered value you’ve already configured, aggregates it for a customer and date range, and produces a polished breakdown they can view in a browser or see embedded directly in your product.
Before creating value receipts, make sure you’re sending signals and have delivered value configured for your product attributes. Value receipts aggregate this data — without it, there’s nothing to show.
Lifecycle
A value receipt moves through a simple set of states:
Draft
Every value receipt starts as a draft. You can refresh it at any time to pull in the latest data. Drafts are useful while a time period is still in progress and numbers are still changing.
Sealed
When you’re ready to finalize a value receipt, you seal it. A sealed receipt is locked — it can no longer be refreshed or updated. This preserves a point-in-time snapshot of the delivered value, which is what you’d typically share with a customer at the end of a reporting period.
Archived
If a value receipt is no longer relevant, you can archive it. Archived receipts are hidden from list views by default but are not deleted — they can be restored at any time by unarchiving.
Visibility: published vs. private
Every value receipt has a share URL that looks like:
What happens when someone visits that URL depends on whether the receipt is published or private.
Published
A published value receipt is fully public — anyone with the link can view it without any authentication. This is useful for quick sharing where access control isn’t a concern.
You can optionally set an expiry date when publishing. After the expiry passes, the link stops working and the receipt automatically reverts to private.
Private (default)
By default, value receipts are private. Accessing a private receipt requires a signed token that your backend generates. This means you control exactly who can see each receipt.
When someone visits a private value receipt link without a valid token, Paid redirects them to a login URL that you configure. After your app authenticates the viewer, it redirects them back to the value receipt with a token attached. The viewer never needs to create a Paid account — authentication is entirely handled by your system.
Read more about private access, login redirects, and embedding.
Embedding
Value receipts can be embedded directly in your own application. Customers see their value breakdown without leaving your product — no context switching, no external links. Authentication is handled securely in the background, so private receipts stay private even when embedded.
For implementation details on embedding and authentication, see authentication and embedding.
