Revenue
Hub Revenue explains how executed trading activity is attributed. It must stay separate from plans, tiers, subscriptions, and enterprise access gates. Balchemy has one standard product access model.
Navigation: Revenue is linked from the current Hub documentation/navigation set alongside Signal Sources. Treat it as an attribution and fee-record surface, not as a promise that source-owner payout rails are live.
Three concepts
| Concept | Meaning |
|---|---|
| Global swap fee | Balchemy earns from executed swaps. |
| Signal Source attribution | Trades can be attributed to a Telegram, Discord, API, CLI, Web, or other source context. |
| Referral attribution | Referral codes track referred users and referral reward/commission records. |
Signal Source attribution and referral attribution can both support partner growth, but they are not the same system.
What Hub can show
Revenue surfaces can include:
- global swap fee totals,
- source/channel attributed volume,
- source/channel attributed trades,
- referral-code attribution,
- partner/source reward records where implemented,
- payout status only when payout rails are implemented and verified.
Source-owner payout should remain explicit as not_instrumented where that is
the current product state. Do not present fake pending, available, paid,
withdrawable, claimable, or settlement-ready balances for source owners.
What Hub must not claim
Do not claim:
- Free, Pro, Enterprise, or subscription access tiers,
- Stripe billing or upgrade prompts,
- automatic source-partner payout after every trade,
- guaranteed payout timing,
- payout availability when no verified product flow exists.