Topping up with crypto removes most of the friction that breaks a regular transfer: no card tied to a country, no dependency on a bank's working hours, and the credit lands the moment the network confirms the transaction rather than on a payment gateway's schedule. Here is the process step by step, what matters when you send the transfer, and what to do if the payment does not show up.
Why a crypto top-up beats a bank transfer
The main advantage is having no tie to banking geography. A transfer can be sent from any address in any country: the sender's card jurisdiction, the bank's support for foreign transfers, and the account currency simply do not matter. A payment description that sometimes gets a bank transfer blocked is not a filter here either — the network does not read purpose fields.
The second difference is how crediting works: the balance updates not because an operator checked the payment by hand, but because the transaction collected the required network confirmations, automatically, regardless of time zone, weekend, or support desk load.
The top-up process: four steps
The process always follows the same order, and no step can be skipped:
- Choose the top-up amount in your account.
- Get a deposit address and the exact amount to send in the selected network — both generated for this specific request and valid for a limited time.
- Send the transfer as a single transaction: to that address, on that network, for that exact amount. No need to split the payment into several transfers.
- Wait for network confirmations — the balance is credited automatically, with no further action from you.
Address and network must match — this is critical
A transfer is processed by the network, not by the recipient personally. If the address is correct but the network is wrong, the transaction reaches neither the balance nor the sender: funds move into a network that does not service that address, with no way to recover them. A network mismatch is the most common cause of a lost top-up, irreversible by the blockchain's own design, not by service policy.
Before sending, check the address character by character and the network specified in the request itself, not whatever your wallet defaults to. A separate trap is an expired request — if the amount is not sent within its window, do not reuse the old address; generate a fresh request instead.
The exact amount and the network fee are not "roughly"
A request is issued for an exact amount, not a range. Sending a rounded, "close enough" amount from an exchange address — normal for internal transfers — almost never matches the requested figure: the system gets more or less than expected and cannot automatically match the payment to a specific top-up, so it needs a manual review.
The network fee is a separate cost paid on top of the amount, not deducted from it. Send exactly the requested amount and let the fee come out of it, and less than required reaches the balance, so the request does not close. Fee size depends on network load and is not fixed, so budget a small margin rather than sending an amount that exactly matches your wallet balance.
How long crediting takes and what to do if a payment does not appear
A typical crediting time is a few minutes to an hour, depending on how many confirmations the chosen network requires and how busy it currently is. During peak load, confirmation simply takes longer, and that has nothing to do with the service itself.
If a reasonable amount of time has passed, the balance has not updated, and the transaction is already confirmed on the network, contact support through a ticket and attach the transaction hash. With the hash, the payment is matched to the request manually within minutes; without it, the search takes far longer, since the operator has to cross-check incoming payments by amount and time.
Frequently Asked Questions
What happens if I send the transfer on a different network than the one specified?
The transaction reaches neither the balance nor the sender. The network it was sent on does not service an address issued for a different network, so the funds cannot be recovered — a limitation of the blockchain, not of the service.
Can I top up by sending a transfer straight from an exchange address?
Technically yes, but you must enter the exact address, network and amount manually — rounding "for convenience" is not an option, or the payment will not match automatically and will need a support ticket with the transaction hash.
Why does the balance sometimes get credited with slightly less than what was sent?
The usual reason is that the network fee was deducted from the transfer instead of being sent on top of it. A request is calculated for the exact amount that should land on the balance, so the fee always needs to be added, never subtracted.
Check top-up status and the full debit history under transaction history and in your account dashboard, which also shows how the shared balance across products is spent. To top up with crypto right now, go to balance.