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
API Reference
Returns the latest status, deposit instructions, tracker steps, and private-provider trace for a SWYPE swap created through your partner account.
GET
/api/partner/v1/swaps/{statusId}
Use the SWYPE Swap ID returned from swap creation. Legacy provider exchange IDs may still resolve internally, but SWYPE Swap ID is the supported management key.
The order-status response is meant to be inspectable. It should expose normalized SWYPE status values, an optional substatus, stable timestamps, route summary information, and recovery indicators when applicable. This gives developers a usable lifecycle model without exposing confidential route heuristics.
On This Page
