# Fee Stack

> Check how a B2B app or connector marketplace bills, collects its cut and pays developers, then write the
> monetization design and the developer-facing fees and payouts page. Describe the take rate, what you do today, the
> pricing models developers want, the payout days, the per-developer figures and the tax split; the browser ranks the
> merchant-of-record posture, the fee instruments, the waiver shapes and the payout cadence, and 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. Built on the SkillSafe skill
> @samber/app-marketplace-monetization-model, from samber/developer-platform-skills (MIT), by Samuel Berthe.

https://fee-stack.skillsafe.ai/

## What is free
- The four menus: merchant of record (developer-billed only at zero take, marketplace-billed once charging, configurable only for a legacy population), fee instruments (revenue share netted at source, program fees, processing as its own line, an audited self-reported share only when forced), waivers (a revenue-exemption tier anchored at $1M with automatic enrollment, behavior discounts, migration incentives only with a back-book) and payout cadence (monthly plus a hold, invoice-cycle consolidation, rolling with reserves, instant only as an option).
- Money and time: pricing models wanted against what the rails can bill; sale to bank as cycle plus hold plus bank days against the published number; the cut against the rails' flat account and payout fees per active developer, with the break-even monthly sales.
- The tax layer: every row owned, US sales tax and EU consumer VAT on the platform under facilitator and deemed-supplier rules, and platform rows with no registration that silently collect nothing.
- Enforcement: an anti-circumvention rule with a delisting path, and six months' written notice for fee changes.
- Exports: a fee schedule (Markdown), the tax split (.csv), the checks (.csv) and everything (.json).

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (design or page), `marketplace`, `numbers`, `carry` (page only: the design's decisions) and `facts`.
- `design` replies with `summary`, `posture` (`rung`, `tax`, `chargebacks`, `payouts`), `rails`, `instruments`, `pricing`, `waivers`, `payout`, `tax`, `enforcement` and `caveats`.
- `page` replies with `summary`, `title`, `intro`, `fees` (`fee`, `amount`, `when`), `payouts`, `tax` (`jurisdiction`, `tax`, `who`), `waiver`, `notice` and `caveats`.
The page holds every reply to its own facts: the ranked rungs in order, only billable pricing offered, the longest sale-to-bank days, every tax owner as law and posture require, no rate or amount the input never gives, a delisting path and six months' notice.

## Links
- API tutorial: https://fee-stack.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/app-marketplace-monetization-model