Deposits

Fund your balance by sending native SOL to the address shown in your dashboard, including the memo that identifies your account. Credit is applied once the transaction reaches finalized commitment, and the amount credited is derived from the chain, never from anything a browser reports.

How to deposit#

Open the dashboard, choose an amount, and take one of two paths.

Connect a wallet. We detect any Solana wallet installed in your browser, build the transfer with the memo already attached, and hand it to the wallet to sign and send. Nothing to copy and nothing to get wrong.
Send from anywhere. Scan the Solana Pay QR, or copy the address and the memo into whatever wallet you use, including one on a phone. This path always works.

The minimum deposit is 0.01 SOL. At 0.0002 SOL per accepted send, that is about fifty transactions; 0.1 SOL is about five hundred.

Why the memo matters#

The memo is the only thing that ties a deposit to your account. A deposit that arrives without it, or with the wrong one, cannot be credited automatically and has to be reconciled by hand.

It is fair to ask why we do not simply credit whoever pastes the signature into the dashboard. Because anyone can watch the deposit address, see an unattributed transfer, and paste that signature first. A signature can only be credited once, so the impostor would win and the real depositor would lose their money. Requiring the memo is what makes that attack impossible.

Your memo is unique to your account, stable, and safe to reuse for every deposit you ever make.

How we verify#

Every deposit passes the same checks before a single lamport of credit is issued.

The transaction must be finalized. Confirmed is not enough, because confirmed can still be dropped.
It must have succeeded on chain. A transaction with an error moved nothing.
It must have moved native SOL to our deposit address. Token transfers do not count.
The credited amount is derived from the deposit address’s own balance change in that transaction. We never trust an amount reported by a browser, because a browser can claim anything.
The on-chain signature is the idempotency key, both in our database and at the ledger. The same deposit cannot be credited twice even if every part of the system retries at once.

Timing#

Finalization usually takes well under a minute. The dashboard follows your deposit through sent, confirming, finalized and credited, and updates your balance the moment credit is applied. A background sweep also picks up deposits independently, so credit still arrives if you close the tab.

If something goes wrong#

Your SOL is on chain and it is not lost. These are the cases we see and what happens next.

Situation	What happens
Sent without a memo	Recorded and flagged for manual reconciliation. Email us the signature and we credit it by hand.
Wrong memo	Same as above. Nothing is credited to the wrong account.
Below the minimum	Not credited automatically. Contact us and we will sort it out.
Transaction failed on chain	Nothing moved, so there is nothing to credit. Send again.
Finalized but still not credited	The sweep retries automatically. If it persists past a few minutes, send us the signature.

For anything on this table, email support@swqos.com with the transaction signature. That signature is all we need to find it.