How to sell license keys on Discord automatically

Why Manual DM Key Fulfillment Kills Software and Script Businesses

Pasting a serial in a ticket works for the first ten buyers. It fails when two staff reply, when a DM is closed, or when the same key is copied twice. The buyer thinks they were cheated. You think the stock is fine.

A key product in Cartcord is a list you upload. A captured PayPal order removes one unused key and sends it to that buyer.

How Automated License Key Stock Pools Work in Cartcord

Each paid order takes one unused key. If you re-send because DMs were closed, the buyer gets the same key again. Re-send does not mint a new license.

An empty pool should not promise a key. Publish guard is there so you do not go live without stock.

Step-by-Step Setup: Uploading Single-Use Activation Keys and Serial Numbers

Create the product, choose license key delivery, paste the unused keys, set the price, and connect PayPal. Buyers start with /buy or the public store page.

Payment goes to your PayPal. Cartcord takes 0% of the order.

Preventing Stockouts with Publish Guards and Order-Level Tracking

The dashboard separates payment status from delivery status. You can see who paid, who received the key, and who is still pending because Discord blocked the DM.

Docs on Pro give buyers the activation steps so they do not open a ticket for the install.

Enterprise Webhooks and Fraud Guard for High-Volume Key Sellers

Enterprise adds signed webhooks and fraud guard. Use them when key sales are large enough that a bad order should be reviewed before delivery, not after the key is already out.

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

How a key pool behaves on a real order

You upload unused keys. A paid order takes one of them and sends that exact key in the DM. A re-send repeats the same key. It does not mint a second key and it does not pull the next line from the pool. That matters when a buyer says they lost the message: you can resend without burning stock. When the pool is empty, publish guard should stop you promising a key you do not have. The public channel never receives the key.

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. 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. Enterprise adds fraud guard and signed webhooks for stores that need an outside system to hear about the order. The webhook is a notification. It is not a second cash register, and it does not move the PayPal money.

Docs cut the support queue after the key is sent

A key without install steps becomes a ticket. Pro and Enterprise include store docs, so the activation steps, the HWID notes, and the changelog live on the store instead of in a pinned message that goes stale. The buyer still paid you directly. The doc page is there so they can use the key without waiting for someone who is asleep.

Manual fulfillment is the wrong default for serials. Use it when a human has to check a machine or a ban list before the key should leave the pool. For ordinary software and script keys, the pool plus /buy is the whole path. Staff hours stop being the fulfillment system.

The operating rules that do not change with the niche

For a license-key pool, 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 license-key pool. 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 license-key pool 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 license-key pool 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 license-key pool 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.

Separate stock delivery from software activation

A key pool distributes strings; it does not implement the licensing server for your application. Your software still needs its own activation checks, expiry rules, device limits, and revocation process. Cartcord can deliver an unused key after a captured payment, but a thirty-day license works only if your licensing system enforces that duration. State those limits in the product description so a buyer understands whether the purchase is perpetual, timed, or tied to a device.

Before importing stock, remove duplicate lines and check that the keys belong to the advertised product and environment. Keep development keys separate from production stock. After a test purchase, verify the delivered key against the activation service and record which product version was tested. When a customer reports an activation problem, use the existing order and its assigned key to investigate. Sending a new key before checking the original can consume inventory while leaving the first key active. Do not paste unused stock into a public support channel or attach a complete key list to a customer invoice.

Frequently asked questions