Can buyers get an install guide?
On Pro and Enterprise you can publish store docs for setup steps. Cartcord does not install the script on the buyer's server.
Direct answer
Plan FiveM sales around the required checkout and licensing system first. Cfx.re identifies Tebex as its exclusive server-monetization partner; Cartcord does not replace that checkout or Asset Escrow. Discord can still organize documentation, product questions and support. Before offering any independently sold resource, verify its rights and platform eligibility, describe compatibility and delivery precisely, and avoid promising an automatic game integration that has not been released.
FiveM and Cfx.re monetization requirements
Cfx.re identifies Tebex as its exclusive FiveM server monetization partner. Cartcord does not replace required Tebex checkout, Cfx licensing, or Asset Escrow. Use Cartcord only for offerings whose licenses and platform rules permit independent PayPal checkout.
Read the official FiveM monetization documentationPreview the customer support handoff
Planning example; no order, payment or game action is created.
Use the checkout required by Cfx.re and the actual product. Cartcord does not replace required Tebex payments.
Begin with the checkout requirement
The first question is whether the exact product belongs to the FiveM monetization workflow governed by Cfx.re's requirements. The official documentation identifies Tebex as its exclusive server-monetization partner. Do not choose an alternative PayPal checkout merely because another service advertises a lower commission. A payment button cannot override the platform's rules or create a license for an asset that the seller is not permitted to distribute.
Keep required Tebex checkout and platform entitlement management in the required system. Cartcord is not presented here as a bypass. Discord documentation and customer support can complement a permitted commerce workflow without becoming a replacement payment channel. If a separate offering may be independently sold, confirm its actual rights and eligibility before creating a Cartcord product; do not infer permission from a broad label such as digital download.
Write a compatibility specification buyers can verify
For an original resource, document the tested server artifact, framework and dependency versions. QBCore and ESX compatibility are not interchangeable promises, and a standalone script may still depend on an inventory, database driver or shared library. List each requirement, identify whether it is included or obtained separately, and explain the tested environment. An attractive showcase should not hide a dependency that materially changes the purchase cost.
Describe supported configuration options and the limits of customization. State whether the buyer receives editable source, an escrow-protected resource or documentation for a separately licensed component. Give an installation sequence, the expected startup state and a rollback process. Keep private server addresses, database passwords and development credentials out of examples. A useful compatibility note lets a buyer identify a mismatch before paying rather than after a failed installation.
Separate file delivery from asset entitlement
A downloadable archive is not the same thing as an entitlement recognized by Cfx.re or Asset Escrow. Copying a file or issuing a random key does not automatically authorize a resource on another server. Follow the actual licensing and transfer process required by the product. Cartcord's stocked key delivery and optional signed license API are separate mechanisms and do not replace a platform-owned entitlement system.
Do not describe Cartcord as installing a resource, spawning an item or granting a vehicle after a FiveM purchase. Direct game-server command delivery is not released. A DM containing a link proves neither installation nor the intended game-state change. If an approved external integration handles those actions, document that integration truthfully and test it through the permitted provider rather than attributing its capabilities to an unrelated delivery preset.
Use Discord for documentation and support
Discord is useful for compatibility questions, release announcements, known issues and troubleshooting. Organize an installation guide by the task the buyer is trying to complete: dependencies, resource configuration, database changes, server start order and verification. Keep a public overview free of secrets, and place genuinely private customer material in an appropriate authorized support process. A long pinned chat thread is difficult to maintain as versions change.
Where a separately permitted Cartcord offer uses store documentation, eligible plans can publish those guides on the storefront. The documentation feature does not validate a FiveM license or install software. Explain which system handles payment, which system controls the entitlement and where the buyer asks for support. Keeping these responsibilities explicit helps staff investigate an issue without sending the customer between unrelated dashboards.
Maintain release and installation evidence
Keep a versioned release archive and changelog. Test a new version on a disposable environment before advising customers to update a live server. Record any migration that changes database tables, persistent inventories or configuration keys. Provide a backup and recovery process appropriate to those changes. A successful fresh installation is useful evidence, but it does not show that every existing customer can upgrade without reviewing their own configuration.
Ask support customers for the purchase reference from the correct provider, the resource version, framework version and a sanitized error. Request the smallest useful excerpt rather than a full production log that may expose credentials or player information. Distinguish an unavailable download from a platform-entitlement failure, dependency mismatch or local server error. Each problem has a different owner and should not be resolved by asking for another payment.
Review original work and redistribution rights
Confirm that models, textures, audio, scripts and dependencies can be distributed under the terms of the actual offering. A component appearing in a server showcase does not establish that it can be included in a commercial archive. Identify third-party material the customer must obtain independently, preserve applicable notices and avoid implying that your store is an official Cfx.re or Rockstar service.
State the permitted server count, transfer policy, support period and update policy when those terms apply. Align the listing with the license and the provider's fulfillment process. Avoid undefined lifetime promises or guaranteed compatibility with future framework releases. Review the offer again when a platform policy, dependency or ownership requirement changes instead of relying on an old product page as proof of continuing permission.
Compare service arrangements fairly
A checkout provider may include platform-specific entitlements, supported game integrations, dispute handling or other services that a generic digital storefront does not supply. Compare those responsibilities alongside price. Cartcord's flat plan and zero Cartcord sales commission apply only to its permitted offerings; payment processing and the seller's other obligations remain. That pricing statement is not a reason to bypass a mandatory commerce channel.
For a legitimate independently sold resource, perform a controlled acceptance test of the actual payment, configured delivery and recovery path before moving new sales. Retain previous purchase records and support obligations. Do not claim that importing product text transfers old customers, active subscriptions or platform licenses. If the required technical or platform capability is missing, keep the working approved workflow rather than advertising a replacement that cannot fulfill it.
| Responsibility | Required provider or seller action | Cartcord scope |
|---|---|---|
| FiveM monetization | Use the required Tebex checkout and follow current Cfx.re rules | This guide does not provide an alternative FiveM payment route |
| Game entitlement | Use the supported provider and game-platform entitlement mechanisms | A Discord login does not verify a FiveM account or license |
| Installation and support | The seller documents dependencies, supported versions and recovery steps | Discord can host seller instructions and support discussions |
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 Cartcord replace required Tebex checkout?
No. Cfx.re identifies Tebex as its exclusive FiveM server monetization partner. Cartcord cannot bypass that requirement or Asset Escrow. Independent checkout is suitable only where the specific product's license and platform rules permit it.
How is a script delivered?
Use the delivery and entitlement workflow required by the specific resource and its platform. Cartcord does not replace required Tebex checkout, Cfx.re licensing or Asset Escrow.
Can I sell a role with the script?
A Discord support role does not transfer a Cfx.re entitlement or create permission for an alternative checkout. Keep required payments and licensing in their approved systems, and verify eligibility before independently selling any separate offering.
What if DMs are closed?
The order stays pending until you re-send from the dashboard.