Where Did the Completed FaucetPay Withdrawal Stop After Broadcast?

A completed FaucetPay withdrawal should have a blockchain transaction hash. Start with that hash, not the wallet app balance. If the transaction is unconfirmed, it is still a network problem. If it is confirmed to the correct address, FaucetPay says it no longer controls the funds; the next investigation belongs to the self-custody wallet display or the receiving exchange's deposit system.

Open the exact withdrawal record

Save the FaucetPay withdrawal ID, coin, network, gross amount, fee, net amount, destination, completion time and transaction hash. Do not investigate from a screenshot that hides the destination or selected network.

Use the Receiver Ownership Map

Identify the first incomplete stage.

• TXID absent or invalid: the completed platform record needs FaucetPay investigation
• TXID valid but unconfirmed: the blockchain has not finalized the transfer
• Confirmed to a different address: the destination instruction was wrong
• Confirmed to the correct self-custody address: inspect wallet network and token display
• Confirmed to an exchange-controlled address: inspect exchange confirmations, minimum, memo and account credit

A transaction hash must be opened on the correct network

A valid-looking hash can return no result on the wrong explorer. Match the FaucetPay withdrawal network, then search the TXID on that chain's established explorer. Confirm the status, recipient, amount and block time.

Unconfirmed is not completed at the receiving layer

FaucetPay can finish internal processing and broadcast the transaction while the network still has not included it in a block. Confirmation time depends on network conditions and the fee used. Do not submit another withdrawal while the first transfer remains visible and unconfirmed.

Confirmed to the wrong address is not a display issue

Compare the explorer recipient with the address copied from the intended wallet or exchange. Blockchain transactions generally cannot be edited after confirmation. Determine whether the address belongs to another account you control, a custodial platform or an unknown party.

Confirmed to the correct self-custody address

The on-chain transfer has reached the keys controlling that address. If the wallet still shows zero, switch to the network used, open the correct account and verify the address balance on the explorer. For tokens, the wallet may need the authentic contract added to its display.

A token can arrive without the gas asset needed later

Receiving USDT or another token does not automatically supply ETH, BNB, POL or TRX needed for a later outgoing transaction on the chosen network. This does not mean the FaucetPay withdrawal failed. It means the received balance may not yet be movable.

Confirmed to an exchange address

An exchange can wait for additional confirmations, enforce a deposit minimum, require a memo or destination tag, pause deposits during maintenance or review the account. Check the exchange deposit history and official asset-specific instructions.

Net amount must clear the exchange minimum

Compare the amount shown on-chain after FaucetPay's deduction with the receiving exchange's current minimum. Kraken warns that deposits below a required minimum can fail, while other platforms may aggregate or delay them. The receiver's rule, not the gross FaucetPay amount, controls credit.

Memo or tag is part of the destination

For assets such as XRP or XLM at custodial services, the address can belong to a shared exchange wallet and the memo or tag identifies the customer. A confirmed transfer to the shared address can remain uncredited when the identifier was omitted or wrong. Only the receiving service can assign it.

Worked self-custody case

A USDT withdrawal is confirmed on BNB Smart Chain to the user's 0x address. The wallet is currently displaying Ethereum and does not show the token on BSC. After switching networks and adding the verified token contract, the balance appears. FaucetPay completed its role correctly.

Worked exchange-credit case

An XLM withdrawal is confirmed to the exchange's shared Stellar address, but the memo was missing. The blockchain movement succeeded, while the exchange cannot map it automatically to the customer's account. The user supplies the TXID, amount, address, correct memo and account details to the exchange's official support.

When FaucetPay still owns the question

Contact FaucetPay when its completed record has no usable TXID, the hash does not describe the recorded withdrawal or the transaction was sent to an address different from the confirmed withdrawal instruction. Include one detailed ticket rather than several partial reports.

When the receiving wallet owns the question

FaucetPay's current help says that after a confirmed transaction reaches the correct address, it no longer controls the funds. Contact the wallet or exchange with the TXID and route details. A self-custody software provider cannot reverse a correct on-chain transfer but can help diagnose display and account selection.

Do not pay a recovery stranger

A block explorer lookup never needs a seed phrase, private key or remote-control session. Ignore anyone guaranteeing reversal or exchange credit for an upfront crypto payment. Use only the official receiving service's recovery process.

Build the correct support packet

Include the FaucetPay withdrawal ID, TXID, asset, exact network, gross and net amounts, destination, memo or tag, confirmation count, completion time and screenshots. State the first incomplete stage instead of saying only that the money is missing.

Do not resend until the first route is classified

A second withdrawal can repeat the wrong address, network, memo or below-minimum amount. Resolve the original record, rebuild the destination packet and use a valid small test only after the failure is understood.

Evidence reviewed on July 30, 2026

Official FaucetPay, wallet and exchange documentation supports the post-broadcast ownership split. Destination rules remain asset-, network- and platform-specific.

• FaucetPay completed-withdrawal troubleshooting: https://faq.faucetpay.io/knowledge-base/i-havent-received-my-withdrawal-what-not/
• FaucetPay transaction-history guidance: https://faq.faucetpay.io/knowledge-base/i-had-balance-in-my-account-and-now-its-not-there-where-did-it-go/
• FaucetPay unconfirmed-transaction guidance: https://faq.faucetpay.io/knowledge-base/unconfirmed-transaction-what-should-i-do-now/
• MetaMask missing-token and network checks: https://support.metamask.io/manage-crypto/tokens/what-to-do-when-your-balance-of-tokens-is-incorrect/
• Kraken missing-deposit checks: https://support.kraken.com/articles/360001488126-cryptocurrency-deposit-is-missing
• Coinbase destination tag and memo guidance: https://help.coinbase.com/en/coinbase/trading-and-funding/sending-or-receiving-cryptocurrency/destination-tag-memo-faq

FAQ