Integration model
Hinkal Receive is designed to be embedded directly into payment and treasury workflows where recipients need to access and manage private balances settled inside the Hinkal smart contract.
It enables merchants, operators, and institutional counterparties to receive funds on-chain as a private balance, controlled by their existing public wallet.
Where it can be integrated
Hinkal Receive can be deployed inside:
Merchant dashboards (PSPs, payment processors)
Wallet interfaces
Treasury portals
Settlement and payout systems
Integrators expose a simple experience such as “Receive Privately” or “Private Balance”, without requiring users to understand privacy primitives such as shielding, UTXOs, or note management.
UI + White-Label Deployment
Hinkal Receive is shipped not only as an SDK, but also as a production-ready UI module.
Integrators can choose between:
SDK-only integration (fully native UX)
Hosted Receive UI (Hinkal-managed portal)
White-label Receive portal (custom domain + branding for PSPs/merchants)
This allows PSPs and payment stacks to launch private settlement quickly without building custom interfaces.
In the Receive portal, users can:
connect their existing wallet
view private balances settled into Hinkal smart contracts
manage payouts from the private balance (payroll, vendors)
selectively reveal transaction history via viewing keys when needed
Scope and Compatibility
Supported across major public chains: Ethereum, Solana, Base, Polygon, Arbitrum, Optimism, and Arc
Non-custodial by design
No chain migration, private chains, or liquidity relocation required
Compatible with existing settlement and compliance workflows
Viewing keys enable internal monitoring, auditability, and selective disclosure
Outcome
Hinkal Receive allows payment stacks to offer a clean merchant experience where funds are received privately on-chain, but accessed with the merchant’s existing wallet, making confidential settlement and payouts feel like a standard payment flow.
Last updated