Cfx Marketplace vs Tebex vs Direct: How FiveM Script Buying Channels Work

Three channels, one payment rail underneath

Every legitimate FiveM script purchase you'll make in 2026 lands in one of three places. The Cfx Marketplace (marketplace.cfx.re) is the official, curated storefront Cfx.re launched in January 2026 — listings there are reviewed by the Cfx team before they go live, and browsing is free; you pay only for what you buy. A seller's own Tebex storefront is the same underlying commerce and delivery system without the Marketplace's curation layer — many established vendors sell this way, predating the Marketplace and continuing alongside it. 'Direct' is everything else: a seller offering to take your payment some other way.

The distinction that actually matters is narrower than it looks, because two of the three channels are the same rail wearing different storefronts. Per Cfx's own platform documentation, Tebex is described as the exclusive monetization partner for FiveM and RedM, and using another payment provider for that monetization is stated to violate the Platform License Agreement (docs.fivem.net; fivem.net/terms). Separately, Cfx's own asset-escrow documentation states that escrowed assets can only be distributed via a Tebex package — there is no other supported delivery path for encrypted resources. Put together: a 'direct' sale of an escrowed script isn't a backdoor discount, it's a transaction the platform's own rules and the delivery mechanism itself don't support. Where a specific policy detail isn't covered above, the authoritative source is docs.fivem.net, not this page.

What escrow protects, and what it doesn't

This isn't the place to re-explain how Cfx asset escrow works mechanically — that's covered in full at /guides/fivem-asset-escrow-explained. What belongs here is narrower: what buying an escrowed asset through a legitimate channel actually buys you, and what it doesn't.

Escrow protects the seller's code from being copied, edited, or resold — that's its entire purpose, and channel-legitimate delivery (Marketplace or Tebex) is what makes the protection function, since your license binds to your Cfx account through the keymaster system. What escrow does not do: it doesn't verify the code is fast, doesn't verify it's secure, doesn't verify the seller will still be around in a year, and doesn't give you any way to confirm a performance or security claim yourself. A legitimate purchase channel protects the transaction. It says nothing about the product.

Open config vs closed logic — reading a listing before you pay

Whichever channel you buy through, the same question decides how much of the product is actually yours to control: which files ship open and which ship escrowed. A listing that states this at file level — locales here, config here, core logic there — is giving you a real answer. A listing that says only 'fully configurable' is giving you an adjective. Ask for the split before paying, on either the Marketplace or a direct Tebex store — the channel doesn't change what you're entitled to ask.

This is also where licensing terms live, and they're worth reading before checkout rather than after a dispute: what a purchase actually grants (typically one license per community, no redistribution), what happens on refund or chargeback, and what counts as a version update versus a paid upgrade. Read the seller's specific terms — ours are at /legal/license — because they can vary by vendor even though the delivery mechanism underneath is the same.

Update delivery, support, and what to expect after you pay

Because delivery for escrowed assets is bound to your Cfx account through the keymaster system, updates typically arrive the same way the original purchase did — through your account, not a separate download link that can go stale. That's a genuine channel benefit: you're not relying on a seller's file host staying online.

None of this replaces vetting the seller's actual support behavior, which is a different question from the channel they sell through. A written response-time SLA, a dated changelog, and a visible last-update date are what predict whether you'll get help in month eight — see the full seven-receipt checklist at /guides/how-to-vet-fivem-script-sellers rather than assuming a Marketplace listing has already vetted that for you. Marketplace review covers whether a listing is legitimate, not whether its support is good.

Before you install: inspection, staging, and backups

Three habits that cost minutes and catch the failures that cost weekends:

• Inspect the package before running it in production — read the file-level escrow split, the documented exports, and the changelog's most recent real entry, not just its date.
• Install to a staging server first, on the same framework and artifact version as production, and test the specific failure modes that matter for that category — a restart-persistence check for garages and housing, a load test for banking (/guides/stress-test-fivem-economy-scripts).
• Back up your database before installing anything new that touches player data, regardless of channel or price. A legitimate purchase channel protects your payment; it does nothing for a migration that goes wrong at 2am.

Vendor lock-in doesn't care which channel you bought through

Buying through the official Marketplace feels like a safer decision, and for payment and delivery, it is. It has no bearing on whether the resource itself binds you to your current framework or hands your migration decision to the vendor — that risk is a property of the code, not the storefront it was sold on. Check framework coupling and escrow scope before buying on either channel (/guides/fivem-framework-lock-in), because a curated listing can still lock you in exactly as hard as an obscure one.