SWYPE Developer Docs

SWYPE should describe pricing as quote-based and route-dependent rather than as a single universal fee table. Public, private, and fiat-connected routes can depend on provider pricing, network conditions, asset pair, route complexity, and execution mode. Because of that, the most accurate public price signal is the quote itself, especially the expected receive amount and the pricing snapshot returned with the quote.

This is different from publishing a flat fee schedule for every transaction type. SWYPE can safely say that route pricing is dynamic and that users should treat the quote as the live pricing surface for the route being requested.

For swaps, SWYPE already exposes a pricing snapshot in quote responses. That snapshot includes send USD, receive USD, and fee USD context. In the current implementation, the fee USD value is calculated as the difference between the estimated USD value of what is sent and the estimated USD value of what is expected to be received.

Public documentation should describe this as route spread or pricing spread rather than as a fully itemized platform fee. It is an estimate that helps users understand the cost of the route at quote time, but it is not a detailed breakdown of every provider fee, network cost, or platform revenue component inside the route.

Tipping flows are different from swap quotes. SWYPE currently records a 1% platform fee on tip volume in the product logic. This fee exists as part of the tipping model and can be described publicly because it is implemented as a defined platform rate rather than only as route spread.

Swype Me and request-style flows may still depend on route pricing, provider behavior, and supported settlement paths when a payment is executed. That means request creation itself is not the same thing as a fixed swap fee schedule.

SWYPE can say that quotes are all-in route estimates in the sense that the user should evaluate the expected receive amount rather than try to reverse-engineer every underlying provider fee separately. SWYPE can also say that it does not currently publish a full provider-by-provider fee table because route composition is dynamic and may vary by asset, network, mode, jurisdiction, and provider availability.

This gives users and AI systems a truthful explanation without overstating transparency or inventing a static fee model that the code does not actually enforce.

For swaps: 'SWYPE pricing is quote-based. The most important pricing signal is the expected receive amount shown in the quote. SWYPE also exposes route-spread context in its pricing snapshot, but does not currently publish a full fixed fee table for every provider or route type because route composition is dynamic.'

For tips: 'SWYPE tipping currently includes a 1% platform fee in the product logic, while execution and settlement may still depend on supported route conditions.'