> For the complete documentation index, see [llms.txt](https://hinkal-team.gitbook.io/hinkal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hinkal-team.gitbook.io/hinkal/hinkal-sdk/hinkal-sdk.md).

# Getting Started

Embed private payments 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](/hinkal/ecosystem/supported-chains.md), while keeping custody, compliance, and routing unchanged.

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

### **Choose Your Platform**

* [Web / TypeScript](/hinkal/hinkal-sdk/sdk-description.md) - Node.js, browser, React, and Next.js
* [React Native](/hinkal/hinkal-sdk/react-native-sdk.md) - React Native and Expo mobile apps
* [Go](/hinkal/hinkal-sdk/go-sdk.md) - backends, payment infrastructure, and settlement services
* [iOS](/hinkal/hinkal-mobile-sdk/ios/ios-sdk.md) - native Swift apps
* [Android](/hinkal/hinkal-mobile-sdk/android/android-sdk.md) - native Kotlin apps
* [Demo App](https://github.com/Hinkal-Protocol/Hinkal-Demo-App) - an example web application built on the Web / TypeScript SDK

The SDK abstracts the privacy mechanics. Developers call simple functions; Hinkal handles proofs, routing, and relaying.

***

### **What the SDK enables**

With a single integration, teams can support:

* **Private settlement and payouts** - 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
* **"Send privately" from public wallets** - public-to-public transfers with no shielding UX and no new wallet model
* **Selective disclosure for compliance** - viewing keys let authorized parties audit or monitor activity without making it public

***

### **Integration Model**

* No smart contract changes required
* No chain or liquidity migration
* Self-custodial by design
* Compatible with existing dashboards and workflows

Privacy is handled at the infrastructure layer, not the interface. Users and operators keep the same UX; on-chain visibility is removed.

***

### **Supported Flow Types**

* [x] Public → Public (private routing) - sender is not publicly attributable
* [x] Public → Private - assets enter a private balance
* [x] Private → Private - sender, recipient, and amount are not visible on-chain
* [x] Private → Public - recipient is public; sender and history stay private

***

### **Who uses the SDK**

* Payment Service Providers (PSPs)
* Wallets and embedded finance platforms
* OTC desks and treasury systems
* Payroll, payout, and settlement tools
* Individual builders

***