Zama is HTTPS for onchain finance: addresses stay public, amounts get encrypted.
Verifiable
Onchain settlement, fully auditable.
Encrypted
Amounts and references encrypted at the token level.
Compliant
Auditors, sanctions screening, and ERP retain access by role.
Composable
Drops into your existing stack.
Cross-border vendor settlement, marketplace payouts, treasury and intercompany flows, trade and supply-chain finance, four flows, one rail.
The Zama Protocol is in production on Ethereum mainnet, asset-agnostic and chain-agnostic, ready to be implemented with USDC, EURC, regulated bank stablecoins, and the custody, treasury, and ERP stack institutions already run.
Vendor payments and balances are encrypted in the corporate AP system, PSP, or treasury platform before they reach the chain. Plaintext never leaves the institution's environment.

The blockchain processes settlement, FX, intercompany, and reporting without decrypting any of it. Sender and receiver addresses remain public; amounts, balances, and commercial references stay encrypted.
You decide who sees what, role by role — through the Zama Protocol's ACL and selective disclosure. Auditors, sanctions-screening providers, beneficial-ownership systems, ERP, and treasury workstations retain authorized access; the compliance stack you already run keeps running.

From confidential payroll to institutional trading — real deployments, on Ethereum mainnet, today.
Confidential corporate payments let companies settle and invoice onchain without making transaction amounts public. With the Zama Protocol, amounts, balances, and commercial references are encrypted at the token level with Fully Homomorphic Encryption (FHE), while settlement stays onchain and fully auditable. Sender and receiver addresses remain public.
Four flows, one rail: cross-border vendor settlement, marketplace and platform payouts, treasury and intercompany flows, and trade and supply-chain finance. In each case, the commercial terms behind the transaction, such as supplier pricing, take rates, or FX strategy, stay encrypted instead of being readable by anyone with a block explorer.
Vendor payments and balances are encrypted client-side, in the corporate AP system, PSP, or treasury platform, before they reach the chain. The blockchain then processes settlement, FX, intercompany flows, and reporting on encrypted data, without decrypting any of it. Data is encrypted before it leaves the institution's environment.
Yes. Through the Zama Protocol's Access Control List (ACL) and selective disclosure, the company decides who sees what, role by role. Auditors, sanctions-screening providers, beneficial-ownership systems, ERP, and treasury workstations retain authorized access, so the compliance stack already in place keeps running.
The Zama Protocol is in production on Ethereum mainnet, asset-agnostic and chain-agnostic. It is ready to be implemented with USDC, EURC, and regulated bank stablecoins, and integrates with the custody, treasury, and ERP stack institutions already run, with no new chain to adopt. GSR and Zama completed the first confidential OTC trade on Ethereum with it.
Contact