​
Discord flows

Discord works well in Hilt when the buyer already understands the destination: a server, a role-gated area, or a paid member community. If you want the public product summary first, see Discord access. The goal is not just to take payment. It is to make the access handoff and the merchant trail feel clean afterwards.

​
Typical Discord flow

  1. the merchant publishes a Discord template
  2. the buyer opens the hosted checkout
  3. the buyer connects or confirms Discord identity when required
  4. the buyer pays on Solana
  5. the buyer lands in the final Discord destination

​
What merchants should prepare

Before launch, make sure you have:
  • the correct invite, role, or destination URL
  • Hilt Connect invited to the Discord guild if you want Discord role automation
  • the guild ID saved in Hilt, plus the paid-role ID if you want provider-driven role automation
  • an offer name that matches the community buyers already know
  • support wording for buyers who need help after payment

​
Add Hilt Connect to your guild

Discord automation works best when Hilt Connect is in the server you sell access to. Invite Hilt Connect before relying on automated role delivery. For renewal messaging, this shared guild is the important part: the customer must be in a server that Hilt Connect is also in. For paid-role automation, Hilt Connect also needs permission to manage roles, and the Hilt Connect role must sit above the paid member role inside Discord. If you use your own Discord bot instead, paste that custom bot token in workspace settings and apply the same guild and role requirements.

​
Discord automation and rescue

When Discord automation is configured, Hilt can grant or remove the paid role directly instead of depending only on a saved invite path. If that provider step fails:
  • the membership records the access problem immediately
  • Hilt can retry the access or revoke path on a rescue schedule
  • your team can still run a direct retry when the case needs hands-on follow-up
That gives Discord merchants a cleaner operational loop than discovering access failures only after buyers complain.

​
Discord launch checklist

Before wider traffic, confirm:
  • the success destination is correct
  • the template title matches the community buyers expect
  • the first payment creates the right member record afterwards
  • support can tell what happened without guesswork

​
What to check after the first payment

Before wider traffic, verify:
  • identity resolution feels clear to the buyer
  • the success state points to the right Discord destination
  • the member record appears correctly
  • the receipt exists
  • support can follow the story from payment to access

​
Good Discord habits

  • keep the offer name close to the Discord community name
  • avoid vague role labels in checkout
  • test the exact destination the buyer will see after payment
  • use Members and Receipts as the operating truth afterwards
Discord works best when the buyer never has to guess what they bought or where they should land after payment.

​
Common questions

​
Can Hilt sell paid Discord access?

Yes. Hilt can sell paid Discord access through hosted checkout, capture or confirm buyer identity, record the payment, and keep the member, receipt, renewal, and support trail in Hilt.

​
Why does Hilt Connect need to be in my Discord server?

Discord only lets a bot DM a user when the bot and user share a guild. Hilt Connect also needs the right role permissions if you want provider-driven paid-role automation. Yes. A saved invite or destination URL is a valid first launch path. Add role automation after you have tested the checkout and access promise end to end.