# Introduction

### What is PolyPay?

PolyPay is a privacy-preserving payroll platform built on Horizen and Base. It enables organizations, DAOs, and global teams to run payroll privately across multiple chains.

### The Problem

Current on-chain payment solutions expose sensitive information publicly:

* Employee salaries are visible to everyone
* Payment recipients can be tracked
* Multisig approvers are publicly identified

This lack of privacy prevents businesses from adopting crypto payroll.

### Our Solution

PolyPay uses **zero-knowledge proofs** and **multi-chain deployment** (Horizen and Base) to provide:

* **Private Payments**: Salary amounts and recipients stay confidential
* **Private Multisig**: Team approvals without exposing signer identities
* **Flexible Payment Logic**: Single and batch transfers
* **Gasless USDC Deposit (x402)**: Fund a multisig on Base with one signature, no ETH required — works for human users and AI agents via the [x402 protocol](https://www.x402.org/)

### Who Is It For?

* Crypto-native startups and SMBs
* DAOs managing contributor payments
* Traditional businesses entering crypto
* Teams using Safe or Squads who want privacy upgrades

### Supported Networks

* **Horizen** (mainnet & testnet)
* **Base** (mainnet & Sepolia)

### Roadmap

* Additional chain integrations
* Fiat on/off-ramp integration
* Escrow and milestone-based payments
* Recurring transfers
* Expand x402 to additional networks and tokens beyond USDC on Base


---

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

```
GET https://q3labs.gitbook.io/polypay-docs/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.