Connect the store only after the server works
The Cfx.re store-setup manual identifies Tebex as the authorized, exclusive game-server monetization partner. It directs operators to the Platform License Agreement , Tebex Acceptable Use Policy and Terms of Service . Review the current terms for your actual products; this technical setup is not legal advice or approval of a particular offer.
Start with a working server installation or txAdmin setup. Know which Cfx account owns the registration key and which account will operate the store. Do not publish credentials while resolving ownership.
Account and project onboarding
Create a Tebex account, verify its email and check the operator details. Complete the identity-verification workflow through the provider’s interface; do not put identity documents into resource files or public support issues.
Create a project with a name, currency and the I operate a game server project type for server monetization. In the control panel, open Integrations > Game Servers, select Connect Game Server > Plugin, name the server and continue. The resulting secret authenticates this integration, not a player’s purchase by itself.
Configure FXServer
Add the secret privately to the server configuration:
# Replace privately. Never use setr or sets for this value.
sv_tebexSecret "REPLACE_WITH_PRIVATE_TEBEX_SECRET"Restart the intended server and return to the Tebex control panel to complete the connection. If Continue remains unavailable, inspect the server console for the exact integration error. The upstream onboarding flow permits Skip to proceed with other setup; skipping does not establish a successful server connection. Resolve the integration before selling a product that depends on server fulfillment.
Protect the secret from source control, screenshots, downloaded client files and logs. Rotate an exposed secret through the provider and update the server rather than merely deleting the message containing it.
Before submitting the store
Complete the store description, customer-support contact, wallet setup, identity verification, at least one package and association with the correct Cfx account. Then submit the store for Tebex review. Customize public templates and packages after satisfying the applicable review requirements; do not call an unreviewed test store approved.
A package needs an explicit fulfillment policy. Distinguish a server command/reward from an escrowed FiveM Asset. Use server-verified identities and an idempotent fulfillment record so retries cannot grant the same benefit twice. Handle offline players, failed delivery, cancellation and subscription expiration deliberately. Do not trust a browser callback or a client-supplied price as payment confirmation.
Verification and support
Use the provider’s supported test workflow to verify connection, package mapping, a single successful delivery, a retry, offline delivery and the required revocation behavior. Record the order/test identifier privately, not payment credentials. A website unit test cannot certify a real transaction, provider review or server-side delivery.
The upstream resources include identity verification , store review , application guidance and creator FAQs . Continue with monetization planning, permissions and secure event handling.