Route browsing without signup
Sasquatch route pages and comparisons do not require a Sasquatch transaction account. Users can research assets, networks, and route structures before execution.
Learn what can be reviewed without signup, which provider steps may still appear, and how account, email, wallet, KYC, and custody requirements differ.
Sasquatch route pages and comparisons do not require a Sasquatch transaction account. Users can research assets, networks, and route structures before execution.
An underlying tool can apply account, verification, email, phone, regional, or eligibility requirements. Check the active flow rather than assuming the comparison interface controls every provider policy.
A route can require wallet signing without requiring a site account, or use manual deposit instructions without a wallet connection. These are different access models.
A support message can require a reply address even when route browsing does not. Never share a seed phrase, private key, or wallet backup.
An account record and identity verification are different. A provider can request verification during a route even if the user did not create a traditional account first.
Confirm provider, displayed access requirements, exact assets and networks, destination, wallet or deposit steps, fees, output, minimum received, quote expiry, and receipt.
Yes. Sasquatch route comparison does not require a transaction account.
Potentially. Provider-specific requirements must be checked in the active flow.
Not universally. Provider or support steps can have separate email requirements.