Do you host the jar?
No. You supply the download URL. Cartcord sends it after payment.
Direct answer
Sell Minecraft development resources by naming the exact plugin, configuration or original asset, supported server version, dependencies and license. Cartcord can deliver a permitted file or key after verified payment, but it does not install a JAR, verify game-account ownership or execute an in-game command. Review the current Minecraft usage rules for the actual offering, and test installation, recovery and support before publishing the product.
How it works for Minecraft sellers
- 01
Invite the bot
Open the dashboard with Manage Server.
- 02
Publish the product
Review payment eligibility and configure file download, plus an optional support role.
- 03
Buyers use /buy
After payment verification, configured delivery is attempted.
Understand the operating cost
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.
What a buyer would see
- Skyblock core plugin$24.99 · File download, plus an optional support role
- Hub schematic$19.99 · File download, plus an optional support role
What /products shows
Interactive example. This preview does not create an order or charge a payment.
Members open the storefront, choose a product, and start checkout.
Publish a useful compatibility matrix
Name the server implementation and version range you tested, along with the Java runtime, required plugins and database dependencies. A plugin tested on one Paper release should not be described as compatible with every Minecraft server. Distinguish Java Edition server resources from Bedrock add-ons. State whether a proxy, permissions plugin or external service is required, and include the versions that formed your test environment.
Provide a representative configuration and explain how to back up the existing server before applying changes. Show the minimal installation sequence, the expected startup messages and a way to confirm that the plugin is active. If a reload is unsupported, say that a restart is required. A clear rollback path is particularly useful when a resource changes permissions, world data, inventories or database records.
Distribute only the resource you can license
Confirm that you own or are authorized to distribute every included component. A configuration pack may depend on third-party plugins whose JARs should be obtained separately. Include your configuration, documentation and original assets without bundling another developer's paid software or private license key. Explain where the buyer obtains required dependencies and whether those dependencies have their own costs or restrictions.
For an original plugin, describe the permitted number of servers, development instances and client projects. A support license and a resale license are different. If you use Cartcord's optional verification API inside your software, implement the documented signature and binding checks and explain the device or installation policy. Delivering a random key does not automatically make an unmodified plugin recognize or enforce it.
Keep checkout separate from server administration
File delivery sends the configured archive or authorized download. Key delivery assigns an inventory key. A role can provide a separate Discord benefit. These are not an authenticated server agent. Cartcord's direct game-command delivery is not released, so do not promise that buying a resource will automatically install it, add an in-game rank or run an administrative command on the buyer's server.
Do not ask a customer to paste a hosting password, RCON password or server-panel token into an ordinary product form or public Discord ticket. If you sell a manual installation service, define a separately appropriate access and support process. A Minecraft username lookup is not proof of ownership of that account, and a typed player identifier should not be treated as authorization for a privileged server action.
Evaluate the actual monetization rules
Review the current Minecraft usage guidelines for the offering you intend to sell, especially when a resource affects paid server access or in-game benefits. A downloadable developer tool and a paid advantage inside a multiplayer server are different propositions. Do not infer permission from the fact that the checkout can technically accept a payment or another server sells something with a similar name.
Describe your own product and independence clearly. Do not present the store as an official Mojang or Microsoft service. Use demonstrations and screenshots you have permission to publish, identify paid dependencies and keep the permitted-use terms visible. This guide explains Cartcord's delivery boundary; it does not certify every plugin, server monetization model or third-party license as compliant.
Support a real server lifecycle
Test startup, shutdown, restart and an update from the previous version with a disposable server and representative data. Keep backups and a copy of the release being sold. Record compatibility changes and explain whether future game updates are included in the purchase. Avoid promising permanent compatibility with every future release when the platform and its dependencies continue changing.
Ask support customers for an order ID, plugin version, server implementation and a sanitized error excerpt. Avoid requesting entire production logs when they may contain credentials or player information. Reproduce the problem on a minimal environment and distinguish a broken download from an incompatible dependency or server configuration. Use the original order for delivery recovery rather than allocating a new license for every troubleshooting attempt.
A launch checklist you can repeat
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.
Compare the operating model, not just the headline fee
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 |
Compare your monthly cost scenarios
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.
Questions
Can I document the config?
Pro and Enterprise include store docs for install and config notes.
Who gets paid?
Your PayPal account, directly.
Is there a commission?
0% from Cartcord. PayPal processing fees still apply.
How does a buyer start?
/store, /products, or /buy, or the public store page.