Sell files, templates, and downloads inside Discord. Buyers pay your PayPal. Cartcord delivers the file and takes 0% of the sale.
To sell digital products on Discord, prepare a clear product listing, connect your seller PayPal account, and configure the file or link buyers should receive after payment. Cartcord supports purchases from Discord and a public storefront, with delivery attempted after payment confirmation. Choose protected uploads when appropriate, test recovery from the buyer account, and publish your license, support and refund terms before launch.
Invite the bot
Open the dashboard with Manage Server.
Publish the product
Review payment eligibility and configure file links and private urls after confirmed payment.
Buyers use /buy
After payment verification, configured delivery is attempted.
Choose by the actual product, audience and services you need. Cartcord's plans are Free $0, Basic $29.99, Pro $59.99 and Enterprise $129.99 per month. Cartcord charges no sales commission; PayPal processing and other merchant costs remain separate. A marketplace may provide discovery, billing, hosting or tax services that a flat Discord-store plan does not.
Interactive example. This preview does not create an order or charge a payment.
Members open the storefront, choose a product, and start checkout.
Start with the outcome and the deliverable. A design bundle might contain editable source files, exported examples and a short installation guide. A spreadsheet might include sample data, assumptions and a clean starting copy. Put these details in the listing so the buyer can distinguish a complete product from a screenshot or a promise of future work. State the application, version and paid dependencies required to open it.
Build the delivery archive from a clean folder. Remove personal documents, development credentials, customer examples and temporary exports. Use descriptive filenames and a version number. Open the archive on another account or device and follow your own instructions. If the guide depends on a permission you granted yourself, a buyer may encounter an access request immediately after paying. Resolve that before publishing.
A file product can send a configured download URL. That is convenient for an existing hosting service, but the receiving service controls availability and sharing permissions. A link product is useful when the deliverable is a private resource rather than an archive. A manual product sends instructions for work that still needs a human. Select the method that matches the actual fulfillment process instead of labeling every order instant.
Protected uploads are a separate option on eligible plans. The optional download vault streams an uploaded file through a single-use link with a time limit and additional network binding. It does not protect an external URL or stop a buyer from copying downloaded content. Explain the recovery path: a buyer whose network changes can request a fresh eligible link through Purchases using the same Discord account.
Personal use, commercial use, client work and redistribution are different rights. Describe which rights the price includes, whether a team can share the files, and whether the buyer may incorporate an asset into a finished product. If a product includes third-party fonts, photographs or sample code, confirm that your license permits distributing them. A checkout receipt does not create rights you did not own.
Distinguish product updates from support. You might include fixes for the purchased major version, offer a limited support period, or sell later releases separately. Say which arrangement applies and identify the support channel. Avoid an undefined lifetime promise if you cannot explain what happens when the product or your business stops operating. Buyers need a concrete commitment they can retain with their order.
Keep a hidden draft while you check the title, price, preview and delivery destination. Use a separate buyer identity for the permitted test flow, then inspect the resulting order and delivery state. Confirm that the buyer can find the purchase again, and that re-sending delivery does not create a second charge. A successful screenshot of the seller dashboard is not a complete checkout test.
When you replace a file, keep a release note and a rollback copy. Describe whether past buyers receive the current version or the version they purchased, and check that policy against the configured asset behavior. If a buyer reports a broken archive, ask for the order ID and application version rather than asking them to post a private link in a public channel. Record a useful resolution for future buyers.
Separate the Cartcord plan from payment processing, hosting, taxes and the time you spend on support. A zero Cartcord sales commission does not make the transaction cost zero. Model a low-volume month as well as a strong launch, and stay within the product and order limits of the plan you choose. Discounting a product may increase the number of support requests without increasing the resources available to answer them.
After launch, look for repeated compatibility questions, failed deliveries and refund reasons. Improve the product page where a missing explanation caused confusion. Use genuine product demonstrations and an original description rather than filling the listing with loosely related keywords. A smaller catalog of maintained products with clear ownership and reliable recovery is more useful to buyers than many interchangeable pages.
Start from a hidden product and review it as a buyer: name, current price, included deliverables, dependencies, access duration, license and support contact. Connect the seller payment account for the intended store and verify that the selected product can be published. Use a genuine preview of your work. Remove test data, private credentials and unlicensed material before adding the delivery destination.
Run an authorized checkout test with an identity that represents a buyer, then inspect both the payment result and fulfillment result. A browser return page is not evidence of a captured payment by itself. Exercise purchase recovery and a delivery retry. Before announcing the product, keep a record of the terms, the version being sold and the recovery instructions your staff will give a customer.
Manual ticket selling can suit occasional custom work, but staff must reconcile each payment and fulfill each promise. A percentage marketplace may include discovery, billing, tax or hosting services you would otherwise operate. Cartcord's flat server plan and direct seller PayPal checkout serve a different workflow. Calculate the cost of the features you actually need instead of treating every percentage or subscription as interchangeable.
Include payment processing, currency conversion, hosting, refunds and support time in the comparison. Cartcord taking zero sales commission does not remove those costs or make Cartcord the merchant of record. Check the current plan's limits and provider eligibility for your particular product. Choose the route that meets the buyer's delivery and recovery needs at the volume you can realistically support.
| Responsibility | Manual ticket workflow | Cartcord released workflow |
|---|---|---|
| Payment confirmation | Staff reconcile the correct merchant transaction | Provider confirmation is checked before configured delivery |
| Fulfillment | Staff send the resource or complete the promised service | Configured file, link, key or role delivery is attempted; manual work still needs staff |
| Recovery | Staff locate the purchase and determine what was delivered | Original-account purchase recovery and recorded delivery results help investigate failures |
| Cost | Account for processor charges, tools and staff time | Account for the store plan, processor charges, hosting and support |
Enter your actual fees. These are editable USD scenarios, not provider quotes. Include processor charges in both scenarios. Compare equivalent services and permitted products; required platform checkout still applies.
Enter every fee, including zero where applicable. Use non-negative amounts, whole orders and percentages up to 100.
Taxes, refunds, disputes, conversion, payout and support costs need separate review. Cartcord sales commission is 0%; the store plan and processor costs remain.
You can use your own download URL. Basic and higher plans also support private managed uploads within storage limits, with signed links or an optional single-use vault. Delivery is attempted after payment confirmation; authorized buyers can recover eligible content through Your purchases.
Only /store, /products, and /buy. There is no separate cart command.
The seller's own PayPal account. Cartcord does not hold the money.
Cartcord takes 0% of the order. You pay a flat server plan. PayPal's own processing fee still applies.
The order stays pending. You re-send delivery from the dashboard after they open DMs. The link is not posted in the channel.