Earnings is the creator-facing business area for payable balances, earning activity, Stripe Connect payout setup, and payout history.
The Earnings and Payouts sections now render operational balances and Stripe Connect status. Public creator rollout still depends on Stripe Connect platform setup, environment wiring, and creator payout policy wording.
The model is usage-based. Players buy platform credits or subscriptions from Continual MI. When paid credits are consumed inside your hosted game, MDL can record a creator earning event in the shared internal ledger. Your share is computed using the platform revenue-share formula and tracked as a payable amount over time.
Once the program is active, earning events are expected to move through a lifecycle:
The platform settlement model converts settled paid usage credits into a creator amount. The remaining amount is retained by Continual MI for platform operation, payment fees, model costs, support, and margin.
Current formula: settled_credits * credit_settlement_usd * creator_percentage.
Purchase-origin data remains useful for diagnostics, but earnings are settled from paid credit usage. The Earnings screen shows normalized creator amounts, while raw purchase and usage diagnostics remain in Monitoring.
The primary number on the future Earnings dashboard is your Payable balance — the sum of all earning events in payable status that have not yet been assigned to a payout batch item (payout_batch_item_id IS NULL). Events that are already included in a draft, approved, or submitted batch are excluded from the payable balance to avoid double-counting.
Gross revenue and pre-hold amounts are intentionally not foregrounded in the creator UI. The payable balance is what matters for payout processing.
Earning events may carry a maturity timestamp. The system tracks when earnings would normally become payable, even before automated payout execution is active. Payable balances include only events that have explicitly reached payable status.
A minimum payout threshold applies before payout batches are created. The default threshold is $100 USD. Balances below this amount are visible and tracked, but are not included in payout processing.
Payouts are processed via Stripe Connect. To receive payouts, you need a configured payout account. Creators complete onboarding directly with Stripe, and account management happens in the Stripe Express Dashboard. Payout accounts go through these states:
Earnings are tracked independently from payout account status, but payout submission requires a ready Stripe Connect account.
Country support follows Stripe Connect account readiness. If Stripe cannot onboard or enable payouts for a connected account, MDL cannot pay that creator through the current payout system.
Payout execution is admin-reviewed. Eligible balances can be placed into payout batches only when the connected Stripe account is ready and the minimum threshold is met. Payout batches are submitted through Stripe Connect transfers.
The Earnings section is the creator-facing business surface. It shows:
The Monitoring > Purchases section remains available for raw operational inspection: Stripe webhook details, checkout session traces, and technical purchase diagnostics. These surfaces are intentionally separate.
