Features
Hinkal Pay is a lightweight application and SDK that enables users and enterprises to send, receive, and distribute funds privately using their existing public wallets.
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:
• Sending confidential settlement
• Receiving confidential settlement
• Executing private payouts from confidential balance
This allows PSPs, payment stacks, merchants, and enterprises to integrate confidential settlement and payout functionality into existing payment flows without introducing new wallets, custody changes, or chain migration.
User Experience
Send Confidential Settlement
The sender, such as a PSP, merchant, counterparty, or enterprise payer:
Deposits funds into the Hinkal smart contract instead of transferring directly to the recipient’s public wallet (EOA)
Fund move into a confidential balance inside Hinkal smart contract, and is accessible with recipient's existing wallet
Sender, recipient, and amounts remain confidential on-chain.
How to execute confidential settlement?
Connect your existing wallet at pay.hinkal.io
Enter recipient wallet address
Select token, amount, and chain
Choose confidential settlement
Submit
Receive Confidential Settlement
The recipient receives funds 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
The recipient does not receive a standard on-chain transfer to their public wallet. Instead, the funds appear as a confidential balance within the Hinkal smart contract, controlled by that wallet.
No new wallet is created. The public wallet remains the authentication and control layer.
How to receive confidential settlement?
Visit pay.hinkal.io
Connect the same wallet address the sender entered as the recipient
Vie and access funds into a confidential balance
Execute Confidential Payouts
Once funds accessed in the confidential balance, the recipient can:
Execute confidential payouts to vendors, affiliates, employees, partners, or treasury accounts
Execute batch payouts, including payroll and operational distributions
Send directly to a public wallet address 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