Does Hilt hold customer funds first?
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.
FAQ
Short answers for merchants, developers, and agents checking how payout ownership, access records, receipts, renewals, support context, and webhooks fit together before they publish a live flow.
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.
Hilt is built for digital products, services, paid communities, memberships, gated content, private downloads, courses, research access, and customer-specific access flows.
Hilt checkout is focused on Solana and USDC. Buyers approve the payment from their own wallet, and the merchant payout wallet remains the settlement destination.
Yes. Buyers pay from a supported Solana wallet. The buyer guide explains the steps in plain language so merchants do not have to teach the whole wallet flow from scratch.
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.
Merchants can send buyers to the Hilt payment guide before checkout. It explains connecting a wallet, approving the payment, and receiving access without requiring the merchant to become a crypto educator.
Yes. Hilt can deliver signed Telegram invite links after payment. The links are designed for access delivery rather than manual proof-of-payment checks.
Yes. Hilt supports Discord access flows where payment confirmation can grant the buyer the relevant role and keep the member record tied to the payment trail.
Yes. Hilt can be used for private downloads and other access-after-payment products where the buyer needs a clean proof trail and a post-payment destination.
Yes. Merchants can use hosted checkout links or the Hilt embed on sites such as Ghost, Carrd, Framer, Webflow, WordPress, or a custom HTML page.
Yes. Hilt Pay for WooCommerce is approved on WordPress.org and remains available as a direct ZIP fallback. It is designed for digital products, memberships, and access commerce.
Yes. Zapier can connect Hilt events and merchant workflows to other tools, including CRM, email, spreadsheets, support, and operating automations.
Hilt uses signed renewal links for recurring access. A member approves each renewal payment explicitly, which fits the zero-custody model and avoids hidden automatic charges.
No. Hilt does not store a card or quietly charge a buyer later. Renewal is an active buyer-approved payment step through the wallet flow.
Yes. Developers can use the API, SDKs, CLI, webhooks, and Postman collection when a merchant needs deeper automation beyond the dashboard and hosted checkout.
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.
Webhooks let a merchant system react to Hilt events such as payment confirmation, checkout outcomes, access delivery, or membership state changes.
Hilt has a free starting tier and paid plans for merchants that need lower transaction fees, more live offers, and stronger operating room as volume grows.
No. Hilt is designed around direct wallet settlement. The checkout records the payment and operating context without turning merchant revenue into a Hilt-held balance.
Refund policy and buyer support remain merchant responsibilities. Hilt keeps the receipt, transaction, member, and support context together so the merchant can review the payment trail clearly.
On-chain wallet payments do not behave like card payments. Merchants should still set clear refund and access policies because buyer support and trust still matter.
Hilt keeps the operational record needed for receipts, member state, transaction hashes, access outcomes, renewals, and support context.
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.
No. Hilt is for legitimate merchants and creators. It is not for illegal activity, fraud, scams, exploitation, sanctions evasion, or abusive material.
Start with the smallest plan that supports the first live offer, then upgrade when volume, lower fees, more offers, or support expectations make the paid plan economics obvious.