Hinkal Enterprise Dashboard is Live

Stablecoin volume is moving on-chain. Institutions, banks, payments platforms, fintechs, treasuries, and merchants are moving real-world payment activity onto public ledgers - payroll, vendor payments, B2B settlement, internal transfers, partner payouts.

Bessemer Venture Partners wrote about this shift in their atlas on stablecoins. They named five structural blockers preventing stablecoins from scaling into global financial infrastructure. Privacy was one of them.

The reason is straightforward. Public ledgers are great for trustless settlement. They’re a poor fit for corporate operations, where every payment publishes sender, recipient, and amount to the entire network. Payroll runs, vendor relationships, intercompany transfers, partner payouts - these are confidential by default on traditional rails. Institutions won’t move them onto rails that broadcast every flow.

Polygon acted first

Polygon Labs was the first to act on that read. After partnering with Visa, Meta, and Modern Treasury, they chose hinkal as an exclusive privacy partner, powering confidential payments inside Polygon Wallet - the wallet institutions and enterprises already use.

"Bringing private payments to the Polygon wallet required a privacy layer we could trust at the infrastructure level. Hinkal brings the cryptographic rigor and compliance-first design that serious payment flows demand. It’s a strong foundation for what we’re building next."

- Marc Boiron, CEO, Polygon Labs

That integration closed one gap. There’s another it didn’t touch.

Enterprises don’t run treasury from a wallet

Off-chain, enterprises don’t run treasury from a single account. They run it from a structured operational system - a treasury dashboard with team roles, approval workflows, batch payment runs, contacts, analytics, transaction history, reporting.

A wallet is a transaction primitive. A dashboard is an operational system. When institutions move treasury on-chain, they need both. The wallet is where the asset lives. The dashboard is where finance teams run their work day-to-day.

What the Enterprise Dashboard is

The Enterprise Dashboard is a unified interface for institutions to run on-chain treasury operations privately. It’s designed around the payment systems enterprises already use - so finance teams don’t have to learn anything new.

Built for institutional on-chain finance: single and batch payouts, payroll management, transaction monitoring, treasury analytics, team roles and approvals, contacts.

Works with existing wallets.

Multi-chain across EVM, Solana, and TRON.

ZK-powered and self-custodial.

Compliant via KYT, viewing keys, and downloadable transaction history.

How it works

The Dashboard includes all the features and workflows institutional treasury actually needs. Confidential and wallet balances sit side-by-side. Stats track total confidential payouts, total payout volume, monthly throughput, and monthly transaction count. Recent transactions and pending payouts show what’s happening across the team at a glance.

Two delivery methods cover the operational range.

Confidential Settlement. Funds route to the recipient’s private balance inside Hinkal smart contract. No public on-chain link to sender, recipient, or amount. The recipients access private balances after connecting their existing wallets. No new account creation, no migration. An optional email notification can be enabled per payout.

Direct to Wallet. Funds arrive directly on the recipient’s public wallet, with Hinkal appearing as the sender. The originating treasury address stays confidential. Useful when the recipient needs immediate, native-asset receipt without a privacy step on their side.

The full surface:

  • Single payouts with ENS and SNS resolution, token selector covering USDC, USDT, DAI, and more.
  • Batch payouts via CSV upload, up to 500 rows per batch.
  • Receive Privately - shareable confidential payment link with QR code for inbound flows.
  • Team roles and a Pending Payouts queue for multi-approver workflows.
  • A shared Contacts book.
  • Full Transaction History with filters and CSV export.

Underneath every confidential transaction is a smart contract called a shielded pool. Funds inside the pool are recorded as cryptographic commitments - entries that record balances and ownership without revealing them on-chain. Every state change is verified using a zero-knowledge proof. The contract confirms a transaction is valid (sufficient balance, correct ownership, no double-spend) without seeing the sender, the recipient, or the amount.

Compliance, in practice

Confidentiality is about who can see, when, and under what authority - not about hiding everything from everyone. The Dashboard ships the controls auditors, regulators, and partners actually use:

  • Viewing keys for selective disclosure. Grant a regulator, auditor, or partner read access to specific records - without making the full history public.
  • Downloadable transaction history. Scoped by time range, filterable by type, status, source, and asset.
  • KYT monitoring, Chainalysis-compatible. Sanctions screening and risk scoring on every private transaction before it executes.

"Hinkal solves one of the hardest problems - privacy without sacrificing compliance. Viewing keys, selective disclosure, and KYT create a framework where institutions can operate confidentially on-chain."

- Mandeep Walia, Chief Compliance Officer, Circle

Your finance team keeps the compliance posture it already has. The Dashboard doesn’t introduce a new one.

Where this fits

Anywhere a finance team today uses a payment service provider dashboard and needs privacy without compromising operational tooling:

  • Treasury operations. Internal transfers between entities, treasury rebalancing, intercompany settlement.
  • Payroll. Employee and contractor payments at any cadence - confidential to counterparties and competitors.
  • Vendor and supplier payments. Single and batch payments to vendors, suppliers, and partners.
  • OTC settlement. Confidential settlement between counterparties without exposing pricing or counterparty relationships on-chain.
  • Partner payouts. Affiliate, partner, and revenue-share payouts where the recipient list itself is confidential.

A note on what ‘privacy’ means here. Fireblocks recently published a taxonomy of on-chain privacy solutions, placing full anonymity - sender, recipient, and amounts all shielded - as a distinct category, with Hinkal among its examples. They argue this level isn’t strictly required for many B2B use cases. In practice, the opposite is true. Payroll, vendor schedules, internal transfers, and deal-related flows aren’t partially confidential in traditional finance. Masking only an address while leaving counterparties and amounts public doesn’t close the gap.

The moment

Three things are now true at the same time. Stablecoin volume is moving on-chain at institutional scale. Privacy has been delivered at the wallet layer by the most institution-aligned chain. And the same protocol is now available as the operational treasury system finance teams run on.

That’s the moment. Enterprise Dashboard is live.

→ Try Out: [Hinkal Prime]