Features

A lightweight application and SDK that enables users to receive and manage funds privately using their existing public wallet.

Instead of sending assets directly to a merchant or recipient’s public address (where balances and settlement flows become visible on-chain), funds are deposited into the Hinkal smart contract as a private balance. The recipient then simply connects their current wallet to the Hinkal interface to unlock and access that balance.

This allows PSPs, payment stacks, and merchants to offer a native “receive privately” option, where settlement happens on public chains but wallet exposure, balances, and transaction history remain confidential, without any new wallets, chain migration, or custody changes.

---

User Experience

Hinkal Receive allows a user to receive funds privately without creating a new wallet or changing how they operate.

A merchant or user receives privately by:

• Sharing their existing public wallet address (EOA)

• Selecting “Receive Privately” in an integration flow (PSP dashboard, wallet UI, checkout)

• Opening the Hinkal Receive interface and connecting the same wallet

Once connected, the user can view and manage their private balance inside the Hinkal smart contract using their existing wallet as the access key.

No new wallet is created. The wallet simply acts as the authentication and control layer.

---

On-Chain Behavior

Under the hood, the sender (PSP, merchant payer, or counterparty):

• Deposits funds into the Hinkal smart contract instead of sending directly to the recipient’s EOA wallet

• Associates the deposit with the recipient’s public address

The recipient does not receive funds as an on-chain transfer to their wallet.

Instead, the funds appear as a private balance inside the Hinkal contract, controlled by the recipient’s existing wallet.

---

Privacy Properties

Hinkal Receive prevents public exposure of inbound payment activity by ensuring:

• The recipient wallet does not appear as the on-chain receiver

• Balances are not visible on the recipient’s wallet address

• Incoming volume and settlement relationships cannot be easily tracked or clustered

Externally, observers only see deposits into Hinkal’s smart contract, without being able to attribute those deposits to specific merchants or operational wallets.

---

Mental Model

Your wallet is the key. Your public wallet UI is a public door to see what is there. Hinkal is the private door.