Crypto Underpayment, Wrong Networks and Late Payments

Underpayments from exchange fees, USDT sent on the wrong network, payments that land after the checkout expired, fake tokens and refunds: why each happens and what to do about it.

TTillCrypto team8 min read

Most crypto payments go fine. The customer scans a QR code, sends the exact amount, and your order flips to paid. The ones that end up in your support inbox are the edge cases: crypto underpayment because an exchange took its cut, USDT sent on the wrong network, a transfer that lands five minutes after the checkout expired. Here's what causes each one and what to do.

Crypto underpayment: the exchange withdrawal fee trap

This is the most common one, and it's almost never the customer trying to cheat you.

Lots of people pay straight from an exchange account. On many exchanges the withdrawal fee comes out of the amount you type in. The customer enters 100 USDT, the exchange keeps its fee, and your address receives something like 99 USDT. The customer sees "100" in their withdrawal history and is sure they paid in full.

Your payment processor should do two things here:

  • Not mark the order as paid. A shortfall is a shortfall, and quietly accepting 99 for a 100 order means you eat the difference every time.
  • Not lose the money either. The transfer gets recorded and flagged so a human can look at it.

In TillCrypto, a transfer that doesn't exactly match an open order is saved as "unmatched" and reviewed by the TillCrypto team, not silently ignored. You won't see it in your dashboard, so your job is to collect the details and pass them on.

What to do on your side:

  1. Ask the customer for the transaction hash (TXID) and the payment ID or checkout link. Send both to TillCrypto support at support@tillcrypto.com, and we can attach the transfer to the order.
  2. Decide on a policy before it happens. Fulfil if the shortfall is small? Refund? If you want a top-up, create a separate payment for the difference (minimum 1 USDT) rather than having the customer send the gap to the same address, because a second loose transfer just becomes another unmatched one. For gaps under 1 USDT, fulfilling is usually the sane choice.
  3. Prevent it at the source. Add one line near your pay button: "Paying from an exchange? Make sure the amount received is exact, not the amount before fees."

One thing that catches people out: if support attaches a 99 USDT transfer to your 100 USDT order, you get a normal payment.paid webhook. The difference is that received_amount (99.00) is lower than amount (100.00). Compare the two before you ship anything.

Overpayment: when "close enough" breaks matching

Overpayment is rarer. Someone rounds up and sends 100.50 for a 100.00 order.

The obvious fix seems to be accepting anything at or above the amount. The catch is matching. If several orders share a receiving address and are told apart by amount, "at least 100.00" becomes ambiguous. Is that 100.01 transfer the 100.01 order, or an overpaid 100.00 order? Guess wrong and you credit the wrong customer.

So exact-amount systems treat an overpayment like any other mismatch. Record it, flag it, let a person decide. Slower for that customer, but it never credits the wrong order.

Once support has attached the transfer, either fulfil the order and refund the extra (if it's big enough to be worth a payout fee), or keep it as store credit if your business allows that. Tell the customer which one you're doing.

Late payments after the checkout expires

Checkouts expire for a good reason: a quoted amount and address can't stay reserved forever. TillCrypto defaults to 60 minutes, and you can set a different window per payment.

Real people blow through that. They open the checkout, realise they need to buy USDT first, wait for an exchange deposit, and pay 70 minutes later.

The expiry time shouldn't be a hard wall. A sensible gateway keeps watching the address for a grace period and keeps that amount reserved on that address, so no new order can claim it. TillCrypto still credits payments that are confirmed within about 30 minutes after expiry. The payment.expired webhook only goes out once that grace period is over, so "expired" means nothing arrived in time.

There's one exception worth planning for. If a transfer shows up even later and support attaches it to the order by hand, you'll get payment.paid for an order you may already have cancelled. Your handler needs an answer for that: re-reserve the stock, or refund.

In practice:

  • Don't release reserved stock or cancel the order at minute 60. Wait for the expired event (or your gateway's equivalent).
  • Handle payment.paid the same way whenever it arrives, even if your UI already told the customer the checkout timed out.
  • Make the handler idempotent. Failed deliveries are retried (1m, 5m, 15m, 1h, 6h, 24h), and anyone can hit "resend" in the dashboard, so the same event can reach you more than once.

Here's a short handler that covers those cases:

js
// Assumes the signature has already been verified
const eventId = req.headers['x-tillcrypto-event-id'];
if (await alreadyProcessed(eventId)) return res.sendStatus(200);

const p = event.data;
const orderKey = p.order_id ?? p.id; // payment links have no order_id

switch (event.type) {
  case 'payment.paid':
    // Can arrive after expiry, or after a manual review.
    if (Number(p.received_amount) < Number(p.amount)) {
      await flagForReview(orderKey, p.received_amount, p.txid);
      break;
    }
    // Must also work for an order you already cancelled.
    await markOrderPaid(orderKey, p.txid);
    break;
  case 'payment.expired':
    // Nothing arrived in time.
    await releaseStock(orderKey);
    break;
}
await markProcessed(eventId);
res.sendStatus(200);

If you haven't set up signature checks yet, read how to verify crypto payment webhooks first.

Two customers paying the same amount at the same time

Say you sell a 100 USDT product and two people check out within the same minute. If both are told "send 100 USDT to this address" and one 100 USDT transfer arrives, whose order is it?

There are two common ways to keep orders apart:

Approach How it works Trade-off
Unique address per order Every order gets a fresh address Clean matching, but more addresses to monitor and sweep, which costs network fees
Unique amount per address Orders on the same address get slightly different amounts Cheap to run, but the customer must send the exact figure

TillCrypto matches on address plus exact amount. If a 100.00 order is already waiting on every receiving address, the next one is quoted 100.01. The customer sees that exact figure on the checkout page, with the QR code and address next to it.

Two habits follow from this. Never write your own "send 100 USDT to T..." instructions in emails or chat; always send the customer to the checkout link, which shows the real amount. And in your books, look at what was actually received, not just the list price. The webhook payload carries amount, pay_amount and received_amount for exactly this reason. That extra 0.01 is yours.

Wrong token, wrong network, or fake USDT

Wrong network

USDT exists on several blockchains, and the same token on a different chain is a different asset. A TRON address starts with T, while Ethereum and BNB Chain addresses start with 0x, so most wallets and exchanges refuse to send ERC20 USDT to a TRON address. The dangerous pair is ERC20 and BEP20: both use 0x addresses, so nothing stops a customer from sending BEP20 USDT to an address that was only watching Ethereum.

A gateway that watches one chain never sees a transfer on another. There's nothing to flag, nothing to review. Whether the money can be recovered depends on whether the receiver controls the same address on the other chain.

If you only accept one network, say so loudly on the checkout and in your instructions. For a deeper comparison, see USDT TRC20 vs ERC20 vs BEP20.

Wrong token on the right network

Sending TRX to a USDT order, or the reverse, happens more than you'd expect. Same network, same address, different asset. It shouldn't be credited as the order's payment. In TillCrypto it's recorded as unmatched, same as a wrong amount, and the TXID-to-support routine above applies.

Look-alike tokens

Anyone can create a TRC20 token, name it "Tether USD" and give it the ticker USDT. Some wallets and explorers show it next to the real thing. Scammers use these to "pay" for goods with worthless tokens.

The name and symbol mean nothing. What counts is the token contract address. The real USDT on TRON is TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t, as listed on Tether's supported protocols page. Your payment system should check the contract of every incoming transfer and ignore everything else. TillCrypto does this and only counts confirmed transfers, so a pending or failed transaction never marks an order as paid. Look-alike tokens and tiny dust transfers aren't even recorded.

Refunds: there is no chargeback button

Blockchain transfers can't be reversed. No chargeback fraud, but every refund is a brand-new outgoing transfer, and mistakes are permanent. A few rules:

  1. Ask the customer for a refund address in writing. Don't just send it back to the from address. If they paid from an exchange, that address belongs to the exchange's hot wallet, not to them, and the funds may never reach their account.
  2. Confirm the network and token. Refund USDT on TRON to a TRON address, and say which network in your message.
  3. Decide who pays the network fee. Put it in your refund policy so it's not a negotiation each time.
  4. Copy the address from the customer's message, not your transaction history. Scammers send tiny transfers from look-alike addresses hoping you'll copy the wrong one.
  5. Keep the TXID of the refund and send it to the customer.

TillCrypto doesn't have a one-click refund. You can request a payout from your balance to the customer's address, but the 2 USDT network fee is deducted from the payout itself: to refund 10 USDT, request 12. The payout also has to be larger than that fee, so a 0.50 overpayment can't go back this way. Payouts are reviewed before they're sent on-chain, so tell the customer it may take a little while. More on how those fees work in TRC20 USDT transaction fees explained.

Quick reference

Problem Usual cause What the gateway does What you do
Underpayment Exchange deducted its withdrawal fee Flags it; credited only after manual review, with the real received amount Send TXID to support, compare received_amount with amount
Overpayment Customer rounded up Flags it; credited only after manual review, with the real received amount Fulfil and refund extra, or store credit
Late payment Customer was buying crypto first Grace period after expiry Wait for the expired event before cancelling
Same amount, same time Popular fixed-price product Unique amount or address per order Always use the checkout link
Wrong token, same chain TRX sent to a USDT order Flags it as unmatched Send TXID to support
Wrong chain Wrong network picked on exchange Never sees it Recovery depends on who controls that address on the other chain
Fake USDT Scam token with a copied name Verifies token contract, ignores the rest Never trust screenshots
Refund Customer request New outgoing transfer Written address, right network, add the fee, keep TXID

None of these are exotic. Sell for crypto long enough and you'll see all of them, so write your policy down now and link it from your FAQ. If you're still setting things up, accepting USDT payments on your website covers the basic flow.

Sources and further reading

Accept USDT on your website

Hosted checkout, signed webhooks and a test mode. 0% processing fee, no monthly fee.