Arcane in one line: confidential transaction infrastructure with a
governed path for authorized review.
Why Arcane
Public blockchains provide shared settlement and verifiable transaction history, but their transparency can expose balances, payment amounts, and patterns of financial activity. Financial organizations need a different operating model. Sensitive transaction details should remain confidential during normal use, while approved compliance, audit, support, and investigation workflows must still be able to access the specific evidence they are authorized to review. Arcane is designed around this separation: privacy for the transaction path and governed visibility for the review path.The Arcane product family
Privacy Layer
Confidential transaction infrastructure for private payments, balances,
and financial activity inside client products.
Compliance Platform
Governed access to private transaction evidence through scoped review,
reporting, and administrative controls.
What Arcane adds to a client product
| Requirement | Arcane capability |
|---|---|
| Transaction confidentiality | Private transfers, balances, and protected financial activity. |
| Controlled visibility | Access to specific evidence based on purpose, scope, role, and approval. |
| Auditability | Review cases, reports, and activity records for authorized workflows. |
| Product integration | Infrastructure and integration tools that connect to an existing client application. |
Designed for financial workflows
Arcane can support products and operations such as:- wallet and stablecoin payments;
- payroll, payouts, and partner distributions;
- treasury and corporate payment operations;
- confidential tokens and digital-asset workflows;
- financial actions embedded in client applications.
Explore the products
How the Privacy Layer works
Follow the private transaction path and understand the client integration
boundary.
How the Compliance Platform works
Follow the controlled disclosure path from request to approved review and
reporting.