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
Migration
Move integrations to the structured partner v1 endpoints and SWYPE Swap ID based tracking model.
The current partner API standardizes on SWYPE Swap IDs, explicit rate-limit visibility, and unified public/private routing endpoints. Public and private swap creation now share one create endpoint and differ only by the mode field plus account access permissions.
On This Page