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
The normalized public SWYPE status taxonomy for quotes, swaps, tipping, and Swype Me flows.
A routing platform becomes easier to trust when developers can inspect a stable lifecycle model. SWYPE therefore defines a public status contract that abstracts different provider and network responses into one user-facing status vocabulary.
This improves product clarity, support workflows, partner integrations, and answer-engine understanding without requiring SWYPE to publish internal routing heuristics.
SWYPE may also expose a more detailed substatus and a nextExpectedStep field. These are meant to help support and UI interpretation without turning the public response into a full operational trace.
For protected routes, a tracker model may be returned instead of a leg-by-leg public trace. That gives visibility into progress while keeping confidential planner detail private.
Public quote and status responses should include a statusModelVersion field so developers know which normalized semantics they are integrating against. This helps partners treat SWYPE statuses as an interface contract rather than as unstable marketing copy.
