# Hinkal SDK

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 is designed for PSPs, wallets, payment stacks, and financial applications that need to operate on public blockchains without exposing sensitive transaction history.

* [<mark style="color:purple;">**Hinkal SDK**</mark>](https://www.npmjs.com/package/@hinkal/common?activeTab=readme) - Complete toolkit for most integration use cases.
* [<mark style="color:purple;">**Hinkal Demo app**</mark>](https://github.com/Hinkal-Protocol/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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hinkal-team.gitbook.io/hinkal/for-integrators/hinkal-sdk.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.