NetGrid Host

Paying with crypto: why the amount must match to the last digit

Our crypto gateway identifies your payment by its exact amount. Send a different sum — even one digit off — and the payment cannot be matched and is lost. Here is why, and how to pay safely from an exchange.

5 min read·Last updated 2026-10-06

Crypto payments on NetGrid Host are credited automatically, without a payment processor, KYC forms or waiting for an operator. The price for that convenience is one strict rule: the amount that arrives at our wallet must be exactly the amount shown on the payment page. Not approximately. Exactly, to the last decimal place.

How a crypto payment is identified

Unlike a bank transfer, a blockchain transaction has no payment reference, no invoice number and no sender name we could trust. Many customers pay to the same receiving address at the same time. The only thing that distinguishes your payment from everyone else's is the amount.

That is why every invoice gets a unique sum: the price in the chosen coin plus a small unique tail after the decimal point (for example 7.9887 USDT instead of 7.98). Our system watches the wallet and matches each incoming transaction to the invoice with that exact amount. The decimal digits are the invoice number.

What happens when the amount differs
If a different sum arrives — less or more, even by one digit — there is no invoice with such an amount, so the transaction cannot be matched to you and is not credited. From the system's point of view the money has arrived from nowhere. Such a payment is considered lost; it cannot be refunded, because we cannot reliably prove whose it was.

Why exchanges and some wallets break the amount

  • Withdrawal fee deducted from the amount. You type 7.9887, the exchange takes its fee from it, and 6.9887 arrives. Exchanges rarely let you pay the fee on top.
  • Rounding. Some exchange withdrawal forms accept only two or four decimals, so the last digits are cut off or rounded.
  • Minimum and step limits. A withdrawal form may silently round the amount to its allowed step.
  • Wrong network. USDT sent as ERC-20 or BEP-20 never reaches a TRC-20 address; TON sent without the correct address format is lost as well.
  • Paying two invoices with one transaction, or splitting one invoice into two transfers. Neither can be matched.

The result in all these cases is the same: the amount on the blockchain is not the amount of your invoice, and the payment cannot be identified.

The safe way: pay from your own wallet, not from an exchange

If your exchange or wallet cannot send an exact sum with all decimal places, do not pay from it directly. Move the funds to a wallet you fully control first, then send the exact amount from there. A self-custody wallet lets you type any amount with any number of decimals and shows the network fee separately, so what you type is what arrives.

We recommend SafePal — a free software wallet for iOS and Android with a cold-storage mode; it supports TRON (USDT TRC-20, TRX), Bitcoin, Litecoin, TON, Dogecoin and Solana. Any other self-custody wallet that lets you enter the full amount works too (for example Trust Wallet or Tonkeeper for TON).

  1. Withdraw a bit more than the invoice from the exchange to your own wallet — enough to cover the invoice and the network fee of the next transfer.
  2. Open the payment page, pick the coin and network, copy the amount with the Copy button (do not retype it by hand).
  3. In your wallet, paste the receiving address and the copied amount. Check the network: USDT and USDC must go via TRC-20 (TRON).
  4. Make sure the fee is charged on top of the amount, not deducted from it, and send.
  5. Keep the payment page open: it checks the blockchain every few seconds and confirms the payment automatically. The invoice is valid for 3 hours.

Quick checklist before you press Send

AmountCopied from the payment page, all decimals included
FeePaid on top; the wallet shows the exact amount that will arrive
NetworkMatches the one on the payment page (TRC-20 for USDT/USDC, native chain for the rest)
One invoiceOne transaction, one invoice; no merging or splitting
TimeSent before the invoice expires (countdown on the page)

I have already sent a wrong amount — what now?

Open a support ticket and attach the transaction hash (TXID), the coin, the amount you sent and the invoice amount. We check such cases by hand. Please understand that this is a manual investigation, it takes time, and crediting cannot be guaranteed — an unmatched transaction is treated as lost under our Refund Policy.

This is not a formality
The exact-amount rule is not our whim and not a trick to keep your money. It is the only way to identify a payment on a public blockchain without a payment processor. Every automatic crypto gateway that uses shared addresses works this way.

NetGrid Host

VPS from€1.99/ month

Unlimited traffic, a 1 Gbps port and NVMe storage. 12 locations across Europe & the US.

Unlimited traffic·1 Gbps port·12 locations