Discord integration

Discord turns confirmed support into community access without asking Loresta to read general server conversations.

Setup flow

Install the server app

The creator authorizes the Loresta bot and application commands for a server they manage.

Choose the destination

Select a supporter hub channel, an optional fallback role, and offer-specific roles below the bot’s highest role.

Publish the support path

Post or refresh one interactive supporter hub with Loresta contribution links, approved perks, and private access checks.

Link supporter access

An eligible supporter proves their Loresta receipt, signs in to Discord, joins the creator server in one click when enabled, and receives the role mapped to their Loresta offer.

Scopes and permissions

Purpose	Required access
Creator installation scopes	identify bot applications.commands
Bot permissions	View Channels, Send Messages, Embed Links, and Manage Roles
Supporter linking scopes	identify guilds.join
Main private menu	/loresta for support, perks, goals, access, and creator setup health
Shortcuts	/support /goal /perks /access

guilds.join is used only after Loresta verifies the supporter against a paid receipt for the connected creator. It lets the supporter enter that creator’s server without finding a separate invite and does not require Create Instant Invite. Loresta does not request the Message Content intent and does not monitor general server conversations.

Signed interactions

Every HTTP interaction is verified with Discord’s Ed25519 public key and the signature timestamp. Invalid signatures receive HTTP 401.

Role safety

Every selected supporter role must remain below the Loresta bot’s highest Discord role. A creator can map individual Loresta offers to Discord tiers and keep a fallback role for unmapped offers. Loresta reconciles access when a contribution is confirmed, refunded, disputed, or repaired from Connections.

Support cards

Creators can publish or refresh one supporter hub in the configured text or announcement channel. The hub links back to the creator’s Loresta Page, shows approved perks or goal progress, offers a private access check, and can show anonymous recent-support activity. Amounts and supporter names stay private unless the supporter chooses otherwise.

/loresta is the simplest starting point. It privately opens a guided menu for supporters and a setup checklist for server managers. Supporters can explore offers, view visual goal progress, understand how verified access works, and check or repair a role without remembering another command. The /support, /goal, and /perks shortcuts publish the corresponding approved card, while /access opens the private access check directly. Loresta sets allowed_mentions to an empty parse list so support cards do not create unexpected mentions.

Supporter identity linking

Supporter linking uses a separate Discord OAuth flow with identify and guilds.join. Loresta adds the verified supporter only to the creator server attached to the paid receipt. The OAuth access token is used for that join request and is not stored. Loresta grants the mapped role only after the receipt and Discord identity are verified.

Role delivery is idempotent. Refunds and disputes reconcile the entitlement and can remove the role.

Troubleshooting Discord

• If no roles appear, move the Loresta bot role above the intended supporter role.
• If publishing fails, confirm View Channels, Send Messages, and Embed Links in the selected channel.
• If one-click joining fails, reconnect Discord from the verified Loresta receipt and retry the private access check.
• If role delivery fails, confirm Manage Roles and the role hierarchy, then run Repair supporter roles from Connections.
• If installation is stale, disconnect and reinstall from Loresta Connections.
• If interactions return HTTP 401, verify the Discord application’s public key and interaction endpoint configuration.