# Institutional Use Cases

### 1. Payment Service Providers (PSPs) & Payment Processors

**Problem**

Public settlement exposes merchant volumes, routing relationships, and revenue concentration. Competitors, analytics firms, and counterparties can reconstruct business performance from on-chain data.

**How Hinkal helps**

Hinkal enables confidential settlement and payouts inside PSP dashboards, removing public visibility into:

* Merchant volumes and flows
* Routing and processing relationships
* Treasury balances used for settlement

**Outcome**

* Private merchant settlement on public chains
* No change to custody, compliance, or fiat rails
* Reduced competitive and operational exposure

Best for: PSPs, crypto processors, payment gateways, neobanks

***

### 2. Payroll, Contractor Payments & Invoicing

**Problem**

On-chain payroll and vendor payments expose salaries, pay cadence, organizational structure, and vendor relationships.

**How Hinkal helps**

Hinkal enables private payroll and invoicing flows using stablecoins, with optional selective disclosure for compliance and accounting.

**Outcome**

* Salaries and payments remain confidential
* No public “who paid who + how much” trail
* Compatible with existing payroll and payout systems

Best for: Global payroll platforms, Web3 companies, DAOs, employers paying in stablecoins

***

### 3. Wallets & Embedded Finance Platforms

**Problem**

End users increasingly demand privacy, but wallets struggle to offer it without complex UX, chain migration, or regulatory risk.

**How Hinkal helps**

Wallets can integrate “send privately” functionality using Hinkal — abstracting shielding and routing under the hood.

**Outcome**

* Private transfers from public wallets
* No new wallet model or chain migration
* Privacy delivered as a feature, not a fork

Best for: Wallet providers, embedded finance platforms

***

### 4. Card Issuers & Stablecoin Settlement

**Problem**

Stablecoin settlement for card programs exposes issuer volumes, redemption flows, and counterparty relationships on public ledgers.

**How Hinkal helps**

Hinkal enables confidential routing and batching of settlement flows while preserving existing redemption and fiat settlement processes.

**Outcome**

* No linkage between issuer wallets and settlement endpoints
* Privacy without changing networks, rails, or compliance models
* Public-chain settlement without public-chain exposure

Best for: Card issuers, crypto card programs, payment networks

***

### 5. Treasury Operations & OTC Desks

**Problem**

Large transfers between desks, counterparties, and internal wallets broadcast inventory movements, AUM changes, and trading intent — increasing front-running and targeting risk.

**How Hinkal helps**

Hinkal enables confidential treasury movement and OTC settlement while preserving public-chain finality.

**Outcome**

* Inventory movements are no longer publicly attributable
* Counterparty relationships remain private
* Reduced surveillance and execution risk

Best for: OTC desks, liquidity providers, funds, market makers

***

### 6. Partner, Affiliate & Revenue-Share Payouts

**Problem**

Public affiliate payouts expose partner lists, commercial terms, and total spend — allowing competitors to reverse-engineer growth strategies.

**How Hinkal helps**

Hinkal enables confidential partner payouts without revealing recipients, amounts, or aggregate spend.

**Outcome**

* Partner networks stay private
* Revenue-share logic is not externally visible
* Reduced competitive intelligence leakage

Best for: Marketplaces, platforms, operators, creator and affiliate networks

***

### Why Institutions Choose Hinkal

* Universal — works across Ethereum, Solana, TRON, and major EVM chains
* Non-custodial — assets remain under user control
* Composable — integrates into existing stacks
* Compliant by design — selective disclosure via viewing keys, KYT, and zkTLS
* Neutral — not a chain, not a wallet, not a gatekeeper