Features
Hinkal Pay is a lightweight application and SDK that enables users and enterprises to receive, hold, and distribute 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 confidential balance. The recipient connects their existing wallet to the Hinkal interface to access and manage that balance.
Hinkal Pay supports both:
• Confidential settlement (inbound flows)
• Confidential payouts (outbound flows)
This allows PSPs, payment stacks, and merchants to offer native “receive privately” and “pay privately” functionality while continuing to operate on public chains, without new wallets, custody changes, or chain migration.
User Experience
Hinkal Pay allows a user or enterprise to receive and distribute funds privately without creating a new wallet or altering existing workflows.
Receiving Privately
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)
Connecting the same wallet to the Hinkal Pay interface
Once connected, the user can view and manage their confidential balance inside the Hinkal smart contract. No new wallet is created. The public wallet acts as the authentication and control layer.
Paying Privately
From the confidential balance, users can:
• Send funds privately to another public address
• Execute batch payouts (vendors, affiliates, payroll)
• Withdraw publicly when required
Private payouts ensure that sender, recipient, and amount are not publicly visible on-chain. Public withdrawals remain available when disclosure is operationally required.
On-Chain Behavior
Under the hood:
The sender (PSP, merchant, counterparty, or enterprise payer):
• Deposits funds into the Hinkal smart contract instead of transferring directly to the recipient’s public wallet
• Associates the deposit with the recipient’s public address
The recipient does not receive an on-chain transfer to their EOA wallet. Instead, funds appear as a confidential balance within the Hinkal contract, cryptographically linked to their public wallet.
Subsequent payouts can:
• Remain within the confidential environment
• Or exit to a public address via standard on-chain transfer
Privacy Properties
Hinkal Pay ensures:
• The recipient wallet does not appear as the on-chain receiver
• Wallet balances remain confidential
• Incoming settlement volumes cannot be easily tracked or clustered
• Outbound payout relationships are not publicly exposed
Externally, observers see deposits into the Hinkal smart contract without attribution to specific operational wallets.
Mental Model
Your public wallet remains your identity and control key.
Public chains show what is sent directly to your wallet.
Hinkal introduces a confidential balance layer controlled by that same wallet.
The wallet is the key.
Hinkal is the confidential environment it unlocks.
Last updated