Revenue share review
Keep 0Gate revenue-share language partner-specific and out of generic developer integration instructions.
Revenue-share terms are partner-commercial terms, not a public integration primitive. A developer can integrate sessions, embeds, redirects, webhooks, and reconciliation without needing revenue-share formulas in the docs.
Public boundary
| Audience | What they need |
|---|---|
| Developer | Which product surface to use, how to create sessions, how to verify events, and how to reconcile. |
| Finance or commercial owner | Contract-specific economics, settlement cadence, invoicing, tax, and reporting terms. |
| Support team | Session ids, transaction refs, event ids, timestamps, and approved escalation path. |
| End user | Approved fee, price, and disclosure copy for the transaction they are completing. |
Safe docs language
- "Commercial terms are account-specific."
- "Use your partner agreement or approved pricing schedule for revenue-share terms."
- "Do not infer commercial terms from quote, fee, or transaction field names."
- "Contact support@0bit.io for partner account or commercial escalation."
Do not publish
- Revenue-share percentages, tier tables, rebate formulas, or margin splits.
- Internal settlement or invoice timing that is not approved for public docs.
- Liquidity provider economics or treasury allocation.
- Any screenshot or example containing real partner revenue data.