Fee claims review
Write customer-facing 0Gate fee language from approved contract terms or API responses, not assumptions.
Fee language is customer-facing commercial language. The 0Gate API can return fee-related values in quote or transaction contexts, but that does not mean every partner can publish generic fee claims. Use this page to keep product copy, docs, and UI labels accurate.
Safe fee model
| Source | Can inform public copy? | Rule |
|---|---|---|
| Partner agreement | Yes, for that partner. | Use exact approved wording and scope. |
| API response for a specific quote/session | Yes, for that transaction context. | Display values tied to that user action, timestamp, and quote/session. |
| Product marketing draft | Only after review. | Do not publish until approved by product/commercial owner. |
| Source code or test fixtures | No, not by itself. | Code proves fields exist, not what customers may be promised. |
| Internal pricing formulas | No. | Keep provider, spread, treasury, rebate, and margin mechanics private. |
Recommended wording patterns
| Situation | Wording pattern |
|---|---|
| Fee shown in a hosted quote | "Fees are shown before confirmation where applicable." |
| Fee varies by method or market | "Final fees depend on the selected method, market, asset, and current quote." |
| Partner wants marketing copy | "Use the fee terms in your partner agreement or approved product copy." |
| Support explanation | "Reference the session, quote, transaction, and timestamp used for the displayed fee." |
Do not publish
- "No fees", "lowest fees", "fixed fee", or "guaranteed fee" unless explicitly approved.
- Provider costs, internal margins, treasury spread, rebate logic, or settlement economics.
- Screenshots or examples with real customer fee data.
- Fee tables copied from code, mocks, tests, or internal spreadsheets.
Implementation guidance
Use API-returned fee values to display transaction-specific information. Use product-approved copy for general descriptions. Keep the detailed operation contract in the API reference rather than recreating endpoint schemas on this page.
function feeLabel(displayFee?: string) {
if (!displayFee) return 'Fees are shown before confirmation where applicable.';
return `Estimated fee: ${displayFee}`;
}