Fees

Dynamo fees are explicit, asset-denominated, and ledger-auditable. Every fee is its own ledger row tied to the settlement that produced it. Control Mode charges no fee. See Fees for every rail.

Credit card application fee

The revenue switchboard's credit card channel (the platform fee) takes a rate in basis points of each stream's settled minus refunded amount, rounded down; a refund writes an explicit fee-reversal row. It starts on at 50 bps. GET /owner/v1/revenue shows every channel and the rate in force; operators change it with:

POST /owner/v1/revenue/card_application_fee
{ "on": true, "bps": 50 }

bps is an integer 0…10000. The channel can be turned off ("on": false); when off, no application fee accrues. Every change is applied live and appended to the revenue switch log (GET /owner/v1/revenue/log). Budgets keep the rate they opened with. On the multi-tenant tier the switches belong to the deployment operator (CORE_REVENUE_SWITCHES): a tenant key can read them, and a write is refused with key_scope.

The protocol fee on the stablecoin rail is read from the vault and is not switchable here; a write is refused with revenue_channel_locked. The other channels (internal ledger fee, usage fee, enterprise entitlements) are off and locked.

The credit card rail runs in Stripe TEST mode in this release, so these fees are test-mode figures; live card money is Release-gated.

What you see

what was spent, the platform fee from the fee ledger, and what you keep against a stated processing price table (its figures are marked to be confirmed).

first, each tied to its settlement: protocol fees (one per vault fee event) and the credit card rail's fee rows (?budgetId= narrows to one budget; limit and cursor paginate).

totals; offline verifiers check that the fee ledger balances. The protocol and credit card fee rows are listed by GET /owner/v1/fees.

a fee calculator page; neither needs a credential. A single-tenant deployment shows its own switchboard. The multi-tenant tier shows the deployment's configured rates (CORE_REVENUE_SWITCHES, or the defaults), one page for every account, and never shows anything about any account.

What never happens