# Why ZKPay?

Current payroll systems are broken for a globalized, decentralized workforce. They expose personal data, rely on outdated SWIFT rails, and involve numerous intermediaries that delay payments and increase costs. Meanwhile, most blockchain-based payment systems lack the privacy, compliance, and enterprise-grade integration required for real-world adoption.

ZKPay was built to fix this — **not by replacing payroll, but by evolving it.**

Here’s why ZKPay is needed:

* **Data Exposure:** Traditional payroll exposes personal salaries and tax records to third parties. ZKPay encrypts it end-to-end.
* **Cross-Border Complexity:** International payments are slow, expensive, and heavily regulated. ZKPay automates conversions through its **X402 Bridge Layer** for seamless fiat-to-crypto salary distribution.
* **Lack of Auditability in Crypto Payroll:** DAOs and Web3 firms struggle to prove fair payments without revealing addresses. ZKPay’s **zkPayroll Proofs** allow verifiable fairness with zero exposure.
* **Fragmented Compliance Requirements:** Each jurisdiction has unique payroll regulations. ZKPay’s **modular zk-KYC plugins** let organizations enable compliance features on demand, keeping the base layer fully private.
* **Integration Friction:** Enterprises can adopt ZKPay instantly using the **ZKPay SDK**, which plugs directly into major HR systems like Deel, Remote, or BambooHR.

ZKPay represents **a pragmatic bridge** between old finance and new cryptography — bringing privacy, efficiency, and compliance to the world’s oldest transaction: paying people for their work.


---

# 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://zkpay-1.gitbook.io/zkp-whitepaper/overview/why-zkpay.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.