> For the complete documentation index, see [llms.txt](https://zkpay-1.gitbook.io/zkp-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zkpay-1.gitbook.io/zkp-whitepaper/overview/technology-behind-zkpay.md).

# Technology Behind ZKPay

ZKPay’s technological foundation combines **zero-knowledge proofs**, **smart contract automation**, and **multi-layer financial bridging** to achieve privacy, compliance, and scalability.

1. **Zero-Knowledge Payroll Proofs (zkPayroll Proofs):**\
   Each payroll transaction batch is encoded into a proof that validates payment fairness, timing, and total consistency — without exposing individual employee details. This ensures transparency for auditors while preserving privacy for recipients.
2. **X402 Bridge Layer:**\
   A high-speed payment bridge that converts fiat inflows into stablecoin outflows in seconds, enabling compliant cross-border settlements. This layer supports integration with multiple regulated on/off-ramp providers for smooth liquidity flow between banks and blockchain.
3. **zk-KYC Compliance Modules:**\
   For jurisdictions requiring auditability, ZKPay offers optional zero-knowledge identity verification plugins. These allow regulators or enterprises to confirm compliance status **without accessing user data**.
4. **HR Integration SDK:**\
   A developer-friendly toolkit that embeds ZKPay’s infrastructure directly into existing HR software, payroll management tools, or DAO payment dashboards. The SDK supports APIs for automated payouts, zkProof verification, and multi-chain support.
5. **Multi-Chain Deployment Architecture:**\
   ZKPay operates as an **EVM-compatible protocol** initially deployed on Ethereum Layer 2 networks for low fees and scalability, with cross-chain expansion to Base, Polygon, and zkSync.
6. **Encryption & Security Layer:**\
   All transactional metadata — including identities, salary amounts, and timestamps — is encrypted using **zk-SNARK-based privacy layers**, ensuring that even network validators cannot correlate payments to individuals.