Connect Discord

With Discord connected, every approved sale creates a personal link. The buyer opens the link, signs in with their Discord account and lands in your server with the purchase role. If they were already in the server, they just get the role. On refund, chargeback or at the end of the subscription, the bot takes the role away and, if you want, removes the person from the server.

Before you start, read how paid communities work.

Step 1: create the application and the bot on DiscordCopy Anchor Link

1. Open the Discord Developer Portal, at discord.com/developers/applications, and click New Application. The application name shows to the buyer on the authorization screen: use the store name.
2. In General Information, copy the Application ID.
3. In OAuth2, copy the Client Secret. If it does not show, generate a new one.
4. In Bot, generate the bot token and copy it.
5. In Discord, open User Settings›Advanced and turn on Developer Mode. Then right-click your server and choose Copy Server ID.

Keep the four values for step 2.

Step 2: connect in VipterCopy Anchor Link

1. In the Vipter dashboard, open General›Integrations›Communities›Discord.
2. In Connection, fill in the fields:

3. Copy the Redirect URL shown right below. In the Developer Portal, open OAuth2›Redirects, add exactly that address and save.
4. Turn on Remove from the server when access ends if you also want to remove the person from the server, besides the role. When off, the person only loses the role and stays in the server.
5. Leave Active on and click Save.

Vipter checks the bot token, whether the Client Secret matches the Application ID and whether the bot is in the server. Since the bot has not been added yet, the connection is saved with the warning The bot is not in the server. Use the Add the bot to the server button.

Step 3: add the bot to the serverCopy Anchor Link

1. After saving, click Add the bot to the server. Opens Discord with the permissions it needs: create invite, kick members and manage roles. Then, under Roles, drag the bot role above the roles it will hand out.
2. In Discord, confirm the server and authorize.
3. Go back to Vipter and click Test connection.

Step 4: put the bot's role above the store's rolesCopy Anchor Link

Discord only lets a bot grant roles that are below its own role.

1. In the server, open Server Settings›Roles.
2. Drag the bot's role, which has the application's name, above every role it will grant.

Step 5: link each offer to a roleCopy Anchor Link

1. In Server Settings›Roles, right-click the role and choose Copy Role ID. Developer Mode must be on.
2. In Vipter, in Access rules, fill in:

3. Click Add rule.

The bot checks that the role exists, that it has the manage roles and create invite permissions, and that its role is above. With removal from the server on, it also checks the kick members permission. If something is missing, the rule is not saved and the dashboard says what to fix.

Step 6: testCopy Anchor Link

1. Click Test connection. Vipter checks the bot, the server and every rule again.
2. Make a test purchase of an offer with a rule and follow the link on the thank-you page, as a buyer. See Test your store.

How the buyer joinsCopy Anchor Link

1. The buyer opens the personal link, on the thank-you page, in the e-mail or in the portal, and taps "Join with Discord".
2. Discord shows your application's authorization screen, which asks to see the account and to join servers.
3. After authorizing, the buyer joins the server with the purchase role and returns to the link page, which confirms it.

If they leave the server while the access is valid, they just open the link again and join. The buyer's walkthrough is in Join the community you bought.

When access endsCopy Anchor Link

The bot takes away the rule's roles. With Remove from the server when access ends on, it also removes the person from the server. If Discord refuses, Vipter tries again, as explained in Follow the accesses.

Common problemsCopy Anchor Link

• The token was not accepted. Check that you copied the whole token.

  Generate another token on the Bot page of the Developer Portal and save. Generating a new token invalidates the previous one.

• The Client Secret does not match the Application ID.

  Check that the Application ID and the Client Secret belong to the same application.

• The bot is not in the server. Use the Add the bot to the server button.

  Do step 3.

• Use the numeric ID (17 to 20 digits).

  Copy the ID again with Developer Mode on. It is a number, without letters.

• The role is above the bot role. In Server Settings → Roles, drag the bot role above it.

  Do step 4.

• The bot needs the Manage Roles permission.

  Use the Add the bot to the server link again or give the permission to the bot's role in the server settings.

• The bot needs the Create Invite permission to add buyers to the server.

  Give the create invite permission to the bot's role.

• The bot needs the Kick Members permission, because removal from the server is on.

  Give the kick members permission to the bot's role or turn off removal from the server.

• This role is managed by an integration and cannot be assigned.

  Roles of other bots and integrations cannot be granted. Create a role of your own for the product.

• Discord shows a redirect error to the buyer

  The Redirect URL is not in OAuth2›Redirects, or it was pasted differently. Copy it again from the dashboard and save it in the Developer Portal.

What to do nextCopy Anchor Link

• Understand what happens on each sale in How paid communities work.
• Edit the Community access e-mail in Transactional e-mails.