> 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/payment-instructions.md).
# Payment Instructions
Every transaction on Silo generates a Payment Instruction. This is an encrypted record that contains the complete details of the transaction and serves as Silo's internal audit trail.
***
#### **What a Payment Instruction Contains**
Each Payment Instruction records the full context of a transaction: sender identity, receiver identity, the amount sent, the amount received, the asset and chain used by the sender, the asset and chain delivered to the receiver, all wallet addresses involved, routing details (swap paths, bridge used), ZK proof references, compliance check results, and timestamps for each stage of the transaction.
This is the complete picture of the transaction. Nothing is omitted.
***
#### **How Payment Instructions Are Stored**
Payment Instructions are built incrementally throughout the payment lifecycle. As each step of the transaction is processed: deposit, routing, compliance checks, withdrawal. The relevant data is captured and stored securely in Silo's internal database. Once the receiver has completed their withdrawal, the full Payment Instruction is finalized, encrypted using SEAL, and uploaded to Walrus (Sui's decentralized storage layer) via a background process.
SEAL handles the encryption, ensuring the contents are not readable without authorized access. Walrus provides durable, decentralized storage so that records are not dependent on a single server or database. The combination means that Payment Instructions are tamper-resistant, durable, and encrypted at rest. They cannot be read by public blockchain observers, by other Silo users, or by anyone without authorized access through Silo's backend.
***
#### **Who Can Access Payment Instructions**
Payment Instructions are accessible only to Silo's backend under defined access controls. Users do not see Payment Instructions directly. Instead, they receive redacted receipts (see Redacted Receipts) that contain a subset of the transaction details appropriate for each party.
Access to the full Payment Instruction is reserved for specific operational needs: dispute resolution between parties, regulatory or audit requests under applicable legal processes, and internal compliance review.
The access control framework is designed to balance two requirements. Users need privacy from the public and from each other. Regulators and auditors need the ability to verify that transactions are legitimate and compliant. Payment Instructions satisfy both by keeping the full record encrypted and access-controlled while giving users redacted, non-doxxing receipts.
---
# 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/payment-instructions.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.