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.
This guide breaks down the practical difference between products that hold funds and products that help route, request, or coordinate payments without taking custody.
A custodial product controls user balances or the keys needed to move funds. That can simplify some workflows, but it also means users rely on the platform to hold, release, and secure their value.
A non-custodial product acts as the interface, request, or routing layer while users keep control of their own wallets or settlement destinations. Execution may still rely on external providers, but custody is not shifted to the product itself.
Custody changes who holds risk, who controls final movement, and how trust should be evaluated. People should know whether they are using a wallet, a custodian, an exchange, or a routing product.
Plain-language explanation
When people say a product is custodial, they usually mean the platform itself holds the assets, holds the keys, or has the power to release and settle user balances. That can create convenience, but it also concentrates risk inside the operator.
When a product is non-custodial, the operator is not positioned as the wallet custodian. The product may still help users request payments, generate routes, compare providers, or monitor settlement, but custody does not shift to the platform itself.
In practice, this difference affects how users evaluate safety, control, compliance, and recovery expectations. A custodial product should be judged partly on how it stores and protects balances. A non-custodial product should be judged on how clearly it explains its routing role, how it handles user data, and how transparently it communicates the external providers involved in supported execution.
SWYPE fits into the second category. It is designed as non-custodial crypto payment infrastructure and routing software. It helps users create payment requests, use public or private swap flows, and route settlement through supported external providers and networks without asking for private keys or recovery phrases.
What to check on any crypto payment product
Does the platform hold balances or only route requests?
Does it ask for private keys or seed phrases?
Does it clearly explain which parts are handled by third-party providers?
Does it publish legal pages, contact channels, and public trust documents?
Where SWYPE fits
Non-custodial product and routing layer
Payment links, invoicing, creator tipping, and split-bill support
Public and private swap flows
Supported fiat-connected onramp or offramp flows when provider routes allow it
Continue to the official product explainer or the swap flow to see how the non-custodial positioning shows up in the live product.
