Pay the exchange
Deposit address · supplied by your order
After creating the order, copy its payment address into your sending wallet. Match the specified asset, sending network, amount and payment window before sending.
Exchange help
Crypto networks,
addresses & memos
Choose the network your receiving wallet accepts. Then check the address and any required memo before sending.
Exchange across networksDeposit and payout: two different addresses
Your receiving address is not where you pay for the exchange. Neither entering an address nor looking up an order requires a wallet connection.
Receive your crypto
Payout address · supplied by your wallet
Open Receive or Deposit in your destination wallet or exchange account. Select the asset and exact receiving network. Copy the current address and any required memo or tag into no1.
Select both networks in no1 before entering the destination. A token symbol or familiar logo does not identify its network or contract.
Verify token contracts and look up an address
Use the issuer’s mainnet contract
Choose the exact mainnet, not a testnet. Circle lists native USDC separately for Ethereum, Base, Arbitrum and Polygon PoS. Tether lists USD₮ by protocol. Compare that contract with the asset your destination accepts; a bridged token is not automatically the issuer’s native token.
Search on the correct network
Look up the complete receiving address on its mainnet. For token activity, check the token contract too. A contract identifies a token, not your deposit destination. Empty history does not make an address invalid; a record proves neither ownership nor a custodian’s ability to credit you.
A valid format does not confirm the network
These shortened prefixes are examples, not payment destinations. Always copy the complete address supplied by the receiving wallet.
- EVM networks
0x… - 0x followed by 40 hexadecimal characters. The same format can appear on different chains. Acceptance by no1 confirms neither ownership, a correct checksum nor support for your asset. Confirm the receiving chain with the recipient.
- Bitcoin
1… / 3… / bc1… - Bitcoin uses legacy and Bech32 formats. Keep the exact address supplied by your Bitcoin wallet. Do not convert it to another network’s format or infer a network from a similar-looking address.
- XRP classic address
r… - Preserve its letter case. Classic addresses contain a checksum, but an accepted format confirms neither that the account exists nor whether its recipient requires a destination tag.
- XRP X-address
X… / T… - An X-address combines an address and tag; no1 does not accept that format. Ask the recipient for compatible classic-address instructions and the assigned tag separately. Do not use a testnet address for a mainnet payment.
Preserve the copied address. Do not lowercase a non-EVM address.
Can you change the receiving address?
- 01
Before creating the order
Edit the destination in the exchange form. Check the receiving asset, network, address and any required memo before submitting.
- 02
Order created, not paid
The order page cannot edit the payout address. If it is wrong, do not fund that order. Create a new order with the correct destination; do not reuse the old deposit address.
- 03
Deposit already sent
Keep the original order ID and deposit TxID. A replacement order cannot move the deposit or authorize a destination change. If a payout TxID is available, inspect its actual recipient on the receiving network; a form change cannot rewrite that transfer.
Asked for a Receiving address when reopening your private order? Enter the original payout address. This unlocks access; it does not change the destination.
Open the original orderWhere to find your XRP destination tag
A destination tag identifies the customer to credit at a shared XRP address. Some wallets need no tag. The recipient decides whether one is required; it never replaces the address or network.
- Copy it from your recipient
- For an exchange account, use its authenticated XRP deposit screen. For your own wallet, use its Receive instructions. Confirm unclear requirements before sending; never derive a tag from an explorer or copy another customer’s tag.
- Keep the two fields separate
- Put the classic address in Receiving address and the assigned number in the memo or tag field. Do not append the tag to the address.
- Use the exact assigned number
- An XRP destination tag is a whole number from
0to4294967295. An explicitly assigned 0 is valid. Do not invent 0 as a placeholder.
Sent without a memo or tag?
Do not send a second payment to fix the first.
Another transfer cannot attach a memo to a payment already sent. Changing a new order’s receiving memo cannot edit it either.
Transaction failed
An XRP recipient that requires a tag can reject a payment without one. Save the failure result and check your sending wallet before trying again.
Successful, but not credited
A transfer may reach a shared address without being credited if its required memo or tag is missing or wrong. Compare the required identifier with the transaction record. This is different from a wrong-network transfer.
Keep the transaction evidence
- TxID, asset, network, destination, amount and transaction result.
- The memo or tag required by the recipient and the value actually sent.
- For a no1 deposit: original order ID, private link, deposit address and exact Deposit memo / destination tag, if shown.
Contact the service receiving the payment
For a custodial recipient, open support inside that custodian’s authenticated account and ask it to match the transfer. Share transaction details privately; credit or recovery is not guaranteed.
For a no1 deposit, select Request help with this payment. In the support form, include your original order ID, TxID, asset, network and the required memo or tag, alongside the value actually sent. Give an email address for the reply. Support needs to review the transfer; submitting a request cannot guarantee credit or recovery.
Check the original order for its payment instructions and status. Do not share transaction details or your private link with an unsolicited account or a contact found in a search ad.
Which memo goes in which field?
Select the receiving asset and network first. A separate memo or tag field appears when that receiving option supplies one. For XRP, enter the assigned numeric destination tag, never a placeholder.
Receiving memo · in no1
Copy the recipient’s exact payout memo or tag into the separate field, not into Receiving address. A label saying optional does not override your recipient’s requirement.
Leave it blank only if the recipient confirms that no memo is needed. If a required identifier has no compatible field, do not create or fund that route.
Deposit memo · in your sending wallet
If the order shows Deposit memo / destination tag, use its separate copy control and enter that value in the sending wallet. It is not the recipient’s payout memo.
Wait if any required deposit detail is missing. Do not substitute a value from another order.
Changing the receiving option or using SWAP clears the memo or tag. Recheck the destination and identifier before submitting. The exchange form has no separate refund address or refund memo field.
Refunds to an exchange account
An exchange’s outgoing address may be a shared wallet, not your account’s deposit address. The original withdrawal cannot supply the receiving instructions for a return.
- Before a proposed return
- Open your custodian’s authenticated deposit screen or support. Confirm the returned asset, network, current address and required memo or tag, and that deposits are available. An XRP tag cannot make an unsupported asset or network compatible.
- If a return is reported as sent
- Compare the return’s own TxID, recipient and memo or tag with those receiving instructions. Use the custodian’s authenticated support to investigate missing credit. The original withdrawal reference is not a refund TxID.
- Refund requests and timing
- Select Request a refund review to open the no1 support form. Include the original order ID and deposit TxID, then state the receiving asset, network, address and any required memo or tag in your message. Support reviews the transfer and can reply using the email you provide. A request is not refund approval; neither an amount nor an arrival time is guaranteed.