For platform teams putting paid apps on their marketplace
Fee StackWho bills, how the cut is collected, when developers get paid, who owes which tax.
Describe the marketplace: the take rate, what you do today, the pricing models developers want, the payout days, the per-developer figures and the tax split. Your browser ranks the merchant-of-record posture, the fee instruments, the waivers and the payout cadence, flags pricing the rails cannot bill, a published timeline shorter than the real one, rails fees larger than the cut, tax nobody owns or that silently collects nothing, and a share with no delisting path or notice. Then the design, and the page developers read.
The marketplace, and a short interview free
Payouts, fees, waivers and tax free
The checks free
What the page flags
The gates
The four menus
Pricing, payouts and the per-developer money
The tax split
Area by area
Your fee schedule free
The instruments, the honest payout days, the tax split by jurisdiction and the notice - the schedule the skill says to publish with your fees.
Fee schedule (Markdown)
The monetization design metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Caveats
Caveats for your team
The page's check of this reply
Saved fee stacks
How it works - and what is sourced
The rankings follow the skill. Developers bill their own customers only while the marketplace takes nothing; once a rate is charged, the marketplace bills and nets its share at source, the only mechanism that does not depend on developers reporting their own revenue. Billing both ways per app is kept only for a legacy population that cannot migrate in one cycle. Processing is a separate labeled line; flat program fees price a real cost; an audited self-reported share exists only when a developer-billed posture forces it. The waiver anchors at the $1M the sourced programs cluster around, with eligible developers enrolled automatically. Payouts default to a monthly cycle with an explicit hold, ride an existing invoice cycle when there is one, roll with reserves when you compete for supply, and offer instant payouts only on top.
Sale to bank is the cycle plus the hold plus the days to the bank - the number to publish, not "monthly". The per-developer check sets the cut against the rails' flat account and payout fees. US marketplace-facilitator statutes and the EU deemed-supplier rule for consumer sales put tax on the platform whatever the billing posture; a platform tax row with no registration collects nothing and cannot be fixed later. Every percentage needs an anti-circumvention rule with a delisting path and six months' written notice of changes. None of this is tax or legal advice - route the published split through qualified counsel.