Spread claims review
Keep spread, exchange-rate, and quote wording tied to approved 0Gate responses and partner-specific commercial terms.
Spread and exchange-rate claims are sensitive because they can be interpreted as pricing promises. 0Gate product docs can explain how partners should treat quote data, but they should not publish internal pricing formulas, provider details, or universal spread numbers.
What can be said
| Topic | Safe wording |
|---|---|
| Quote preview | "Quotes are indicative until the user confirms or a locked quote is accepted where enabled." |
| Exchange rate | "Display the rate returned for the specific quote or session." |
| Spread | "Use approved partner wording or API-returned values for the specific transaction." |
| Expiry | "Tell users that quote information can change before confirmation." |
| Support | "Investigate using quote id, session id, transaction ref, and timestamp." |
What must stay out
- Internal rate source, provider selection, venue, reserve, or treasury logic.
- Universal maximum spread claims unless contractually approved for the specific product.
- Screenshots with real customer quote data.
- Code comments, tests, or fixture values treated as customer-facing pricing.
- Statements that imply 0Gate quotes are final when the flow is only a preview.
Quote display pattern
Product copy examples
| Instead of | Use |
|---|---|
| "Guaranteed best spread." | "The quote shown before confirmation reflects the current available rate for that flow." |
| "Fixed FX fee." | "Final pricing depends on method, market, asset, and quote timing." |
| "Powered by internal liquidity engine." | "0Gate provides hosted quote and payment flow handling." |