Merchant docs /docs
Site Sign in Apply as merchant

V2 boot & SecureConfig

fivem_serverBoot.lua, TenantId, V2 metadata, and customer Config.LicenseKey.

In the merchant dashboard: After sign-in → merchant dashboard — Sign in · Sign in to dashboard

fivem_serverBoot.lua (V2)

Base file merged into server.lua — requests a License Ticket via POST /public/fivem/v1/issue-ticket and verifies locally with Ed25519 keys embedded in V2 metadata.

No Bearer, no TenantApiToken, no bootstrap-config, no webhooks on the customer server.

SecureConfig (in boot)

SecureConfig = {
  ScriptName = resourceName,
  TenantId = 123,
  EnableTamperCheck = false,
}

In automated delivery, PlatformLicenseRuntime (schema platform_license_runtime.v2) is also injected: build_id, issue_ticket_url, license_public_keys, …

Register merchant logic

Put script logic inside _platformRegisterWhenLicenseValid(function() … end) at the bottom of server.lua — do not use exports[GetCurrentResourceName()]:RegisterWhenLicenseValid for the same resource.

config.lua

  • Manual delivery: customer edits only Config.LicenseKey.
  • Automated delivery: key is injected in metadata — no manual copy.

REST details: issue-ticket and Legacy paths.