> For the complete documentation index, see [llms.txt](https://docs.silopay.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silopay.io/compliance/redacted-receipts.md).
# Redacted Receipts
Every Silo transaction generates a redacted receipt for both the sender and the receiver. These receipts confirm that a payment occurred and provide each party with enough information to verify the transaction, without exposing the other party's wallet address, transaction hash, or routing details.
***
#### **What the Sender Sees**
The sender's receipt shows: the amount they sent, the receiver's username, their own outbound transaction hash (proof that funds left their wallet), and the timestamp of the transaction.
The sender does not see the receiver's wallet address, the receiver's withdrawal transaction hash, or any details about how the payment was routed or delivered on the receiver's side.
***
#### **What the Receiver Sees**
The receiver's receipt shows: the amount they received, the sender's username, their own inbound transaction hash (proof that funds arrived at their wallet), and the timestamp of the transaction.
The receiver does not see the sender's wallet address, the sender's deposit transaction hash, or any details about which asset or chain the sender paid from.
***
#### **What Neither Party Sees**
Neither the sender nor the receiver sees the other's wallet address or the other's on-chain transaction hash. The only shared information is the username, the amount, and the timestamp. This means a receipt can be used to confirm that a payment took place: for record-keeping, expense tracking, or dispute purposes, without doxxing either party's on-chain identity.
***
#### **Relationship to Payment Instructions**
Redacted receipts and Payment Instructions draw from the same underlying transaction data captured in Silo's database throughout the payment lifecycle. Receipts are generated and delivered to both parties as soon as the relevant transaction data is available, they do not depend on the Payment Instruction being finalized or uploaded to Walrus. The redacted receipt is a filtered view of the transaction record, tailored to show each party only the information relevant to them. The full Payment Instruction, once finalized and stored on Walrus, contains the complete unredacted record and remains encrypted and access-controlled on Silo's backend.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.silopay.io/compliance/redacted-receipts.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.