Crypto eSIM payment failed or stuck: what to check first

Something went wrong. The page didn't turn green. The eSIM didn't arrive. Your wallet says the transaction is confirmed. Now what.

Almost all of these are one of four failure modes, and three of the four are fully recoverable. Here is how to tell which one you're in.

Failed vs pending vs stuck

These words get used interchangeably and shouldn't be.

• Failed — the transaction never made it onto the blockchain. Funds still in your wallet. You can retry.
• Pending in the mempool — broadcast but not yet in a block. Common on Ethereum when you underpaid gas. Locked but not gone.
• Confirmed but not credited — done on-chain but the merchant hasn't marked your order as paid. Roughly 80% of "help" tickets live here.
• Sent to nowhere useful — wrong address or wrong network. See the last section.

The clue for which one you're in is on the block explorer, not the confirmation page.

Step 1: check the transaction, not the tab

1. 1

   Get the transaction hash

   In your wallet, open the transaction history. Copy the hash — a long string of hex characters. This is the transaction's public identifier and every subsequent step needs it.

2. 2

   Open the right explorer

   • Tron: tronscan.org
   • Ethereum / Base / Polygon: etherscan.io / basescan.org / polygonscan.com
   • Solana: solscan.io
   • BNB Chain: bscscan.com

   Paste the hash. If the page says "not found", the transaction never broadcast — you're in the "failed" case, not a support case. Retry in your wallet.

3. 3

   Read three fields

   • Status: Success, Pending, or Failed.
   • Amount: the number the recipient actually received (this is the important one — not what you typed).
   • To: the destination address. Compare its first 4 and last 4 characters to the address on the checkout page.

Ninety percent of tickets close themselves at Step 3.

The four scenarios and their fixes

1. Status: Failed / not found on explorer

The transaction didn't happen. Funds still where they started. Refresh your wallet to confirm.

Fix: retry. If it keeps failing at the wallet level, the usual causes are insufficient gas token (no TRX on Tron, no ETH on Ethereum), a nonce collision from a stuck earlier transaction, or the wallet is offline.

2. Status: Pending, no confirmation for 20+ minutes

Almost always an Ethereum mainnet gas issue — you broadcast below the current market and miners are ignoring you.

Fix: in your wallet, use "speed up" (raises the fee on the same transaction) or "cancel" (replaces it with a zero-value self-send at higher fee, freeing the nonce). Both cost a little more gas. Neither loses funds.

3. Status: Success, amount matches, but no eSIM

This is an underpayment and it needs a human to reconcile. Open a support ticket with:

• Order number
• Transaction hash
• The exact amount received per the explorer
• The exact amount quoted on the checkout

Resolution is usually a top-up request for the small difference — send the shortfall on the same network to the same address, quoting the hash, and the order releases. Typical time: 15 minutes to an hour depending on queue.

4. Status: Success, but the network is wrong

You sent USDT-TRC20 to what was meant to be a USDT-ERC20 invoice, or vice versa. The blockchain worked exactly as you told it to.

Two sub-cases:

• Address exists on both networks (possible for EVM-family chains). Recovery may be possible if the merchant controls the same address on the target chain. Not a promise, but a possibility.
• Address only exists on one network. The funds are at that address on a chain the merchant has no key for. Recovery is not guaranteed and is not fast.

The blockchain does not know you meant to send it somewhere else. It only knows you signed for what you signed for.

What speeds up your resolution

• Transaction hash, copied from the wallet before you close it.
• The block explorer link, not a screenshot of your wallet UI.
• The exact amount received (from the explorer), not the amount you typed.
• The network name in full — 'USDT on Tron', not just 'USDT'.
• Your order number from the checkout confirmation page.

With those five things, most tickets close in one reply. Without them, it's a back-and-forth to establish what happened before anyone can fix it.

What we can't do

There is a small class of problems that support cannot fix. Funds sent to a wallet the merchant does not control. Funds sent on a network the merchant has no infrastructure for. Chargeback-style reversals — crypto does not have those.

For everything else — underpayments, overpayments, stuck-in-mempool, wrong-order — the fix exists and is usually cheap. Just send the hash first.

Read this next

The underpayment case is the one that never had to happen. Sending the exact amount at a crypto checkout covers the wallet setting that causes it and how to make sure your "15.00" arrives as 15.00.