> 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/resources/faq.md).

# FAQ

<details>

<summary>Is Silo a wallet?</summary>

No. Silo is a payments platform. Users connect their existing wallets to Silo and maintain full control of their funds. Silo does not store, hold, or manage private keys.

</details>

<details>

<summary>Is Silo custodial?</summary>

No. Silo is non-custodial. Withdrawals require the receiver's wallet signature. Silo cannot move funds on a user's behalf. Silo's role is to facilitate payment routing and privacy — not to take custody of user funds.

</details>

<details>

<summary>Do I need a new wallet to use Silo?</summary>

No. Silo works with whatever wallet the user already has on any supported chain.

</details>

<details>

<summary>What happens if I send to the wrong username?</summary>

Silo routes payments based on the username entered by the sender. Users should verify the recipient's username before confirming a transaction. Because Silo is non-custodial and transactions settle on-chain, payments sent to the wrong username cannot be reversed by Silo.

</details>

<details>

<summary>Can the sender see my wallet address?</summary>

No. The sender only sees your username. Your wallet address, payout chain, preferred asset, and routing details are never visible to the sender.

</details>

<details>

<summary>Can anyone see who paid who on-chain?</summary>

No. Silo uses shared vaults and zero-knowledge proofs to break the on-chain link between the sender's deposit and the receiver's withdrawal. Public blockchain observers cannot determine who paid who.

</details>

<details>

<summary>Is Silo completely anonymous?</summary>

No. Silo provides privacy from the public, not anonymity from Silo itself. Silo maintains an encrypted audit trail (Payment Instruction) behind every transaction that records the full details of the payment. This record supports dispute resolution, regulatory compliance, and audit requirements. Users receive redacted receipts that confirm the transaction without exposing the other party's wallet details.

</details>

<details>

<summary>How is Silo different from Tornado Cash?</summary>

Tornado Cash is a permissionless mixing protocol with no compliance controls, no receipts, no username system, and no payments UX. Silo is a payments platform with privacy built in. Silo provides username-based payments, cross-chain delivery, redacted receipts, compliance screening, and an encrypted audit trail — none of which Tornado Cash offers. For a full comparison, see Comparison to Privacy Protocols.

</details>

<details>

<summary>Does Silo require KYC?</summary>

Not at the Personal tier. Users can sign up with just an email or phone number and transact within defined limits. Higher tiers (Plus and Business) require identity verification and unlock lower fees, higher limits, and additional capabilities like commerce and payroll. See Three-Tier System for details.

</details>

<details>

<summary>What assets does Silo support?</summary>

USDC is currently the primary supported asset. Additional asset support is expanding. See Supported Chains & Assets for the latest coverage.

</details>

<details>

<summary>What chains does Silo support?</summary>

Silo is currently live on Ethereum, Sui, and Solana. See Supported Chains & Assets for updates.

</details>

<details>

<summary>What are the fees?</summary>

Silo charges a single per-transaction privacy fee: 30 bps (Personal), 25 bps (Plus), or 20 bps (Business). Network gas and swap fees are passed through at cost with no Silo markup. Cross-chain USDC transfers via CCTP carry $0 Silo fee. See Fee Structure for full details.

</details>

<details>

<summary>Who pays the fee?</summary>

It depends on the payment context. In peer-to-peer payments, the receiver absorbs the fee by default (with an optional gross-up toggle for the sender). In commerce, the merchant always pays. In payroll, the employer always pays. See Three-Tier System for the full breakdown.

</details>

<details>

<summary>What if I lose access to my wallet?</summary>

Silo does not custody funds or manage private keys. If a user loses access to their wallet, Silo cannot recover the funds. Wallet recovery depends on the user's wallet provider and their own backup procedures.

</details>

<details>

<summary>Can Silo freeze my funds?</summary>

No. Once a payment is successfully deposited into the shared vault, Silo has no control over the flow of funds. Withdrawals are governed by the smart contract and can only be triggered by the receiver's wallet signature. Silo cannot seize, redirect, or freeze funds that are in the vault. Silo's compliance lever is gating — it can refuse to facilitate a payment that fails policy checks (sanctions screening, KYT) before funds enter the vault. But once the transaction is successful, Silo has no ability to intervene.

</details>

<details>

<summary>Is Silo available in my country?</summary>

Silo does not serve sanctioned persons, addresses, or jurisdictions. Availability by jurisdiction will be detailed as the platform's regulatory posture is finalized with legal counsel.

</details>

<br>


---

# 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/resources/faq.md?ask=<question>&goal=<endgoal>
```

`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.
