Launch Telegram and Discord memberships, gated community access, private downloads, and digital products from one merchant workspace. Hilt keeps payouts direct to the merchant wallet while handling receipts, renewals, access delivery, and the record keeping around each payment.
Start free, publish one live flow, and upgrade once the payment-to-access loop is proven.
Merchant launch flow
Checkout
Merchant outcome
Merchant-owned payouts
The buyer pays on-chain and Hilt routes the net directly to the merchant wallet.
Recurring access, not custodial billing
Renewals, grace windows, and reactivation links keep access moving without hiding funds.
Receipts and support built in
Buyer history, receipts, and support context stay tied to the payment instead of disappearing into chat.
Why merchants trust the flow
Merchants do not just need a checkout. They need to know the payout reached the right wallet, the buyer got the right access, and support can see the full story if something goes wrong.
1. Buyer pays with a clear commercial promise
The buyer sees what they are buying, what it costs, and where they should land after payment.
2. The merchant payout lands where it should
Hilt records the Hilt fee and routes the net to the merchant payout wallet instead of hiding it behind a platform balance.
3. The record stays readable afterwards
Receipts, member status, renewals, and support context stay tied together so the merchant is not guessing later.
The buyer pays on-chain and Hilt routes the net straight to the merchant payout wallet instead of parking it in a hidden balance.
Payment confirmation, member status, receipts, and support history stay tied together instead of being scattered across chat, wallets, and screenshots.
Renewal timing, grace windows, and follow-up links stay visible in the merchant view so access does not turn into guesswork.
Merchants can launch in the dashboard first, then automate the same live products from the API or CLI on any tier without rebuilding the operating model.
Interactive demo
Open the demo page to change the offer and watch three things update together: what the merchant is selling, what the buyer sees at checkout, and what the post-payment outcome should look like.
Merchant side
Buyer side
After payment
The useful part of the demo is not just the checkout. It shows why merchants trust Hilt afterwards: payment confirmation, the member outcome, the receipt, and the support context all need to tell the same story.
Templates first
Choose the right launch shape for memberships, paid communities, private downloads, or merchant-controlled unlocks.
Telegram memberships
Best for paid communities
Collect a Solana payment, attach it to a Telegram user ID, and manage renewals from one merchant dashboard.
Buyer flow
Buyer pays, gets the invite path, and is recorded against their chosen Telegram handle or user ID.
Merchant view
Merchants can verify who has paid, who is expiring, and who needs support without leaving Hilt.
Renewals
Renewal reminders and one-click renewal links keep the membership cycle moving.
Discord access flows
Best for tokenless access
Launch paid Discord memberships without forcing your customers into custodial flows or manual checks.
Buyer flow
Customers pay on-chain, confirm their member identity, and follow a clear after-payment handoff.
Merchant view
See member status, receipts, and payment history in one clean operating view.
Renewals
Use recurring reminders and expiry tracking instead of chasing manual renewals.
Downloads, redirects, and digital unlocks
Best for digital products
Sell a paid report, unlock a private page, issue a link, or gate a private launch page with the same checkout engine.
Buyer flow
The checkout is lightweight, wallet-native, and fast enough for one-off purchases and paid access.
Merchant view
You control payout wallet defaults, redirect behavior, and support context from the workspace.
Renewals
Use reminders for repeat access plans or simple follow-up prompts for re-purchase flows.
How it works
Publish the flow, take payment, prove who paid, then keep access and records tidy as volume grows.
Start with Telegram, Discord, redirects, downloads, or a custom access flow instead of wiring everything from scratch.
Set your payout wallet, access destination, renewal timing, and checkout branding, then publish a clean payment link.
Hilt confirms the on-chain payment, records the receipt, and links it to the buyer details you asked for.
Track payments, members, renewals, receipts, and support from the dashboard as your access flow grows.
Full breakdown
Hilt combines launch, payment capture, buyer identity, member records, renewals, receipts, and support so merchants are not stitching the whole paid access loop together by hand.
Paid communities
Telegram and Discord merchants who need a simple way to sell access, verify members, and handle renewals.
Crypto-native digital products
Premium content sellers, research desks, and independent builders selling downloads, links, and private access.
Gated launches and subscriber access
Launches, subscriber products, and gated areas that need wallet-native checkout without building the whole access loop from scratch.
A guided builder for paid communities, gated access, redirects, downloads, and merchant-owned custom flows.
Hosted Solana checkout with merchant-owned payout routing, branded buyer pages, confirmation flow, receipts, and a clean operating trail.
Wallet-linked member records, Telegram and Discord connect steps, expiry tracking, lookup tools, and renewal reminders that keep paid access predictable.
Customer tickets, receipt context, member troubleshooting, and a clear history for follow-up when something needs attention.
Merchant docs first, then API routes and CLI workflows for teams that want to automate the same live products they launched in the app.
Set payout wallets, delivery targets, checkout branding, and workspace defaults without turning Hilt into a custody layer.
Developer path
Start in the app, then automate the same merchant workflow through supported API routes, CLI commands, and docs when you are ready.
What developers automate
Launch in the dashboard, then automate the same merchant objects from your backend. The app says templates; the API and CLI expose those same live records as products.
Use Hilt from the terminal for products, member lookups, receipts, and API key management once the dashboard flow is already live.
The docs explain the merchant workflow first, then go deep on the supported API, checkout examples, post-payment operations, error handling, and CLI coverage for the same live templates.
Merchant quickstart
Get a merchant live quickly with the dashboard-first launch path.
Examples
Copy supported cURL, TypeScript, and Python examples for products, checkout, members, receipts, and support.
Checkout and products
Review the supported product and hosted-checkout contract without wading through internal plumbing.
Webhooks and async flow
Understand the async settlement path, webhook-style integrations, and how to keep your backend in sync with Hilt.
Pricing
The early tiers are there to help merchants prove one live offer. Higher tiers mostly buy lower Hilt fees, stronger support, and more comfortable operations once the volume is worth it.
Billing
Start free, then move up once your access flow is live and proving itself.
Annual billing lowers the effective monthly cost.
Free
Start here
Free
5.0% + $0.30 transaction fee
Start with one live flow and upgrade later.
For first templates, testing the full payment-to-membership loop, and keeping one live link online before upgrading.
Starter
Low friction
$29
/month
2.0% transaction fee
Billed monthly.
For paid communities, solo merchants, and simple access links that need a clean launch path.
Growth
Scaling sweet spot
$99
/month
1.0% transaction fee
Billed monthly.
For active merchants running multiple templates, repeat renewals, and regular customer support.
Scale
Better economics
$299
/month
0.5% transaction fee
Billed monthly.
For higher-volume teams that want better fee efficiency, deeper controls, and stronger merchant tooling.
Common questions
The questions below are the ones that usually sit between “this is interesting” and “we should actually go live with this”.
The buyer pays on-chain and the merchant controls the payout wallet. Hilt helps run the flow without sitting on the merchant's funds first.
Usually one clear paid-access offer: a Telegram membership, a Discord access flow, a private download, or a gated redirect. The first launch should feel obvious to the buyer in one glance.
No. The dashboard is the main path. Merchants can launch from the app first and bring in the API or CLI later if the business needs deeper automation.
Hilt records the payment, receipt, and post-payment outcome together. If the flow creates or extends access, the merchant can follow that member trail and any later support issue from the same workspace.
No. API, CLI, and docs are available across the plan ladder. Higher tiers mainly change the economics, support level, and operating comfort once the volume is there.
That is where Hilt is strongest. Payments, receipts, member status, and support context stay tied together so the merchant is not hunting across wallets, chat logs, and screenshots to work out what happened.
Ready to get started
Start with one template, publish one real checkout, and bring in the API or CLI later if the business needs deeper automation.