> 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/three-tier-system.md).
# Three-Tier System
Silo uses a three-tier account system that determines transaction limits and what types of payments a user can participate in. The tiers are Personal, Plus, and Business. Each tier is additive: every higher tier includes everything the previous tier can do, plus new capabilities.
The core design principle is that the sender never needs to think about tiers or payment types. They type a username and an amount, and Silo handles everything else. Tier logic and payment type enforcement happen in the background.
***
### **Tier 1 — Personal - 30 BPS**
Personal accounts are for everyday users making payments to friends, family, or other individuals. No identity verification is required. Users sign up with an email address or phone number only.
Personal accounts can send and receive peer-to-peer payments with other Personal and Plus users. They cannot buy from merchants (Commerce accounts) or receive payroll payments. If a Personal user tries to pay a merchant, the system prompts them to upgrade rather than showing an error.
Transaction limits are $2,000 per day and $10,000 per month. Transaction screening (KYT) is applied to all payments.
Note: Transaction limits are illustrative and subject to change pending legal review.
***
### **Tier 2 — Plus - 25 BPS**
Plus accounts are for users who transact frequently and want lower fees and higher limits. KYC (identity verification) is required. Users verify with an ID and selfie through Silo's verification partner.
Plus accounts can do everything Personal accounts can do, and they also unlock two additional capabilities: buying from merchants (sending payments to Commerce accounts) and receiving payroll (receiving payments from Payroll accounts). Plus accounts cannot become a merchant or send payroll, those require Business tier.
Transaction limits are $50,000 per day and $250,000 per month.
Note: Transaction limits are illustrative and subject to change pending legal review.
***
### **Tier 3 — Business - 20 BPS**
Business accounts are for companies and operators who need to accept customer payments or send payroll. Full KYB (Know Your Business) verification is required, including business registration and beneficial ownership documentation.
Business accounts can do everything Plus accounts can do, plus two additional capabilities depending on their sub-type:
Commerce sub-type: for businesses accepting payments from customers. Online stores, marketplace sellers, service providers, and anyone invoicing clients. Only Plus and Business users can send payments to Commerce accounts, Personal users cannot.
Payroll sub-type: for businesses paying employees or contractors. Only Plus and Business users can receive payroll payments, Personal users cannot.
The sub-type (Commerce or Payroll) is selected during onboarding and locked to the account. Businesses that need both capabilities can request a review to add a second sub-account.
Transaction limits are $500,000 per day and $5,000,000 per month, with custom limits available.
Note: Transaction limits are illustrative and subject to change pending legal review.
***
#### **Tier Gating**
Tier restrictions are enforced at the routing layer, not the user interface. A Personal user cannot send to a Commerce or Payroll account even if they know the username. The system checks the sender's tier against the receiver's account type before the payment is processed. If the interaction is not permitted, the user sees a prompt to upgrade.
This creates a natural upgrade path. Users who want to buy from merchants or receive payroll upgrade to Plus. Users who want to accept payments as a merchant or run payroll upgrade to Business. Each step requires more verification and unlocks more capability.
For full details on fee rates, fee responsibility, and swap costs, see [Fee Structure](/fees/fee-structure.md).
---
# 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/three-tier-system.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.