roblox monetization
When to Load
Load when adding a Game Pass, Developer Product, subscription, private server, Creator Rewards-related product decision, or purchase eligibility check.
Quick Reference
- Prompt purchases from the client, but grant value only from server-owned code.
- Passes: durable ownership for an experience. Check ownership server-side and refresh after a purchase.
- Developer Products: repeatable consumables. Grant through a server-owned receipt handler, either
ProcessReceiptorBindReceiptHandlerwithEnum.ReceiptType.DeveloperProduct.PromptProductPurchaseFinishedis not purchase confirmation. - A receipt that cannot be safely granted must return
NotProcessedYet. Roblox redelivers it when the player rejoins (there is no time-based retry). - For eligibility-sensitive purchases, check
PolicyServiceand current Roblox guidance. If a paid-random-item restriction applies, offer the user the documented choices, including earnable rewards, a known non-random sequence, or direct purchase. Do not default to hiding or blocking the feature; handle the affected purchase path without stopping unrelated work. - Creator Rewards is a platform program, not a grant API. Track eligibility, attribution, engagement, and dashboard reporting separately from purchases and inventory.
- Test failed grants, duplicate receipts, player absence, and interrupted saves before shipping.
- A receipt handler's presence is not proof of correctness; inspect its ownership, durable idempotent grant, and retry paths for unknown products or absent players.
Need the details? Load references/full.md for purchase flows and failure handling.