Where Was the Faucet Supposed to Send the Payment?

The word “paid” does not identify a destination. It may mean the faucet completed an internal record, sent a FaucetPay micro-payment, broadcast a direct wallet transfer or submitted a deposit to an exchange address. Start with the payout method saved before the request. Then follow only that branch and stop at the first record that does not exist.

Use the Four-Branch Paid Destination Map

Select the route that the faucet actually promised.

• Branch A — source marked paid but exposes no external payment record
• Branch B — FaucetPay internal payout
• Branch C — direct blockchain transfer to a self-custody wallet
• Branch D — blockchain deposit to an exchange or custodial account

Record the payout claim before troubleshooting

Save the source account, coin, amount, paid time, payout ID, recipient, stated method and any TXID. A screenshot containing only a green Paid label cannot identify the route.

Branch A — paid exists only in the faucet ledger

Ask whether the source created a withdrawal reference, FaucetPay payout ID or blockchain hash. If it cannot identify a recipient or external record, the faucet still owns the explanation. Do not contact the wallet with only a source screenshot.

Branch B — FaucetPay internal credit

The FaucetPay API can send to an email, username, supported address or payout hash and return a platform payout ID. Open the exact coin history in the intended account. A personal blockchain TXID may not exist because the payment can settle internally.

Check FaucetPay recipient and coin

Compare the saved email, username or address with the account and confirm the native currency. A payment sent as LTC will not appear in BTC history. A source-side completed label with the wrong recipient remains a source problem.

Branch C — direct self-custody transfer

Require the TXID and exact network. Open the matching explorer and compare status, recipient, asset and amount. A successful transfer to the correct address proves that the blockchain ledger changed even if the wallet interface remains empty.

If the explorer has no successful transaction

An invalid hash, failed transaction, unrelated recipient or wrong chain means the faucet has not proved payment to the intended wallet. Return to source support with the discrepancy.

If the explorer shows the correct asset at the address

The issue is now wallet display or account selection. MetaMask currently advises checking the correct network, comparing the address on the explorer and manually adding a token when the blockchain balance exists but the interface does not detect it.

Check the selected account, not only the wallet app

One wallet can contain several derived or imported addresses. Compare the complete explorer recipient with the active account. Restoring the correct seed phrase does not guarantee that the interface has selected the same derived account.

Check token contract and network

A token can be on another EVM network or hidden from the wallet’s default list. Use the contract from the successful explorer record and a trusted official source. Do not add a token supplied by an unsolicited support message.

Branch D — exchange deposit

A successful TXID at an exchange address is not the final account credit. The exchange can require more confirmations, a memo or tag, a minimum deposit and internal processing. Compare the current deposit instructions with the on-chain transaction.

Below-minimum exchange deposits need a separate decision

The transfer can be real while the exchange refuses to credit it because the net amount is too small. Do not send a top-up unless the exchange’s current recovery policy explicitly says cumulative credit is supported.

Paid can refer to a batch, not final confirmation

Some faucets mark a payment paid when it enters the operator’s payout system or batch. Require a specific FaucetPay record or TXID. The status word alone should not be promoted to evidence of wallet receipt.

Worked FaucetPay branch

A faucet records paid DOGE and provides a FaucetPay payout ID. The user’s general dashboard looks unchanged, but the DOGE history contains the matching native amount. The payment succeeded; the wrong view caused the empty-wallet conclusion.

Worked hidden-token branch

A faucet provides a successful Polygon USDC transaction to the correct 0x address. The wallet is showing Ethereum Mainnet and has not detected the Polygon token. Switching to the correct network and adding the verified token reveals the balance.

Worked false-payment branch

The source shows paid but supplies a hash for another address and amount. The wallet is empty because the faucet has not proved payment to the saved destination. The user pauses all claims and opens one source ticket.

Use the current-owner rule

No external record means source support. A valid FaucetPay payout ID with no matching internal history can involve the source and FaucetPay. A correct on-chain wallet balance with a blank interface is a wallet-display issue. A correct exchange deposit after required confirmations belongs to the exchange.

Do not resend or change destinations during diagnosis

A second payout can create an overlapping amount and another recipient. Preserve the original route until the first payment is reconciled.

Destination-branch technical references

The wallet, exchange and FaucetPay documentation below was checked on July 30, 2026. It supports the split between internal credits, direct transfers and custodial deposit processing.

• FaucetPay payout recipients and payout IDs: https://beta.faucetpay.io/api-docs
• MetaMask incorrect or missing token balance: https://support.metamask.io/manage-crypto/tokens/what-to-do-when-your-balance-of-tokens-is-incorrect/
• FaucetPay claiming overview: https://beta.faucetpay.io/help/getting-started/claiming-from-faucets
• Coinbase memo and destination tag guidance: https://help.coinbase.com/en/coinbase/trading-and-funding/sending-or-receiving-cryptocurrency/destination-tag-memo-faq
• Kraken deposit statuses: https://support.kraken.com/articles/360000674066-cryptocurrency-deposit-statuses

FAQ