How to sell digital products on Discord in 2026

Why Discord can shorten the digital-product buying journey

The buyer is already in the server. They do not need a new account, a new app, or a marketplace profile. A store that starts with /store, /products, or /buy keeps the decision next to the conversation that created it.

That only works if payment and delivery are the same path. If the next step is a ticket, a manual invoice, and a file pasted in chat, the sale cools off. Cartcord's job is to make PayPal and the DM the next step.

The Problem with Manual Ticket Sales vs. High-Fee Marketplaces

A ticket bot is fine for support. It is a bad cash register. Staff in another time zone, a buyer who closes DMs, and a file dropped in a public channel are how digital stores lose both the money and the file.

A marketplace that takes 5% to 10% solves the queue and then takes a cut of every order, and it often holds the payout. Cartcord charges a flat plan for the server and takes 0% of the sale. PayPal's processing fee still applies. The payment lands in the seller's own PayPal account.

Step-by-Step: Setting Up an Automated Discord Store with Cartcord (/store, /products, /buy)

Invite the bot to a server you manage. Owners and members with Manage Server open the dashboard. Add a product, set the price, and choose file or link delivery. Publish guard stops the product going live if PayPal, the delivery setup, or stock is missing.

Buyers browse with /store or /products and start product checkout with /buy or the public store. Your purchases on the web recovers eligible orders. New recovery and staff commands are rolling out; basket checkout is not released.

Connecting Direct-to-PayPal Payouts (Why Keeping Payment Ownership Matters)

The owner verifies Live PayPal credentials and explicitly attaches the account to each owned store. Cartcord does not hold a platform wallet balance or take sales commission. PayPal fees, holds and fund-availability rules still apply.

That is the difference from a platform wallet. A refund is a PayPal refund you control. A failed DM does not expose the file in the channel. Check payment and delivery separately; eligible paid content can also be recovered through Your purchases.

Automating Instant Delivery for Files, Private Links, Keys, and Roles

File delivery sends the download URL you configured. Basic+ also supports protected managed file versions within the published storage limits. Link delivery sends a private URL. Key delivery takes one unused key from the pool you uploaded. Role delivery grants a Discord role after payment. Optional fixed-duration passes require an available expiry service and do not renew payment automatically. Manual delivery notifies you and the buyer with the instructions you wrote.

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

Commission Breakdown Table: 0% Flat SaaS vs. 10% Marketplace Cuts

Free is $0 for 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, plus coupons, themes, and docs. Enterprise is $129.99 with unlimited products and orders, fraud guard, and signed webhooks.

On a $5,000 month, a 10% marketplace cut is $500 before PayPal. Cartcord Pro is $59.99 and $0 of that $5,000. Use the fee calculator if you want the comparison on your own number.

A worked month for a file store

Take a template shop doing $3,500 in a month at a $35 average price. That is about 100 orders, which fits Basic if you stay under the cap and Pro if you also want coupons and docs. A 10% marketplace cut on $3,500 is $350 before PayPal. Twelve months of that cut is $4,200. Cartcord Pro for the same year is $719.88 and $0 of the $42,000 in sales. The fee calculator on this site uses the same shape of comparison and labels competitor rates as assumptions, not a live quote from those companies.

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.

What the buyer and the staff actually see

The buyer runs /products, picks the file, and approves PayPal. The receipt lands in DMs with the download URL you configured. If their DMs are closed, the order stays pending. You re-send from the dashboard. The link is not pasted into the public channel, which is how a lot of ticket shops accidentally give the file away. Staff with Manage Server can see payment status and delivery status as two different facts, so a captured payment with a failed DM is not treated as an unpaid order.

Publish guard is the check before you go live. It warns you when PayPal is not connected, the delivery URL is missing, or stock you promised is empty. That is the difference between a pretty product card and a store that can finish the order. Coupons and 100% free claims are for launches and creator codes. They do not change the 0% commission on the paid orders that follow.

The operating rules that do not change with the niche

For a file and template store, 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 file and template store. 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 file and template store 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 file and template store 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 file and template store 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.

Write a listing that prevents the first support ticket

A digital product listing should answer four questions before the buyer runs /buy: what arrives, which tools are needed to use it, what rights the buyer receives, and how to request help. For a UI kit, describe the design application and file format, component count, supported versions, and commercial-use terms. For a template, explain whether the buyer duplicates a workspace or downloads a ZIP. Avoid promising lifetime updates unless you have decided how you will distribute them.

Check the exact delivery URL from a separate browser session. A link that works for the creator may require the creator's own cloud-storage login. Confirm that a buyer can access the intended purchase without seeing other customers' files. Keep version notes in one place and put the support contact beside them. A successful payment is evidence that checkout worked; it is not evidence that a private download link is usable. Review both before telling the whole server that the store is open.

A worked platform-fee comparison

This example assumes a $35 average order, a 10% platform commission, and the Cartcord plan required by order volume. Processor fees, taxes, refunds, and product costs are excluded.

Frequently asked questions