Non-custodial fund flow
Hilt is designed so the buyer pays on-chain and the merchant controls the payout wallet. The product is meant to run the payment-to-access workflow, not to sit on a hidden merchant balance.
Trust & safety
Know what Hilt handles, what it never takes custody of, and where responsibility stays.
Cold traffic should not have to reverse-engineer this from legal pages. Hilt is designed to keep the payment flow readable: the buyer signs with their own wallet, the merchant controls the payout wallet, and the receipt and support trail stay visible after payment.
At a glance
Buyer signs with their own wallet
Merchant controls payout destination
Hilt records receipts and member trail
Private keys are never the product model
How the trust model works
A merchant should be able to explain this flow in plain English.
Hilt should make the promise before payment, the payout after settlement, and the support trail later all line up. If one of those pieces feels vague, trust gets harder.
1. The buyer signs with their own wallet
The buyer approves the payment themselves. Hilt does not ask them to hand over custody to complete the flow.
2. The merchant controls the payout wallet
The commercial destination is merchant-owned. Hilt is there to route and record the flow, not to become the wallet owner.
3. The record stays readable afterwards
Receipts, member state, renewal timing, and support context stay connected so the merchant can prove what happened.
Buyer wallet signing
Buyers sign and broadcast payments with their own wallets. Hilt does not ask a buyer for their private key and does not sign transactions on their behalf.
Merchant payout wallet control
Merchants choose the payout wallet for each flow. That payout destination should be reviewed carefully by the merchant before a product or template goes live.
What Hilt records
Hilt keeps the operational trail around a payment: product setup, receipt records, member status, renewal timing, support context, and the post-payment destination that was promised to the buyer.
What Hilt does not custody
Hilt does not custody buyer funds, does not take possession of wallet private keys, and does not pretend to replace the merchant's own responsibility for payout wallet ownership or access delivery.
Private key and API key safety
Buyers should never share wallet seed phrases or private keys. Merchants should treat Hilt API keys as secrets inside their own systems, rotate them if exposed, and keep internal access tightly limited.
Receipts and support trail
Every useful payment flow eventually becomes a support flow. Hilt keeps receipts, member state, and support context tied together so merchants can answer what happened without piecing it together from screenshots.
Merchant responsibility
Merchants remain responsible for the offer they publish, the accuracy of their payout wallet, the delivery destination, the community rules, and how refunds or access disputes are handled under their own policy.
Refunds and access disputes
Hilt gives merchants a clearer payment and receipt trail, but the merchant still decides how to resolve a refund or access complaint. Buyers should be able to read that policy before they pay.
Legal and contact path
The legal pages should support the trust story, not replace it.
Hilt currently operates in the UK under the trading name Hilt. If you need commercial, legal, support, or privacy detail, the fastest path is below.
Does Hilt hold customer funds first?
No. Hilt is built around a non-custodial flow where the buyer pays on-chain and the merchant controls the payout wallet.
Does the buyer sign with their own wallet?
Yes. The buyer uses their own wallet to approve the payment. Hilt does not ask for a private key or seed phrase.
Who controls the merchant payout wallet?
The merchant does. Hilt helps configure and operate the flow, but the merchant is responsible for setting and reviewing the payout wallet correctly.
What information does Hilt keep after a payment?
Hilt records the payment context that helps merchants operate the business afterwards: receipts, member or access status, renewal timing, support trail, and the destination that was promised to the buyer.
Does Hilt store wallet private keys?
No. Hilt does not store buyer wallet private keys. Merchants should also keep their own wallet credentials outside Hilt and treat API keys as secrets.
What if a buyer pays but gets stuck afterwards?
That is exactly why the receipt and support trail matters. Hilt keeps the payment, member outcome, and support context tied together so the merchant can investigate what happened cleanly.
Who is responsible for refunds or access disputes?
The merchant is. Hilt provides the record of what was sold and what happened afterwards, but the merchant's own refund and access policy still governs the commercial relationship.
Where can I read the legal terms or contact Hilt?
Use the legal pages for terms, privacy, and refund policy, or contact Hilt directly through the public sales and support addresses linked below.