Discord Flow
Use this format when payment should unlock access to a Discord server or role-based community.
Merchant setup
In the template builder, configure:
- format:
Discord - merchant payout wallet
- fixed amount in SOL or USDC
- delivery target or invite handoff
- destination name
Example:
Founding members - optional Discord role or guild override if one template should bypass the saved workspace default
- billing interval in days
- grace period in days
Workspace settings handle the shared checkout branding:
- checkout brand name
- logo image
- hero image
- default success button
Buyer experience
The buyer:
- opens the hosted checkout
- taps
Connect Discord - returns to checkout with the Discord identity linked
- pays from a Solana wallet
- receives confirmation and access instructions
Merchant workflow
The merchant can later verify:
- who paid
- which Discord identity was attached
- when the current membership period ends
- whether the member is active, in grace, expired, or failed delivery
Good Discord use cases
- premium servers
- role-gated communities
- subscription communities
- paid early-access or insider groups
Launch advice
- start with one clear role or server outcome
- keep the buyer identity field obvious
- keep the post-payment access handoff obvious
- make renewal timing easy to understand in the checkout description
- use support tickets for disputes instead of trying to reconcile by memory