Can one store mix files and roles?
Yes. Each product has its own delivery type.
Direct answer
For permitted Rust community offerings, describe whether the buyer receives an original plugin, configuration archive, Discord role or manually fulfilled server benefit. Cartcord can deliver its configured digital product after verified payment; direct Rust commands, Steam ownership linking and automatic in-game provisioning are not released. Check Facepunch's current server and content rules, publish clear fulfillment terms, and test the actual server-side process separately from the payment.
How it works for Rust sellers
- 01
Invite the bot
Open the dashboard with Manage Server.
- 02
Publish the product
Review payment eligibility and configure files, keys, and a one-time discord 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
- Custom monument file$34.99 · Files, keys, and a one-time Discord role
- Queue skip role$10 · Files, keys, and a one-time Discord 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.
Identify the deliverable precisely
A Rust plugin source file, an economy configuration, a Discord supporter role and a live-server package have different delivery requirements. Name what is included and which parts require a server administrator. If the buyer receives a file, list the supported server build, plugin framework and required dependencies. If the offer is a service or server benefit, state who completes it and the expected fulfillment time.
Provide a clean example configuration and instructions for backing up the previous state. Explain whether the resource changes permissions, player inventories, server economy values or persistent data. A screenshot of an in-game benefit is not evidence that purchasing the listing will automatically apply it. Show how the customer or administrator verifies completion and how to recover if a configuration change does not work.
Respect game and content ownership
Review Facepunch's current community-server and hosting guidelines for the exact offer. In particular, do not use a package to bypass ownership of Facepunch DLC or artificially grant content a player has not purchased. A store setting, role or third-party plugin does not create permission to override those ownership rules. Distinguish original server content you can license from platform-owned content and another creator's work.
For a plugin or configuration archive, distribute only components you own or are authorized to redistribute. Identify dependencies that the customer must obtain separately and preserve relevant license notices. Use an accurate independent-store description rather than implying an official Facepunch relationship. If a policy or dependency changes, review affected listings before continuing to advertise the old behavior.
Do not confuse a receipt with an authenticated game action
Cartcord currently supports files, links, stocked keys, Discord roles and manual fulfillment. It does not have a released direct Rust command agent. A delivered key does not run a command, and a Discord role does not prove ownership of a Steam account. If you sell a manual server benefit, staff must follow the published process and record completion rather than marking a DM as proof that the game state changed.
Do not accept a typed Steam identifier as sufficient evidence that the purchaser controls that account. A future integration needs an authorized linking process and server-scoped authentication. Keep RCON passwords and server-panel credentials out of listings, public messages and downloadable examples. Use a separate appropriate administration process for services that need privileged access; ordinary checkout fields are not a credential-sharing channel.
Plan for wipes, restarts and repeat purchases
State how a server wipe affects the benefit. A purchase might apply to one wipe, a fixed period or an untimed entitlement; those terms must match the process that actually grants and removes it. Do not imply that Cartcord automatically reapplies an in-game package after a wipe. Keep records that an administrator can reconcile with the relevant server and player when manual fulfillment is involved.
Test a resource on a disposable server before offering it for production use. Check restart behavior, configuration upgrades, duplicate application and rollback. Maintain a changelog and explain whether later versions or compatibility fixes are included. A repeat purchase should have defined behavior instead of accidentally stacking a benefit or removing a previous valid entitlement. Separate product updates from new paid access.
Handle support and refunds with the right evidence
Publish a support route and ask for the order ID, resource version and a sanitized description of the problem. Inspect payment and delivery state separately. A paid order can have a failed DM; a successful download can still require installation help. Re-send the existing configured delivery when appropriate instead of asking the buyer to pay again merely to recover a missing message.
When a refund changes eligibility, explain which digital access can be closed and which server-side work still needs an administrator. A stored delivery event does not prove a particular Rust inventory or permission changed. Review the safe evidence export alongside relevant server records and support history, and avoid including unrelated player information or administrative credentials in a dispute response.
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
Does the role expire?
Untimed roles remain until removed. Optional timed passes require an available expiry service and explicit setup; check the recorded product terms before purchase.
Is Cartcord a game host?
No. It sells and delivers. It does not run the Rust server.
How do refunds work?
You handle the PayPal refund. Cartcord does not hold the funds.
Which plan is the best value?
Pro at $59.99 a month for stores that need coupons, themes, and docs.