Komerza bot vs custom application
Use a custom app if you want the bot in your server to carry your own branding, or you already run a bot and want one application for everything.
Setting up a custom Discord application
1
Create the application
- Go to the Discord Developer Portal and click New Application
- Give it a name - this is what customers see on the authorization screen - and create it
- Open the OAuth2 tab and copy the Client ID and Client Secret
2
Add the redirect URL to your application
Still on the OAuth2 tab, under Redirects, add this URL exactly, with no trailing slash:
3
Create the bot and copy its token
- Open the Bot tab and add a bot to the application
- Click Reset Token, then copy the Bot Token
4
Invite the bot to your server
Build an invite URL with your client ID and the two permissions Komerza needs:
Open the URL, pick your server, and authorize.
5
Copy your server ID
In Discord, enable Settings → Advanced → Developer Mode, then right-click
your server and choose Copy Server ID.
6
Connect it in Komerza
In the dashboard go to Discord, click Use Custom Bot, and fill in:
- Server (Guild) ID
- Client ID
- Client Secret
- Bot Token
Using the Komerza bot instead
On the Discord page, click the connect button and authorize the Komerza bot into your server. There is nothing to register and no credentials to paste. You can switch to a custom app later by disconnecting first.Settings
Three store-wide settings on the Discord page, each overridable per product.Join Mode - when the customer joins and gets the role
Join Mode - when the customer joins and gets the role
- Add and grant after payment (default) - the customer is added to your server and given the role only once payment completes.
- Add on link, grant after payment - the customer joins your server as soon as they link Discord at checkout, but the role waits for payment.
Discord Requirement - whether linking is mandatory
Discord Requirement - whether linking is mandatory
- Required - the customer cannot check out without linking Discord.
- Optional (default) - offered, not enforced.
- Disabled - not shown at checkout.
Revocation Behavior - what happens on refund or chargeback
Revocation Behavior - what happens on refund or chargeback
- Revoke and remove (default) - the role is removed and the customer is kicked from the server.
- Revoke role only - the role is removed, the customer stays in the server.
- Do nothing - the customer keeps the role.
Assigning roles to what you sell
Roles attach to variants, not products, so different tiers can grant different roles. Komerza reads the role list straight from your server, so create the roles in Discord first. Per-product overrides let one product require Discord while the rest of your catalogue doesn’t, or change the join mode for a single product. Anything left unset falls back to the store default.Grants
The Grants tab lists every role Komerza has handed out, with the customer, the role and the order behind it. You can Revoke a grant manually - useful when someone breaks your rules but hasn’t refunded.Troubleshooting
Next steps
Products & Variants
Roles are assigned per variant.
Managing Orders
Refunds drive role revocation.
Notifications
Discord alerts for store events are configured separately.
Selling Subscriptions
Expiring subscriptions can revoke access too.