Pumpx deposits using SOL fund the wallet through a Solana transfer
Pumpx deposits through the Quick Start route add SOL to a trading wallet on Solana. The described route starts inside a logged-in account, where Deposit opens the receiving details. Pumpx’s download instructions describe a testing-phase release limited to regions with trading licenses. The sender then withdraws SOL to that address using the Solana network. Confirmation precedes the balance appearing in Assets. Adding funds and buying a token are separate actions, so a deposit does not select or purchase a token. The amount and timing of another transfer follow your funding decision. Before sending, match the recipient address and network; afterward, inspect the balance belonging to the receiving wallet.
Key takeaway: The receiving address and Solana network must match the withdrawal instructions before you send SOL to fund the trading wallet.
SOL and Solana identify the funding route
SOL is the asset being transferred, and Solana is the network carrying this deposit to its receiving address. Both belong in the sending service’s withdrawal instructions. Selecting the asset identifies what you intend to send; selecting the network identifies the transfer route. Keep those choices together when preparing this particular deposit.
Other assets and networks require their own receiving instructions. The Heima whitepaper reports cross-chain trade payments in Pumpx using assets such as USDT, BNB, and ETH. Those payment options do not establish compatibility with this Solana deposit address.
Where can I find the deposit address?
The described app provides a Deposit entry on the home screen at first login and another within Funds. Both lead to the receiving details, which include a QR code and a Solana wallet address.
The home-screen entry
At first login, the home screen displays Deposit alongside the app’s other functions. Open it to locate the receiving details before preparing the outgoing withdrawal. Merely opening this screen does not authorize a transfer from an exchange account.
The Funds entry
Funds provides another way to open Deposit without relying on the first-login entry. Use the receiving address shown there as the recipient for the SOL route.
The sending exchange handles the outgoing withdrawal
The deposit screen supplies a destination, while the exchange handles the withdrawal from your SOL balance on that exchange. The documented Binance route starts from that balance and uses Withdraw followed by Crypto Address. Other sending services may arrange their controls differently. The prerequisites remain a SOL balance and a withdrawal route matching the receiving instructions.
Recipient and withdrawal network
Enter the address from Deposit in the recipient field, and select Solana as the withdrawal network. Review the recipient after pasting it, before authorizing the transfer. The address identifies the receiving wallet, while the network choice preserves the route described for this deposit.
Amount and final approval
Enter the quantity of SOL you intend to transfer, then review the withdrawal details before submitting them. It does not specify a token purchase size or a limit-order setting inside the trading app.
When does the SOL balance appear?
For the documented SOL funding route, Assets shows the incoming SOL balance after the transfer confirms. Withdrawal approval starts the sender’s process and does not establish network confirmation. Check whether the SOL transfer succeeded and used the intended recipient address before treating the unchanged balance as a display problem. Quick Start gives no fixed arrival time. Inspect Assets for the receiving wallet after confirmation, keeping the sender’s withdrawal status distinct from the balance the app displays.
A wallet switch can explain a different asset total
In this hypothetical example, a confirmed SOL transfer has reached the wallet whose address the reader used. Assets currently displays a different wallet, and selecting the receiving wallet reveals the incoming SOL. The apparent missing deposit comes from viewing another wallet’s total.
Assets reports the balance of the selected wallet, and the app allows switching wallets to view different accounts. The transfer destination determines which wallet receives the SOL. The selected view determines which balance appears. Switching that view changes the displayed account without moving the funds between wallets.
If the receiving wallet also lacks the deposit, changing the view has not resolved the discrepancy. The recipient address and transfer confirmation then need attention.
Does depositing SOL also buy a token?
Depositing SOL funds the wallet; a token purchase requires its own trading action.
Token search and token details help you choose a token, while Deposit supplies receiving information. Limit orders also have a separate purpose: they apply trading conditions after you choose a token and configure an order. A funded balance alone does not show that an order exists or a purchase has completed.
Further funding follows a decision to add SOL
The manual SOL route fits a new transfer when you want to increase the receiving wallet’s balance. Treat each additional withdrawal as a separate funding decision. Start from the wallet you intend to use and its displayed receiving details. Compare any saved recipient in the sending service with that address before using it. Once the incoming SOL appears in the receiving wallet, that deposit is complete.
Pause the withdrawal if the destination or network does not match
Pause before authorizing the withdrawal if its recipient differs from the displayed deposit address or its network differs from Solana. Correct the sending instructions before returning to the withdrawal approval.
If you want to send another asset or use another network, this address alone does not establish a suitable route. Continue only after the receiving interface supplies instructions matching that transfer. If your goal is a purchase using an asset held on another chain, Heima-integrated payments can avoid first funding with SOL where your app supports that asset and network.
Pumpx deposits: questions and answers
-
Should I paste a token contract address into the SOL withdrawal form?
- Use the Solana wallet address from Deposit as the withdrawal recipient. A token contract address identifies a token for search and does not identify your receiving wallet. Copying a contract address from token details serves a different purpose from funding the wallet.
-
Does receiving a SOL deposit require sharing a recovery phrase?
- Receiving SOL through the described route requires the deposit address, not a recovery phrase. The sender uses the public receiving address to direct the transfer. A recovery phrase or private key controls wallet access and does not belong in the withdrawal recipient field.
-
Are withdrawal charges included in the SOL amount I enter?
- The sending service determines how its withdrawal amount and charges relate. Read its final review for the quantity it will send and any separate or deducted fee. Keep those quantities distinct when checking the expected incoming SOL. Pumpx platform trading fees concern a separate trading action.
-
Does a token sale failure mean my SOL deposit did not arrive?
- A token sale failure does not establish that an earlier SOL deposit failed. A token contract can block the sale of that token. Check that the incoming SOL transfer succeeded and reached the intended wallet, separately from the attempted sale.