Does Cartcord take a percentage of sales?
No. Cartcord charges a flat server plan and 0% of the order. PayPal's processing fee still applies.
Cartcord versus Tebex
Tebex provides game commerce for supported ecosystems. Cartcord provides configured Discord delivery and independent seller PayPal checkout only for permitted offerings. FiveM's required Tebex checkout and Cfx.re licensing are not replaced, and Cartcord's game-server command engine is not 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 documentation| Area | Cartcord | Tebex |
|---|---|---|
| Primary workflow | Discord storefront and five configured digital delivery methods | Game commerce and integrations for supported platforms |
| FiveM eligibility | Does not replace required Tebex checkout or Cfx.re licensing | Cfx.re identifies Tebex as its exclusive server monetization partner |
| Published platform pricing | Flat Cartcord plan; PayPal and other merchant costs are separate | Tebex documents 15% for FiveM and 5% for other games, plus applicable plan/payment terms |
| Game commands | No released game-server command delivery | Evaluate Tebex's documented integration for your platform |
| Independent digital goods | Use only when product rights and platform rules permit | Choose the checkout required by the specific ecosystem |
Establish platform eligibility before comparing cost
For FiveM server monetization, the official Cfx.re documentation identifies Tebex as the exclusive partner. Cartcord does not offer an alternative-payment bypass for that requirement. A lower displayed fee would not make an otherwise prohibited checkout suitable. Start by identifying the exact product, applicable license, required checkout channel and any asset-entitlement system that controls delivery.
Other ecosystems have their own rules and technical requirements. Selling a permitted downloadable configuration is different from granting a rank, issuing game currency or unlocking a platform-owned asset. Confirm the actual offering before selecting a payment and delivery system. The comparison here describes workflows; it does not establish that every game-related product can be sold through independent PayPal checkout.
A file delivery is different from an in-game effect
Cartcord can attempt a configured file, link, key, Discord-role or manual delivery after verified payment. Sending a plugin archive does not install it on a customer's server. A Discord support role does not prove ownership of a Minecraft, Steam or Roblox account. A manual instruction does not become an authenticated game command merely because it appears in a product preset.
If automatic in-game delivery is essential, evaluate the provider's supported connector, account-linking method, offline-player behavior, retry handling and refund policy. Cartcord's direct game-server command engine is not released. Keep a working permitted integration rather than replacing it with a download or DM that cannot perform the promised side effect. Test the server behavior separately from the payment result.
Compare equivalent responsibilities
Tebex's published plan documentation distinguishes platform percentages, optional paid-plan features and other payment terms. Cartcord has a flat store plan with zero Cartcord sales commission, while PayPal processing and the seller's other obligations remain. These are different service arrangements. Model the payment method, volume, taxes, disputes, hosting and integration work you would need under each option.
A sensible migration begins with products that are both permitted and technically supported by the destination. Retain original purchases, licenses and support records. Do not transfer platform entitlements by copying a CSV, and do not treat Cartcord's key inventory as a replacement for Asset Escrow. Use Discord documentation and support alongside required checkout where that is the correct arrangement.
Map each product to its actual fulfillment system
Make an inventory of what the customer receives: an archive, an asset entitlement, a persistent server rank, a consumable item or a manually delivered service. For each item, record the system that can create and remove that benefit. A downloadable server configuration may need ordinary file support, while an in-game effect needs an authenticated integration that understands the server and the player's identity. Keep required platform checkout and licensing attached to the relevant product instead of treating the entire game community as one interchangeable catalog.
For a FiveM offer, review the official monetization requirements before designing links or commands. A Discord support page can explain a resource without replacing its required purchase channel. Cartcord's command-template tool is an administration aid; it does not verify a Tebex purchase, establish account ownership or deliver a paid game benefit. Never make a buyer type an arbitrary player name and assume that proves entitlement. The decision about payment eligibility comes before any comparison of commission or monthly plan cost.
Ask concrete questions about game-side reliability
When reviewing a game commerce integration, ask what happens if the server is offline after payment, if the player changes a display name or if the same event is delivered twice. Request the documented identity format and the behavior for a player who has never joined. A reliable connector needs an explicit retry and duplicate-handling model. These questions are evaluation criteria for the provider you select; they are not claims that Cartcord currently supplies a direct game connector.
Refunds require equally specific treatment. A removable permission, a downloaded archive and a consumed inventory item have different reversal limits. Removing a Discord support role cannot undo every game-side effect. Write down the scope of any promised revocation and explain when manual review is necessary. Keep the original payment reference and delivery evidence so support can investigate a disputed order without improvising a replacement entitlement. Test permitted administrative examples on a development server before using them around real players or valuable inventory.
Plan a complementary Discord storefront carefully
Some communities have independent, permitted digital goods alongside products that must remain on an ecosystem-specific checkout. Describe the separation clearly in navigation and product copy. A documentation archive, original artwork or a permitted support product should say exactly what it includes and which rights the seller can grant. Do not use a vague bundle name to imply an asset license, game currency or privileged access that the actual delivery method cannot provide. Keep required licensing and purchase links discoverable to the buyer.
Budget for the work that remains with the operator: maintaining downloads, verifying compatibility, answering installation questions and applying updates. Compare like-for-like responsibilities when deciding whether a flat Cartcord plan is useful for those independent goods. Keep game integration costs and required Tebex charges attached to the workflow that uses them. The practical outcome can be two coordinated systems with clear responsibilities. There is no need to label a Discord storefront a universal Tebex replacement when the product and platform requirements call for different tools.
Sources and comparison assumptions
Checked on October 24, 2026. Plans, eligibility and fees can change. Compare your actual payment method, order count, taxes, hosting and support requirements. Cartcord's zero sales commission does not remove processor costs or make Cartcord the merchant of record.
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
Who receives the buyer's payment?
The seller's own PayPal account. Cartcord does not hold the funds.
Which commands do buyers use?
Only /store, /products, and /buy.
Are paid roles a subscription?
Role payments are one-time. Optional timed passes require a ready expiry service; new timed setup is blocked while it is unavailable. Recurring buyer billing is not released.
How should I choose a plan?
Choose by your actual product count, order volume and required features. Review the current pricing table and include payment processing and support costs in the comparison.