How to sell Minecraft plugins and configs on Discord

Why Minecraft Developers and Setup Studios Sell Inside Discord

The buyer is in the server asking about Paper versions and config flags. A store command is closer than a marketplace listing.

Automating JAR, ZIP, and License Key Delivery After PayPal Checkout

File delivery sends your download URL after PayPal capture. Basic+ can store a protected file version within the file/store size limits. Key delivery is there if each buyer needs one unused license.

Granting Verified Customer Roles for Plugin Support Channels

Sell a separate one-time role if customers should see a support channel. The bot has to be above that role or the grant fails.

Hosting Plugin Configuration and API Documentation Using Store Docs

Pro store docs can hold the config and update notes. Buyers read them instead of asking the same install question.

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

A plugin sale is a file, a key, and a support role

Spigot and Paper jars, schematic ZIPs, and config packs are files you host. Cartcord attempts the selected delivery after PayPal capture. Choose one delivery engine per product: a file URL, a stocked license key or a configured role. A single purchase does not automatically combine all three. Untimed roles have no configured expiry. Timed passes require an available expiry service and explicit setup. Verified full refunds can queue eligible Cartcord-owned role removal, subject to worker availability and other valid grants. It is not buyer recurring billing. Store docs, on Pro and Enterprise, are the place for the config keys and the API notes, instead of a pastebin that you update in three channels.

Minecraft buyers already live in Discord. A marketplace account is an extra signup and a cut. Your PayPal is the payout. At a $25 plugin and 100 orders, that is $2,500. A 10% cut is $250. Basic at $29.99 covers 100 orders if you do not need docs yet. Pro at $59.99 is the step when the docs and the coupon for a launch matter.

Keep the jar off the public channel

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. If the DM fails, the order stays pending and you resend. Do not drop the JAR in general because the buyer said they cannot find it. That is how a paid plugin becomes a free one. Publish guard is there so you do not list the plugin before the URL or the key pool exists.

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 Minecraft plugin shop, 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 Minecraft plugin shop. 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 Minecraft plugin shop 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 Minecraft plugin shop 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 Minecraft plugin shop 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.

Publish a reproducible compatibility and upgrade checklist

A plugin buyer needs more than a download button. List the supported Minecraft versions, server implementation, Java version, required dependencies, and known conflicts. For a configuration pack, say which plugins are included and which must be purchased separately. For a schematic, state the format and the tools used to import it. Do not redistribute another developer's paid JAR simply because your server setup depends on it. Describe exactly what your license permits the customer to install or modify.

Write an upgrade path that starts with a backup and names the files that should be replaced. Show a minimal configuration example and explain any new database migration or permission node. Test the steps against a clean staging server, then record the product version and date in the documentation. A paid customer role can make the support channel easier to find, but it does not verify that the buyer's server environment matches your test environment. Ask for relevant version information and redacted error logs when investigating a report. Never require a customer to publish database credentials or a full server configuration containing secrets.

Frequently asked questions