For the complete documentation index, see llms.txt. This page is also available as Markdown.

Getting Started

Embed confidential payments and settlement into existing systems — without changing wallets, contracts, or chains.

The Hinkal SDK lets platforms add privacy to on-chain transfers and settlement flows on Ethereum, Solana, Tron and major EVM chains, while keeping custody, compliance, and routing unchanged.

It supports Node.js, browser apps, React Native mobile apps, and native Go backends.

It is designed for PSPs, wallets, payment stacks, and financial applications that need to operate on public blockchains without exposing sensitive transaction history.

  • Hinkal SDK - Complete toolkit for Node.js, browser, React, and Next.js integrations.

  • Hinkal React Native SDK - Mobile SDK for React Native and Expo.

  • Hinkal Go SDK - Native Go SDK for backends, payment infrastructure, and settlement services.

  • Hinkal Demo app - An example web application utilizing the Hinkal SDK.

The SDK abstracts all privacy mechanics. Developers call simple functions — Hinkal handles the rest.


What the SDK Enables

With a single integration, teams can support:

  • Confidential settlement and payouts

    Execute on-chain transfers without publicly revealing sender, recipient, balances, or amounts.

  • Private treasury operations

    Move funds internally or between counterparties without broadcasting inventory or strategy on-chain.

  • Public-to-public private transfers

    Enable “send privately” from standard public wallets — no shielding UX, no new wallet model.

  • Selective disclosure for compliance

    Viewing keys allow authorized parties to audit or monitor activity without making it public.


Integration Model

  • No smart contract changes required

  • No chain or liquidity migration

  • Non-custodial by design

  • Compatible with existing dashboards and workflows

Privacy is handled at the infrastructure layer, not the interface — so users and operators keep the same UX, while on-chain visibility is removed.


Supported Flow Types

  • Public → Public (Private Routing)

    Sender is not publicly attributable.

  • Public → Private

    Assets enter a confidential state.

  • Private → Private

    Fully confidential transfers, the value of transfer is not visible on-chain.

  • Private → Public

    Recipient is public, sender and history remain private.


Who Uses the SDK

  • Payment Service Providers (PSPs)

  • Wallets & embedded finance platforms

  • OTC desks & treasury systems

  • Payroll, payout, and settlement tools

  • Individual builders

Last updated