> This page is for version v2 (default).
> For other versions, use one of these documentation indexes:
> - v2 (default): https://docs.paid.ai/v-2/llms.txt
> - v1: https://docs.paid.ai/v-1/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.paid.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.paid.ai/_mcp/server.

# Value receipts

> Customer-facing documents that showcase the measurable value your AI agent delivers

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](/documentation/getting-started/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.

## Prerequisites

* [Signals](/documentation/getting-started/first-signals) flowing for the customer and product you want to report on.
* [Delivered value](/documentation/getting-started/delivered-value) configured for the relevant product attributes.
* At least one customer with signal data in the receipt date range.
* For private or embedded receipts, [embed authentication](/documentation/value-receipts/authentication-and-embedding) configured before sharing with customers.

## Lifecycle

A value receipt is fixed from the moment you create it. Its data, its design and the organization's branding are captured at creation and do not change afterwards. To show a customer newer numbers, create a new receipt.

### 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:

```
https://app.paid.ai/public/value-receipts/{token}
```

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](/documentation/value-receipts/authentication-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](/documentation/value-receipts/authentication-and-embedding).