Security before, during and after a crypto exchange
Check the site, asset, network, full address and current order before sending. An address that passes a format check can still belong to the wrong recipient or an unsupported network. Keep wallet secrets and private order links out of public messages.
Reviewed September 10, 2026 · Orbiswap product reference
Never share
Seed phrase or private key
Orbiswap asks for public wallet details, never recovery phrases or private keys.
Always match
Asset, network and address
A familiar ticker or prefix is not enough.
Keep private
Order tracking link
It is a recovery reference, not a public receipt.
01
Public addresses route funds; wallet secrets control them
An exchange uses public destination and refund addresses, plus a memo or tag when required. These details do not authorize spending. A recovery phrase or private key can give someone control of funds; do not enter either in an exchange form or send it to support. Do not grant remote access to your wallet or device for an unsolicited recovery request.
- Reject any request to “verify” a seed phrase.
- Do not import a stranger’s recovery file or browser extension.
- When available, compare the full address on the trusted wallet display before confirming.
02
Treat the network as part of the address
A 0x address can be used on several EVM networks, but its format does not prove that the recipient accepts each one. Check the exact blockchain and asset representation, including the token contract where applicable. A correct checksum or successful blockchain transfer does not guarantee that a receiving service can credit an unsupported route.
- Read the full network label in both interfaces.
- Match token contract or native-asset identity.
- Include the memo or tag supplied by a custodial receiver.
03
One order, one current deposit instruction
Open the current order before each exchange and use its displayed payment details. Addresses can be shared or repeated, so an address alone does not identify an order. Compare the full address, network, amount and any memo with the wallet send screen, then save the private tracker before broadcasting.
- Use the current order instructions even when the address looks familiar.
- Compare the full address on both screens; matching a few characters is insufficient.
- Avoid public screenshots containing the private tracking token.
04
Real support asks for evidence, not control
Contact support through the product’s official support page. Start with the order ID, transaction hash, actual network, amount and relevant public addresses. Share transaction evidence only in the private support conversation. Ignore unsolicited recovery messages, requests for wallet secrets and demands for a second payment to prove ownership.
- Prepare public transaction evidence.
- Ignore direct messages claiming guaranteed recovery.
- Do not send a second payment to prove wallet ownership.
WORKING CHECKLIST
The last review happens before broadcast
- The intended domain and the current order are open.
- Asset, network, address and memo match.
- No wallet secret has been entered or shared.
- Tracker and transaction evidence will be stored privately.
FAQ
Questions about this reference
Can support ask for a transaction hash?
Yes. A transaction hash is public evidence. It is fundamentally different from a private key or seed phrase.
Is a small test transaction always safe?
No. A test payment does not replace checking the full address and network. An exchange may expect one exact deposit, so do not split it into a test and a remainder unless the current instructions explicitly permit that.
What if the copied address changes?
Stop before confirming. Verify the intended destination independently on a trusted device and compare the full address. Do not continue from a clipboard value that changes unexpectedly.
Does No KYC remove blockchain risk?
No. Account friction and transaction safety are separate concerns. Wrong-network transfers and exposed wallet secrets remain dangerous.
CONTINUE THE RESEARCH