What is a FiveM license identifier?

The license value is one of the main server identifiers for the Rockstar license relationship in a FiveM connection. Some players also present license2. The two values may appear identical or different in practice, so a record system should preserve both with their source.

A fivem identifier points to the Cfx.re account, discord to the connected Discord account and steam to the Steam session. Do not assume every type will appear on every connection: player account links, client state and server configuration affect the available set.

• license / license2 — Rockstar license relationship
• fivem — Cfx.re account relationship
• discord — Discord user ID presented with the connection
• steam — Steam account; it may be absent for some players

Character names and Discord usernames change easily. An identifier can provide a more durable link beneath those display names. When the same license appears in an older ban record and a new connection, that match is much stronger than a similar name.

The phrase “identifier matched” still needs context. Shared computers, transferred accounts, bad source data or broken logging can create mistakes. Read the source, time and other matching traces together.

For a whitelist review or ban appeal, first verify the value type: license:, discord: and fivem: refer to different fields. Search the complete value in a restricted moderation tool, then compare the Discord accounts and ban records it returns.

Do not paste raw identifiers into public channels or screenshots. Moderators usually need the match type and evidence strength. Personal data such as IP addresses should stay out of ordinary lookup results.

If two Discord accounts present the same reliable FiveM identifier at different times, that is a strong link signal. Repetition across several hard identifiers increases confidence. Soft signals such as names, avatars and shared servers may explain a graph, but should not build the cluster alone.

Argos labels the evidence type behind each linked-account result. A moderator can see whether the connection came from a license, membership or name signal instead of accepting an unexplained “alt found” badge.

A manual lookup is useful for historical review. Argos Guard compares the identifier set presented during connection with the archive. When hard evidence crosses your configured threshold, it can send a Discord alert, kick the player or reject the connection. A name-only similarity does not meet the default automatic-enforcement threshold.

Per Cfx.re’s identifier table both are Rockstar Online Services licenses — they come from the same source. The difference is which players present them: license2 is the ROS license of players using Steam, and the official documentation’s own note says it **can be the same value as `license`**.

The practical consequence: do not treat license2 as "a different account" or "a second license". On some connections the two are identical, on others only one arrives. So do not use them interchangeably when matching a record, and do not read a connection carrying only license2 as "no license". Argos stores both as separate columns and reports which one produced the match.

This is the point server owners most often assume wrongly: a license is not a label the player can change at will — it is bound to a game account. A player can change their display name, their Discord account and their character; the license stays the same. That is exactly why ban evasion is possible: a new account produces a new license, but the old account’s trace is not erased.

“Does not change” is not the same as “infallible identity”, though. A shared computer, a transferred account or an unusual connection can surface the same license on an unexpected player. So a single identifier match is not enough to decide on; account age, membership history and the other identifiers are read together.

The strongest confirmation is several hard identifiers pointing at the same accounts: the same license, the same Steam, the same Discord ID. When those three overlap, the link reaches evidence level.

Every player does not carry every identifier type, and Steam is the one that fails most in practice. Cfx.re has stated that it “can no longer guarantee FiveM will be able to offer Steam integration, including identifiers”, because that integration depends on workarounds rather than an official Steam AppID.

The consequence is concrete, and it is the part servers most often get wrong: a connection handler that blocks players arriving without a steam identifier will reject legitimate players who simply did not have Steam running. Cfx.re’s own guidance on that announcement was to remove the Steam blocking check from resources that had it.

So match on identifiers when they are present, and read a missing steam identifier as “not reported”, never as “suspicious”. The Cfx.re documentation presents the list as what GetPlayerIdentifiers returns, not as a guarantee for every connection — so a policy that rejects on any missing field will reject real players.