Turnkey is the infrastructure a lot of fintech and crypto teams build on so their users get a wallet without ever touching a seed phrase. It creates the keys, guards them inside hardware-isolated enclaves, checks the user's identity, enforces policy, and signs - all behind a single sign-in. 

Turnkey solves signing. Confidentiality is a different problem. Public blockchains work in the open by default: balances, counterparties, and transfer amounts are readable by anyone with a block explorer. For a payments app, a neobank, or any business moving real volume, that visibility isn't a detail to manage later. It's structural: users' counterparties, cash positions, and payment history sit in permanent public view.

Hinkal fixes that, and if you already build on Turnkey, turning it on is a configuration. No new wallet, no custody handoff, no rebuild of the key layer. You add privacy to the wallet infrastructure you already chose.

The integration touches one thing: the signature

Hinkal needs a signature to work, and nothing else from the wallet. A Turnkey wallet already produces signatures - that is its core job - so Hinkal plugs in exactly where a signature already exists and asks for nothing deeper. Everything below the signature stays as it was: Turnkey still creates the keys, guards them, and signs, the private key never leaves the enclave, and Hinkal never sees it. That is why enabling it is a configuration change rather than a rebuild - you are not touching the key layer, the custody model, or the wallet your users already have.

What happens when a user sends privately

To the user it is one tap. Underneath:

1. The app builds the operation with the Hinkal SDK - a transfer, payment, swap, deposit, or withdrawal - and produces the payload that needs the user's authorization.
2. The Turnkey wallet signs that payload inside its enclave, the way it signs anything else.
3. Hinkal uses the signature to access the user's shielded account, then a relayer submits the transaction on-chain. The user's public address never appears as the sender, so the link between the wallet and the activity is never written to the chain.

The only thing crossing between the two systems is a signature - exactly what Turnkey was built to produce.

Confidential, not unaccountable

Every private transfer carries a zero-knowledge proof that it is valid - the sender owns the funds, the funds have not been spent before, and nothing was created out of thin air - without revealing the sender, the recipient, or the amount. Validators verify the math without seeing the inputs. Confidential to the market, provably correct to the network, in one operation.

What the same wallet can now do

Once the signer is wired in, every action the wallet already performs gets a private version: balances, deposits, withdrawals, transfers, payments, swaps.

Selective disclosure

Privacy here means confidentiality between counterparties, not hiding from regulators. Through viewing keys, a user can open specific activity to an auditor, a regulator, or an approved party - exactly when they choose, and no further.

If your wallet runs on Turnkey, you can turn this on

The integration lives at the Turnkey layer, so any product built on Turnkey can enable it. Privacy becomes a capability of the wallet your users already operate on, on the keys they already control, inside the app they already use - not a separate product they have to go find.

Explore the integration ->