Products
Hinkal consists of seven products built on a single privacy protocol. Each is a different surface over the same private balance.
Hinkal App
Send, swap, and receive privately from the wallet you already use - on Ethereum, Solana, TRON, Robinhood Chain, and other major networks.
For: individuals and small teams paying from their own wallet
Manage public and private balances in one place
Send privately, straight from your wallet or private balance
Swap tokens privately, same-chain and cross-chain
Receive through your private deposit address, with automatic KYT screening built in - no new wallet, seed phrase, or custodian
Quick Actions: bridge and send in one go, pay multiple recipients at once, and fund wallets with randomized delivery timing
Hinkal Prime
Enterprise treasury and payouts on private balances, with roles, approvals, and compliance controls built in.
For: enterprises and organizations running treasury and payouts as a team
Private and public balances in a single view, with shielding and unshielding between them
Single payouts and batch payouts from a CSV validated against the organization's balances before anything is signed
Two roles and an approval queue - members prepare payouts, owners review, approve, or reject
Per-recipient delivery, either private or direct to a public address - recipients need no Hinkal account
Transaction history and analytics across the whole organization
Hinkal Wallet
A self-custodial, multi-chain wallet with public and private accounts in a single interface.
For: individuals who want one self-custodial wallet for public and private activity
A public account that works as a standard wallet - buy, swap, bridge, send, and receive
A private account to move assets into, with private-to-private transfers where sender, recipient, and amount stay private
Send to public addresses from the private account - the sender stays private
Swaps and cross-chain transactions inside the private account
Connects to dApps the same way standard wallets do
Hinkal API
A REST API whose server runs inside a secure enclave, letting developers integrate Hinkal's privacy layer directly into their own backend.
For: enterprise platforms driving privacy from their own infrastructure
Private deposits, withdrawals, transfers, and swaps callable from any backend
Enclave-attested execution, so the server itself can be verified to run the expected code
The same privacy primitives as the rest of the protocol, exposed as REST endpoints
No frontend SDK or wallet UI required
Hinkal SDK
A developer-first toolkit that lets PSPs, payment processors, neobanks, OTC desks, and enterprises embed private payments directly into their existing infrastructure.
For: enterprise developers embedding private payments in their own product
Private balances and transactions inside your application
Private sends, swaps, and cross-chain flows
User activity that stays private, with no wallet history exposed on-chain
Selective disclosure for compliance, reporting, or audit needs
No changes to custody, compliance processes, or routing logic
Hinkal WaaS
A Wallet-as-a-Service REST API that lets companies create and manage their users' wallets and execute private on-chain transactions without integrating the SDK.
For: enterprises managing wallets for their users, in any language
Private deposits, withdrawals, and transfers from any language or stack
An organization model that mirrors how companies operate - admins create users, assign wallets, set policies, and can act on their behalf
Server-side wallets whose private keys are generated, stored, and used only inside a secure enclave - never seen by the API server, the database, or Hinkal engineers
Every request signed with an Ed25519 X-Stamp and a unique nonce, so calls can't be forged or replayed
Hinkal MCP
A Model Context Protocol server that lets AI agents move funds between public and private balances through natural-language requests.
For: individuals and developers letting AI agents move funds on their behalf
Private deposits, withdrawals, and transfers driven by an agent instead of manual calls
A custodial wallet created server-side on first use - the agent acts for the user while their machine holds only an access key
The same primitives as the rest of the protocol, exposed as tools any MCP-compatible assistant can call
Works with Claude Desktop, Claude Code, or any custom MCP host - no need for the agent to understand proofs, UTXOs, or relaying
Last updated

