SWYPE uses cookies and similar storage to keep the site secure, remember essential session state, and make payment flows work reliably.
Used for secure sign-in, payment-request continuity, fraud prevention, and account protection.
The current SWYPE experience does not rely on advertising cookies to operate the product shell.
Read the full notice on the cookie page. SWYPE never asks for wallet connect, private keys, or recovery phrases.
Developer Hub
Public swap API, private swap access, widgets, embeds, rate limits, migration notes, and support docs for partner integrations.
Getting Started
Guides
Support
Migration
Changelog
Guides
A high-level explanation of how SWYPE routes swaps, tipping, and Swype Me requests without publishing proprietary route-planning detail.
SWYPE routing starts with user intent. A user may be tipping a creator, paying a request, completing a swap, or using a partner integration. The system first validates the request shape, resolves the destination preferences, and checks whether the flow should be treated as a public route, a private route, or a fiat-connected route.
From there, SWYPE prepares deposit instructions and tracking identifiers, stores the request or transaction record, and returns a stable SWYPE status key to the client. The user-facing surface can then guide the sender while SWYPE continues to reconcile the route in the background.
Tipping and Swype Me follow the same architectural model as swaps, but they begin with a payment or request experience instead of a trading intent. In these flows, the recipient configures the destination wallet and payout preferences while the payer is guided through a cleaner payment path. SWYPE handles the request logic, payout resolution, state tracking, and expiry behavior without taking custody of user funds.
This means SWYPE can honestly describe tipping and Swype Me as non-custodial request and routing flows. The product owns the guided experience, recordkeeping, and reconciliation while supported execution and settlement happen through external providers and supported networks.
Public routing is the standard SWYPE route mode. Public mode aims to find the safest and cheapest supported path available for the requested assets and networks and then return payment instructions quickly. It is the right description when the user wants a straightforward route and does not need the additional confidentiality-focused path used by private mode.
Public documentation should describe this as SWYPE selecting a supported path based on route validity, destination compatibility, provider availability, estimated cost, and operational reliability at request time. That is accurate and useful without exposing scoring, ranking, or failover internals.
SWYPE can expose route semantics without exposing full route decomposition. That means quote and status surfaces can describe whether a route is direct, multi-step, hosted, or protected, can disclose provider labels where safe, and can expose estimated duration and public status semantics without publishing confidential planner outputs.
This is the right middle ground between complete opacity and full router introspection.
