Protect your crypto wallet before paying for hosting
Keep recovery material private, prepare the correct network and review the destination and recipient amount before a hosting payment.
At a glance
A self-custody wallet leaves signing authority with whoever controls its keys. With a custodial service, the operator controls transfers and access. Understand which model you use before relying on it for an expiring invoice.
Know who controls the wallet
A self-custody wallet leaves signing authority with whoever controls its keys. With a custodial service, the operator controls transfers and access. Understand which model you use before relying on it for an expiring invoice.
Read your wallet's official instructions for backups and recovery. Your hosting password, wallet password and recovery material are different credentials. Make sure you know which one restores access and which one only unlocks the installed software.
Keep recovery material private
Keep your recovery phrase and private key secret. Do not share them with support staff, through a payment page or with the sender of a message. Do not include this information in a payment screenshot or an ordinary shared note. Store a backup in the format required by your wallet and encrypt any copy accessible over a network.
Keep payment records separate from wallet recovery information. An invoice reference may be useful to support; a recovery phrase is not. If someone offers to repair a hosting payment in exchange for wallet secrets, stop the interaction and use the official contact route.
Prepare the supported network
Before selecting a method, inspect your wallet's available sending networks. SilentVPS supports BTC, ETH, SOL and LTC on their respective networks, native TRX on Tron, USDT on Tron or Ethereum, and USDC on Ethereum. A familiar token name alone does not establish compatibility.
Check the fee estimate and the amount that will arrive. For a token transfer, your wallet may need the chain's native asset for fees. A custodial withdrawal can have its own fee, minimum and delay. Resolve those details before confirming an invoice rather than discovering them near expiry.
Verify what you are about to sign
Use the current invoice to check the full destination address, asset, network and recipient amount in the wallet. Review the transaction before authorising it. Do not trust a matching prefix alone or a destination copied from an unsolicited message.
The SilentVPS invoice provides payment instructions for a transfer. It does not need your recovery phrase or private key. An unexpected signature request or token-spending permission should be reviewed against the task before you approve anything.
Preserve the record without exposing access
After sending, save the transaction identifier with the invoice reference and follow the order status. Keep private order tokens out of public screenshots. Share only what is necessary to review a payment with the official support contact.
If a payment seems delayed, inspect the wallet's transaction state and the network used. Do not send a second transfer merely because the website has not updated. Ask for a review using the existing identifiers, and keep enough context to distinguish that transfer from any future invoice.
- Correct asset and network checked.
- Recipient amount and network fee reviewed.
- Full destination verified before authorisation.
- Transaction identifier saved privately.
- Recovery material never shared with the merchant.