How to Create a Tebex Store for a FiveM Server

To create a Tebex store for FiveM, register the store in Tebex, select the FiveM integration, copy the generated secret into the server-side sv_tebexSecret setting, restart the server and verify authentication before adding packages. Use the current official setup page while you work; dashboard labels and onboarding steps can change.

Do not paste the secret into a client script, screenshot, public repository or support message. Anyone who receives it should be treated as having access until the key is rotated. This guide covers the connection and test process, not a promise that every possible package is permitted.

Before you connect the store

• Review the official Cfx.re Tebex setup and monetization rule.
• Confirm who owns the Cfx.re server and Tebex business account.
• Back up server.cfg and record who can read or change secrets.
• Define one test entitlement that can be safely granted and removed.
• Prepare a non-production or controlled test window.

1. Create the store and choose FiveM

Create the account through Tebex's official creator onboarding and add a game server using the FiveM integration. Use real business and support details; do not invent a company identity or hide recurring billing. Keep account recovery and multi-factor authentication under the business owner's control.

2. Add the server secret

Copy the secret shown for that game-server connection and add the documented setting to the server-side configuration:

sv_tebexSecret "REPLACE_WITH_THE_SECRET_FROM_TEBEX"

Do not copy the placeholder literally. Keep the setting outside any file served by a web server or committed to Git. Restart FXServer using the same controlled process you use for other configuration changes, then inspect the server console for the integration's authentication result.

If authentication fails, compare the server entry and secret in Tebex, check for whitespace or quoting errors, and rotate the key if its confidentiality is uncertain. Do not disable unrelated security controls to make the connection work.

3. Define one package precisely

Before adding many products, create one package with an exact name, price, billing frequency, entitlement, delivery time, compatibility, expiry and support route. Verify the current platform rules for that entitlement. A vague “VIP” label is not enough for a buyer or for the developer implementing fulfilment.

4. Configure server-side fulfilment

Use commands supported by the specific resource or framework you actually run. Do not paste a generic command from another server and assume its identifiers or argument order apply. The fulfilment must:

• resolve the correct buyer/server identity;
• run only after an authenticated Tebex event;
• be safe when the same delivery is retried;
• log the order reference and resulting entitlement;
• support expiry or reversal where the product terms require it.

5. Test before publishing

1. Preview the package on desktop and mobile and verify price, renewal and delivery text.
2. Run a controlled purchase through the official test/creator workflow available to the account.
3. Confirm exactly one entitlement is granted to the intended identity.
4. Retry the delivery and prove that it does not grant twice.
5. Test the game server or database being unavailable and reconcile the result afterward.
6. Test cancellation/expiry and the applicable refund path.
7. Verify the support team can find the order without asking for passwords or payment-card data.

6. Launch with operational ownership

Assign an owner for failed deliveries, refunds, disputes, secret rotation and order-to-entitlement reconciliation. Review staff access periodically. A discount or large CTA cannot compensate for a package that is unclear or fails to deliver.

For package policy, entitlement design and lifecycle controls, use the full FiveM server monetization guide.