Passes let you charge users a one-time Robux fee to access special privileges inside your game, such as entry to a restricted area, an in-game avatar item, or a permanent power-up.
Create a pass
To create a pass:
- Go to Creations and select a game.
- Go to Monetization ⟩ Passes.
- Click Create pass.
- Upload an image to display as the pass icon. Make sure the image doesn't exceed 512x512 pixels, doesn't include important details outside of its circular boundaries, and is in .jpg, .png, or .bmp format.
- Enter a name and a description for the pass.
- Select a category for the pass. The category is used to organize items in your in-game Shop.
- Click Create pass.


Get the pass ID
To use scripting, you need a pass ID. To get the pass ID:
Go to Monetization ⟩ Passes.
Hover over a pass' thumbnail, click the ⋯ button, and select Copy Asset ID from the context menu.

Sell a pass
You can sell passes in two ways:
Inside your game
To implement and sell a pass inside a game, call MarketplaceService functions.
Use GetProductInfo() to retrieve information about a pass, like name and price, and then to display that pass to users. You can sell the pass inside your game's marketplace, for example. For passes, the second parameter must be Enum.InfoType.GamePass.
local MarketplaceService = game:GetService("MarketplaceService")
-- Replace the placeholder ID with your pass ID
local productId = 000000
local success, productInfo = pcall(function()
return MarketplaceService:GetProductInfo(productId, Enum.InfoType.GamePass)
end)
if success and productInfo then
-- Check if product is for sale
if productInfo.IsForSale then
-- Display product information
-- Replace the print statements with UI code to display the pass
print("Pass Name: " .. productInfo.Name)
print("Price in Robux: " .. productInfo.PriceInRobux)
print("Description: " .. productInfo.Description)
else
print("This product isn't for sale")
end
endUse PromptGamePassPurchase() to prompt a pass purchase if the user doesn't already have the pass in their inventory. You can call this function when a user performs actions like pressing a button or talking to a vendor NPC.
local MarketplaceService = game:GetService("MarketplaceService")
local Players = game:GetService("Players")
-- Replace the placeholder ID with your pass ID
local passID = 0000000
-- Prompt pass purchase
local function promptPurchase()
local player = Players.LocalPlayer
local hasPass = false
local success, message = pcall(function()
hasPass = MarketplaceService:UserOwnsGamePassAsync(player.UserId, passID)
end)
if not success then
warn("Error while checking if player has pass: " .. tostring(message))
return
end
if hasPass then
-- Show a message telling user they already own the pass
else
-- Prompt pass purchase
MarketplaceService:PromptGamePassPurchase(player, passID)
end
endUse PromptGamePassPurchaseFinished to handle a completed pass prompt and purchase and assign the user the privileges associated with the pass.
Place the script inside the ServerScriptService so that the server handles the user's pass privileges.
local MarketplaceService = game:GetService("MarketplaceService")
-- Replace the placeholder ID with your pass ID
local passID = 0000000 -- Change this to your Pass ID
-- Handle a completed prompt and purchase
local function onPromptPurchaseFinished(player, purchasedPassID, purchaseSuccess)
if purchaseSuccess and purchasedPassID == passID then
print(player.Name .. " purchased the Pass with ID " .. passID)
-- Assign the user the ability or bonus related to the pass
end
end
-- Connect PromptGamePassPurchaseFinished events to the function
MarketplaceService.PromptGamePassPurchaseFinished:Connect(onPromptPurchaseFinished)Outside your game
Roblox surfaces your Listed passes outside your game, including on the Roblox homepage, in search results, and on the post-purchase page after a player buys Robux. A player can buy your pass and then join your game with it already granted.
To make a pass eligible for external sales:
- In the Creator Hub, go to Monetization ⟩ Shop.
- Mark the pass Listed.
Passes don't require a ProcessReceipt fix, but they must be Listed to appear outside your game. We recommend adding a custom icon to each pass so players can recognize it on external surfaces; if you don't add one, Roblox shows a default icon.
Assign pass privileges
You must manually assign pass privileges to users that purchase your passes. To do this, use PlayerAdded when a user joins your game to check if they already own the pass and to assign them the pass privileges.
Place the script inside the ServerScriptService so that the server handles the user's pass privileges.
local MarketplaceService = game:GetService("MarketplaceService")
local Players = game:GetService("Players")
-- Replace the placeholder ID with your pass ID
local passID = 0000000
local function onPlayerAdded(player)
local hasPass = false
-- Check if user already owns the pass
local success, message = pcall(function()
hasPass = MarketplaceService:UserOwnsGamePassAsync(player.UserId, passID)
end)
if not success then
-- Issue a warning and exit the function
warn("Error while checking if player has pass: " .. tostring(message))
return
end
if hasPass then
-- Assign user the ability or bonus related to the pass
print(player.Name .. " owns the Pass with ID " .. passID)
end
end
-- Connect PlayerAdded events to the function
Players.PlayerAdded:Connect(onPlayerAdded)Free trials
Free trials give players the full benefits of a pass for one game session before they purchase it. Each player can start one free trial per pass, and only one free trial can be active at a time.
Starting December 2, 2026, free trials are available to players for any pass that has them enabled. New passes have free trials disabled by default.
You can also configure free trials with the Open Cloud game passes API.
Enable free trials
To enable free trials for one or more passes:
- Go to Creations and select a game.
- Go to Monetization ⟩ Shop ⟩ Free Trials.
- Enable free trials for each pass you want players to try.
You can also select a pass from Monetization ⟩ Passes, open its sales settings, and enable free trials there. To disable free trials, turn the setting off for each pass on the same pages.
How free trials work
When free trials are enabled for a pass, players who don't already own it see a Try button in Shop. After a player starts a trial:
- The trial lasts for one game session.
- A button in the top right of the screen indicates that the trial is active. Before the session ends, the button changes to Buy so the player can purchase the pass during the trial.
- If the player purchases the pass during the trial, they keep it. If the session ends without a purchase, access is revoked.
If a session ends unexpectedly because of a system error and the player rejoins within one hour, the free trial continues.
Players who already own a pass aren't eligible for its free trial and don't see a trial offer.
Update your code for free trials
Access checks continue to work during a trial, but you must update any code that grants permanent items, currency, or saved data when ownership becomes true.
| Event | Behavior | Recommended action |
|---|---|---|
| Player starts a trial | PromptGamePassPurchaseFinished fires on the client and server with purchaseSuccess set to true | Call GetPassOwnershipAsync and confirm Owned is true before granting permanent rewards |
| Trial is active | UserOwnsGamePassAsync returns true | Use existing temporary access checks as usual |
| Trial ends | No event fires. Ownership checks return false | Re-check ownership when access matters instead of caching ownership for the session |
Use GetPassOwnershipAsync to distinguish a purchased pass from an active trial. On the client, the method can only query the local player. On the server, it can query any player.
| Field | Description |
|---|---|
| Owned | Whether the player purchased the pass. |
| Active | Whether the player currently has access through a purchase or an active trial. Matches UserOwnsGamePassAsync. |
| StartTime and EndTime | Included while a trial is active. |
local MarketplaceService = game:GetService("MarketplaceService")
-- Replace the placeholder ID with your pass ID
local passID = 0000000
local function grantPermanentRewardIfOwned(player)
local success, ownership = pcall(function()
return MarketplaceService:GetPassOwnershipAsync(player, passID)
end)
if not success then
warn("Error while checking pass ownership: " .. tostring(ownership))
return
end
-- Only grant permanent rewards for purchased passes, not free trials
if ownership.Owned then
-- Grant permanent items, currency, or saved data here
elseif ownership.Active then
-- Player is in a free trial; grant temporary access only
end
end
MarketplaceService.PromptGamePassPurchaseFinished:Connect(function(player, purchasedPassID, purchaseSuccess)
if purchaseSuccess and purchasedPassID == passID then
grantPermanentRewardIfOwned(player)
end
end)In Studio playtests, free trials last one hour so you can test the start, active, and expiry flow before you publish.
Common patterns to update
Most pass code assumes that once a player owns a pass, they own it forever. A free trial gives the pass for a limited time, so the following common patterns can let players keep its benefits after the trial ends. A player in a trial should get exactly what a buyer gets, and ownership can also end for buyers, for example after a refund. The fix for all of them is the same: apply pass benefits from a live ownership check, and don't save them.
Saving or caching ownership
The most common pattern stores "owns pass" the first time UserOwnsGamePassAsync returns true, in saved data or in a table for the session, and reads that value instead of calling the API again. After the trial ends, the stored value is still true.
if data.Passes[passID] or MarketplaceService:UserOwnsGamePassAsync(player.UserId, passID) then
data.Passes[passID] = true
grantPassBenefits(player)
endCall UserOwnsGamePassAsync every time access matters, such as on join, on spawn, and when the benefit is used. Roblox caches the result internally, so repeated calls are inexpensive, and the result changes to false when the trial ends. If a call fails, deny access and try again on the next check.
local function ownsPass(player)
local success, hasPass = pcall(function()
return MarketplaceService:UserOwnsGamePassAsync(player.UserId, passID)
end)
return success and hasPass
end
local function onCharacterAdded(player)
if ownsPass(player) then
giveTool(player, "Dark Blade")
setSpeed(player, MAX_SPEED)
end
endSaving what the pass grants
Some passes write their benefit into saved data, such as an item in the inventory, a maxed upgrade, an unlock, or currency. Even with a live check on every join, the saved benefit stays after the trial ends. Clearing an ownership flag doesn't help if the benefit itself was saved somewhere else.
if ownsPass(player) then
data.Inventory["Dark Blade"] = true
data.Upgrades.Speed = MAX_SPEED
data.Coins += BONUS_COINS
endApply the benefit at runtime from ownsPass, as in the previous example, so it's rebuilt every session and ends when ownership ends. If the pass grants something players keep and use up, such as currency, sell it as a developer product instead.
If your game already saved pass benefits, stop saving new ones and remove only items you recorded as granted by the pass, such as items tagged with the pass ID. Don't remove an item from every player who doesn't own the pass, because they might have earned or traded for it.
Granting from the purchase signal
PromptGamePassPurchaseFinished also fires with purchaseSuccess set to true when a trial starts. From this signal, apply the same runtime benefits you apply on join, and don't save anything.
Gifting and trading
- Gifting. A player in a trial looks like an owner, because UserOwnsGamePassAsync returns true. If your gift flow refuses a gift when the recipient already has the pass, check the recipient's Owned from GetPassOwnershipAsync instead, so a player in a trial can still receive the pass as a gift.
- Trading. A trade usually saves the item to the other player's inventory, where it no longer depends on the pass. Pass ownership can end at any time, such as when a trial ends, a purchase is refunded, or a player deletes the pass from their inventory, and the traded item stays with the other account. If you want players to trade an item, sell it as a developer product instead of granting it through a pass.
Checklist
Before you enable free trials for a pass, check that:
- Ownership comes from a UserOwnsGamePassAsync call each time access matters, never from a saved or cached value.
- Pass benefits are applied at runtime and never saved, so they end when ownership ends.
- PromptGamePassPurchaseFinished applies the same benefits as joining.
- Gift flows check the recipient's Owned, and you sell items that players can trade as developer products, not through a pass.
Free trial metrics
To view free trial metrics:
- Go to Creations and select a game.
- Go to Monetization ⟩ Shop ⟩ Free Trials.
The page shows free trial revenue, how often trials are shown and started, and how often they convert to a purchase, both overall and per pass. Purchases during or after a trial use your usual pass earnings.
Personalize your in-game store
You can use product intelligence APIs to sort and recommend passes to users. Personalizing your in-game store helps surface the most relevant items to each user, boosting engagement and revenue. By tailoring passes to user preferences, you can improve their discovery, increase conversion rates, and unlock new monetization opportunities.
Rank passes for sale
RankProductsAsync takes in a list of product IDs and returns a personalized ordered list of those products. You can use this method to provide your users with personalized item recommendations in your in-game store.

local MarketplaceService = game:GetService("MarketplaceService")
-- Create the array of products you want to rank
local productIdentifiers = {
{InfoType = Enum.InfoType.GamePass, Id = 123},
{InfoType = Enum.InfoType.Product, Id = 456},
{InfoType = Enum.InfoType.Product, Id = 789}
}
-- Optional: Wrap the call in an async task so that if the request is slow,
-- it doesn’t freeze the UI / game
task.spawn(function()
-- Use a pcall to handle errors gracefully
local success, result = pcall(function()
return MarketplaceService:RankProductsAsync(productIdentifiers)
end)
if not success then
-- If failed, 'result' is the error message.
warn("Failed to rank products:", result)
end
-- Load the returned items into the store.
for i, rankedItem in ipairs(rankedProducts) do
local productIdentifier = rankedItem.ProductIdentifier
local productInfo = rankedItem.ProductInfo
-- ...
-- Logic to add productInfo into store
end
end)Display your top passes
RecommendTopProductsAsync takes an array of InfoType values and returns up to 50 items a user is most likely to engage with and purchase. You can use this method to create a "Top Picks" section in your in-game store.
If no recommendations can be determined, RecommendTopProductsAsync returns 0 items. Any passes that the user already owns are also not returned.
In rare cases, calls to the ranking model can be slow. To help prevent added lately for users, we recommend using task.spawn to make the call to RecommendTopProducts non-blocking.

local MarketplaceService = game:GetService("MarketplaceService")
-- Create an array of product types to include. In this case both game passes and developer products
local productTypes = {Enum.InfoType.GamePass, Enum.InfoType.Product}
-- Optional: Wrap the call in an async task so that if the request is slow,
-- it doesn’t freeze the UI / game
task.spawn(function()
-- Use a pcall to handle errors gracefully
local success, result = pcall(function()
return MarketplaceService:RecommendTopProductsAsync(productTypes)
end)
if not success then
-- If failed, 'result' is the error message.
warn("Failed to rank products:", result)
end
-- Load the returned items into the store. Make sure to filter out any
-- ineligible items from topRankedItems such as developer products the
-- user can no longer purchase
for i, rankedItem in ipairs(rankedProducts) do
local productIdentifier = rankedItem.ProductIdentifier
local productInfo = rankedItem.ProductInfo
-- ...
-- Logic to add productInfo into store
end
end)Promote a pass
To help more users discover your game, you can opt-in to have your passes featured on Roblox's Buy Robux page. Opting-in to promote your passes can help increase the time and Robux users spend in your game. There is no limit to the number of passes you can promote.
Users are shown passes that are relevant to their play history and engagement on the platform. They are not shown passes that they already own.

When users purchase an eligible Robux package, they receive the promoted pass and are prompted to claim their pass by joining your game.

To opt-in to promote one of your passes:
- Go to Monetization ⟩ Passes.
- Select the pass you want to promote.
- Select Promotions.
- Enable Include this item in the bonus pool.
- Click Save Changes. The pass is shown to relevant users in the Buy Robux page.
The promoted pass:
- Can be off-sale or on-sale. If they're on-sale, their Robux value must be greater than 49 Robux and less than 801 Robux.
- Must include a thumbnail.
- Cannot grant paid random items.
- Must comply with the Community Standards.
Pass analytics
Use pass analytics to analyze the success of individual passes, identify trends, and forecast potential future earnings.
With analytics, you can:
- View your top passes over a selected time period.
- Showcase up to eight top-selling items on a time-series graph to analyze overall sales and net revenue.
- Monitor your catalog and sort items by sales and net revenue.
- View how many passes were acquired by users through promotion on the Buy Robux page.
- View how many users joined your game after acquiring the pass through the Buy Robux page.
To access pass analytics:
- Go to Creations and select a game.
- Go to Monetization ⟩ Passes.
- Select the Analytics tab.
