Developer operations
Check the current requirements before planning a payout
The reviewed DevEx overview lists a minimum of 30,000 earned Robux, a verified email, an eligible portal account, age thirteen or older, and good standing under the applicable terms. Those are not the complete agreement, and reaching the balance threshold does not guarantee approval. Review the current process in your own Creator Hub before promising a payment date to a contractor or spending the expected proceeds. Keep a simple checklist with the requirement, the evidence you have, and anything still unresolved. This guide explains preparation rather than determining eligibility for a particular person. A correct calculator result cannot substitute for the platform's account and earnings review.
Reconcile earned Robux rather than the displayed total
Separate eligible creation earnings from purchased Robux, subscription grants, transfers, and other sources that may not qualify. The platform decides which amounts satisfy the earned-balance conditions. Keep transaction records for your own games and items and document legitimate team distributions. A group payment does not automatically make the underlying source eligible if it came from activity that violates the terms. Compare the estimate shown in the DevEx area with your records and investigate an unexplained difference before treating every visible token as cashout-ready. Preserve dates and adjustments so a later review can be understood. Avoid mixing a speculative resale value with settled earnings from original creation work.
Prepare identity and account details through official flows
Use the legal account-owner information requested by the official process and keep it consistent with the payout registration. Do not submit a friend's name simply because that person has a convenient payment account. Complete verification through the supported interface when requested and ask an appropriate guardian or adviser for help where needed. Keep access to the verified email secure because review and registration messages may depend on it. Never send an identity document, password, or authentication code to this portal or to someone claiming they can accelerate approval privately. Record the status of your submission and check account notifications rather than responding to a message solely because it uses a familiar payout logo.
Review the dated tax-information transition
As reviewed on October 31, 2026, Roblox's tax guidance identifies November 1, 2026 as the effective date for classifying DevEx payments as royalties and directs creators to review tax information in Creator Hub. The documentation distinguishes U.S. and non-U.S. tax documentation, including applicable W-9 or W-8 forms. Which form, classification, treaty claim, or withholding treatment is correct depends on the person's circumstances. Use the current official instructions and obtain qualified tax advice rather than selecting an answer from a generic tutorial. Keep this dated transition separate from general game-income planning: a page written before a policy change can otherwise remain misleading long after the interface has moved to a new process.
Build a gross-to-net cash planning sheet
Start with the eligible earned balance and the rate applicable to that earnings category and period. The standard example of 30,000 multiplied by 0.0038 gives 114 USD before other charges, but the current program also describes circumstances with different rates. Do not apply an enhanced rate to all earnings merely because it appears in a headline. Keep provider charges, local currency conversion, any applicable withholding, and other business expenses on separate lines. This is a planning sheet, not a calculation of your personal tax liability. Use the eventual statement to reconcile the actual amount received. Preserve the original estimate so the cause of any difference remains visible instead of being hidden by a changed multiplier.
Submit carefully and track the review state
Check the legal name, contact details, amount, and requested registration information before confirming a request. Follow the status through the supported dashboard and keep the relevant references in your records. A request, a reviewed approval, a completed portal registration, and a settled payment are different stages. Do not budget as though they occurred on the same day. If an issue requires clarification, provide the requested information through the official route and avoid repeated speculative changes to your identity or payment details. The portal cannot guarantee a review time or payment outcome. A conservative cash calendar should let ordinary project maintenance continue even when a request takes longer than the most favorable example another creator reported.
Keep an organized annual record
Maintain a folder for payout statements, relevant tax documents, transaction summaries, project expenses, and the dates when you updated account information. Store sensitive records securely rather than in a shared public game repository. A project partner can receive an appropriate accounting summary without receiving your private identity documents. Reconcile totals periodically so preparation does not begin only when a form or payment problem appears. Review whether the legal owner or business structure has changed before submitting future requests. Smooth administration comes from accurate records and current instructions, not from a promise that a minimum balance automatically becomes approved cash. Use professional advice for individual filing obligations and keep the development team informed about payment commitments that depend on actual settlement.
Official references and current requirements
Policy details were checked on October 31, 2026. Fees, eligibility, and program rules can change; check the official requirements before publishing or requesting a payout.