How to sell paid Discord roles with PayPal

Best Communities for Paid Discord Roles

Signals rooms, coaching cohorts, supporter perks, and private beta channels already live in Discord. Start by deciding whether you promise one-time access or a recurring membership. Your billing and role-delivery workflow must match that promise.

Cartcord grants the role after PayPal capture. Optional timed access requires a live expiry service; setup is blocked while that service is unavailable. A pass is paid once and does not bill the buyer every month.

How Automatic Role Assignment Works After PayPal Capture

The buyer runs /buy, pays your PayPal, and the bot assigns the role you configured. The bot must be above that role in Server Settings. If it is below, the grant fails and the order stays pending.

Check bot hierarchy, membership and delivery results, then retry the existing order if appropriate. A refund request still needs the seller's review.

Why Percentage Fees Hurt High-Ticket Role Communities

A $99 role with a 10% platform fee pays $9.90 to the platform before PayPal. Fifty of those a month is $495 gone. Cartcord Pro is $59.99 for the server and $0 of each role.

Your Cartcord subscription is the only Cartcord charge. It is not a cut of the role.

Step-by-Step Guide to Launching Paid Roles Using Cartcord

Create a role product, paste the role id, set a one-time price, and connect PayPal. Tell buyers to use /store or /buy. On Pro you can add a coupon for a launch or a 100% claim for a comp.

Written by the Cartcord team that builds the Discord store bot, PayPal checkout, and delivery pipeline.

A role sale is a one-time grant

Cartcord grants the role after PayPal capture. You can leave access untimed. A fixed-duration pass can be configured only when the expiry service is available. Hide it and finish active checkouts before changing the duration. The buyer sees the duration before checkout, and the paid order keeps a snapshot so later edits cannot shorten an existing pass. The bot queues expiry and, for longer passes, a reminder three days before expiry. It preserves pre-existing access and other valid grants. A re-send repeats delivery; it does not renew an expired pass. This is a one-time payment, so describe a seven-day pass as a seven-day pass rather than an automatically renewing weekly subscription.

Percentage platforms hurt role communities because the fee is taken on every high-ticket payment. A $99 signal role on a 10% cut is $9.90 gone before PayPal. Cartcord's fee is the flat plan for the server. The $99 lands in your PayPal, minus PayPal's processing fee. Coupons and free claims are how you open a launch or an influencer code without inventing a second store.

Who should be allowed to manage the role store

Buyers browse and start checkout with /store, /products and /buy; web purchase recovery is available through Your purchases. There is no cart command and no extra checkout command. They can also open the public store URL. After PayPal captures the payment, delivery is a file link you host yourself, one unused license key from your pool, a private URL, a Discord role granted once, or a manual order that stays pending until staff act. Optional timed passes require an available expiry service; payments do not recur. Basic+ supports private uploads with short-lived signed links or optional 24-hour single-use downloads within the published storage limits. Manage Server is the permission that opens the dashboard. You do not hand the PayPal password to moderators. They can resend a delivery or read an order if you give them the Discord permission the dashboard already trusts. Each server has its own plan, so a second community does not spend the first server's order quota.

Plans stay server-wise. Free is $0 with 3 products and 3 orders a month, which is enough to prove one offer. Basic is $29.99 with 25 products and 100 orders. Pro is $59.99 with 150 products, 1,000 orders, coupons, themes, and store docs, and it is the plan most active stores should use. Enterprise is $129.99 with unlimited products and orders, fraud guard, and signed webhooks. None of those prices is a percentage of the sale. PayPal's own processing fee still applies, and Cartcord does not hold the payout.

The operating rules that do not change with the niche

For a one-time paid role, the sale is finished only when PayPal has captured the payment and the delivery you configured has been sent. Cartcord takes 0% of that order. The monthly cost is the server plan, not a slice of revenue. PayPal still charges its processing fee, and that fee is between you and PayPal. Cartcord never holds a balance you later withdraw, so Cartcord does not impose a wallet payout schedule; PayPal can still apply fees, holds or account restrictions.

Keep the command list short when you announce a one-time paid role. Members run /store to see the shop, /products to browse, and /buy to pay. They can also use the public store URL, which is the address a person outside the server, and a search engine, can open. Do not invent a cart command. Do not ask them to open a ticket to pay for something the bot can already deliver. Tickets stay for support and for the rare order you marked as manual.

Delivery for a one-time paid role is one of five setups. A file uses an external URL or a Basic+ protected managed version. Managed uploads allow 25 MiB per file and 250 MiB reserved storage per store. A license key is one unused line from the pool, and a resend repeats that same line. A private URL is a link. A role is granted after capture. Optional timed passes require a live expiry service and are paid once, without recurring billing. A manual order stays pending and pings staff with the buyer details and the instructions you wrote. Publish guard is what stops the product going live while PayPal, the delivery, or the stock is missing.

Pick the plan from the order count, not from a feeling about the niche. Free covers 3 products and 3 orders a month. Basic is $29.99 for 25 products and 100 orders. Pro is $59.99 for 150 products and 1,000 orders, and it adds coupons, themes, store docs and scoped merchant API keys. Enterprise is $129.99 when you need unlimited volume, fraud guard, and signed webhooks. The example of 10% on $5,000 is a $500 scenario input, not a statement of any vendor's current rate. Pro is $59.99 and none of the $5,000. Use the fee calculator for your own sales number, and read pricing before you promise a buyer a feature that sits on a higher plan.

When a one-time paid role is live, check three things after the first real payment. The PayPal capture should show on the order. The delivery status should show sent, or pending if the buyer's DMs were closed. The public store URL should be the same shop the commands show, so a member who shares the link is not sending people to an empty page. If a name looks like a test, a demo, or a sandbox, or the shop has no products, that storefront is noindex and stays out of the sitemap. A real shop with products can be indexed. From any of these guides you can open pricing, the fee calculator, and the solution pages linked under the article.

A clean launch for a one-time paid role is a short announcement, not a new website. Name the server, list the three products with their prices and whether the buyer receives a file, a key, a link, or a role, and tell them the commands. The announcement generator on the tools page drafts that message. The fee calculator puts a percentage marketplace next to the flat plan so the owner can see the year, not just the first sale. Pricing is the page that states Free, Basic, Pro, and Enterprise without a sales adjective doing the work. Those three links are the next step after this article, and they are the same facts the rest of the site is willing to stand behind.

Buyer recovery, refunds and feature boundaries

Use Your purchases with the original Discord login to recover eligible content. A paid order can have failed, pending or held delivery. Fix the underlying issue and retry the existing order instead of charging again. Basic adds protected file versions, Pro adds API keys for product/order reads and non-key stock updates, and Enterprise adds risk review and signed webhooks.

The merchant issues refunds in PayPal. Verified completed partial refunds preserve access; cumulative full refunds close new delivery access and queue eligible saved role removals through the scheduled access service. New recovery/staff bot commands still have a separate rollout. Existing signed links and downloaded copies cannot be universally recalled. Signed license verification with device limits is available only after developer integration. Optional single-use downloads protect managed uploads, not external URLs. Timed passes require a ready expiry service and are blocked for new setup while it is unavailable. Pro+ creator referrals issue store coupon rewards after qualifying paid delivery; they do not create cash balances or automatic payouts. Basket checkout, component bundles, recurring buyer billing, seller Stripe/crypto checkout, game-server command delivery and automatic booking are not released.

Decide the access policy before naming the role

A one-time role grant and a recurring membership are different promises. Cartcord's role delivery grants the configured Discord role after payment. Do not advertise a monthly renewal, automatic expiry, or scheduled removal unless you operate a separate system that supplies those behaviors. Label a supporter purchase as one-time access when that is what the buyer receives. If you manually review access later, explain the policy in plain language before checkout.

Test permissions with an account that has no staff privileges. Confirm that the purchased role reveals the intended channels and does not inherit moderator powers. Check that the bot's highest role sits above the role it must assign, and avoid targeting managed integration roles. If delivery fails, inspect hierarchy and membership before re-sending the existing order. A support message should identify the affected order and the promised role without asking the buyer for their PayPal password. Document refund and access-removal decisions separately; a payment record and a Discord permission change are related operational events, not the same database status.

Frequently asked questions