The Faucet Says Paid. FaucetPay Says Zero. Who's Right?

Both can be telling the truth. 'Paid' is a word the faucet puts in its own database, and different sites use it for different moments. On one site it means the withdrawal was approved. On another it means a batch was closed, or that a request went out to FaucetPay. Sometimes it means a blockchain transaction was sent. Only some of those moments put money in your account. So treat Paid as the faucet's claim, then check it against the one record that settles the question: the history for that coin in your FaucetPay account. The useful question isn't 'did they pay?' but 'how, to whom, and in what coin?' Most cases are solved once you know that.

The short answer

Treat Paid as unconfirmed until it matches something in FaucetPay. You need four things from the faucet's withdrawal record: the coin, the amount, the exact recipient it used, and whether it paid internally through FaucetPay or with an on-chain transaction. Then look at the history for that coin in FaucetPay, not the dollar total on the dashboard. If all four line up with an entry, you've been paid. If one doesn't, that's where the problem is.

'Paid' doesn't mean the same thing everywhere

There's no standard definition. Read the faucet's withdrawal legend or help page before assuming the strongest meaning. Depending on the site, Paid can mean any of these:

• An admin approved your request.
• Your request was added to a batch that has since closed.
• The faucet sent a request to FaucetPay's API, which may or may not have succeeded.
• FaucetPay accepted the payment and credited an account.
• A blockchain transaction was broadcast.

Your faucet balance dropping proves very little

Many faucets deduct the amount as soon as you request a withdrawal, before anything is sent. The number going to zero shows the faucet moved it out of your available balance. If the payment fails later, some sites refund it and some don't. Either way, the drop isn't delivery.

Save the withdrawal row before it changes

Capture the whole row, not just a cropped green badge. You want the withdrawal ID, status wording, coin, amount, the destination (even if partly masked), when you requested it, when it was marked Paid, and any reference or note field. Note the time zone too. Faucets and FaucetPay don't always use the same clock, and a two-hour offset can make a real entry look missing.

Make sure you're looking at a withdrawal, not a claim

A claim that says 'paid' often only means the reward went into the faucet's internal balance. FaucetPay won't see anything until there's a separate withdrawal or auto-payout. If you can't find a withdrawal entry at all, you're a step earlier than this page. See the guide on rewards that aren't showing yet.

Three ways a faucet can pay you

Which one your faucet used decides what evidence should exist.

• Internal API payout: the faucet sends from its FaucetPay balance to your account using FaucetPay's API. No blockchain transaction. The faucet gets a payout ID back, and you get an entry in your coin history.
• Direct transfer: a FaucetPay user sends to your username or email inside FaucetPay. Also no blockchain transaction, instant and irreversible.
• On-chain deposit: the faucet sends a normal blockchain transaction to your FaucetPay deposit address. There should be a transaction hash (TXID) you can look up on an explorer.

If it was an internal payout

Searching a block explorer won't help, because the payment never touched a blockchain. Ask the faucet whether its API call to FaucetPay succeeded, and for the payout ID tied to your withdrawal. FaucetPay's API returns that ID on a successful send and reports failed sends separately. A faucet that marks rows Paid before checking the response is a common source of exactly this problem.

If it was an on-chain deposit

Then there should be a TXID, and you can check it yourself. Open it on the explorer for the right network and confirm it exists, that it went to your current FaucetPay deposit address, that the coin and amount match, and that it has confirmations. A string the faucet calls a TXID that no explorer can find isn't proof of anything.

Common reasons the balance stays at zero

Most Paid-but-zero cases fall into one of these. Go through them before contacting anyone.

The payout came in a different coin

Multi-coin faucets often show rewards in satoshi or dollar equivalents and convert at withdrawal into whichever coin was selected. You're checking BTC while the row says LTC. Read the coin on the withdrawal row and open that history. Also scan recent activity by time and amount across all coins.

It went to another FaucetPay account

An old email, a second account or a one-letter typo in a username sends an internal payment somewhere else, and internal payments are instant and can't be reversed. Compare the masked recipient on the faucet's row with the email and username you're logged in with. Don't create a new account to 'test' it.

It went to your linked address instead of your deposit address

This one catches people out. In FaucetPay, a deposit address receives crypto into your account. A linked address is your own external wallet, used when money leaves FaucetPay. If you gave the faucet your linked address, the payment went straight to your external wallet. FaucetPay will correctly show zero. Check that wallet.

The deposit was below FaucetPay's minimum

FaucetPay applies minimum deposits per coin and network to on-chain deposits. A faucet that sends a tiny amount on-chain to your deposit address can reach the right place and still not be credited. This doesn't apply to internal API payouts, which is another reason to find out which route was used. Sending more on top won't fix a deposit that's already below the minimum.

Wrong network or unsupported token

Tokens with the same ticker exist on several chains, and some 'USDT' isn't the USDT FaucetPay supports. FaucetPay warns that unsupported tokens sent to its addresses may not be credited, and recovery isn't guaranteed. If the faucet sent on-chain, check the network and token contract on the explorer, not just the symbol.

The batch was marked Paid, but your payment failed

Some operators mark a whole batch Paid when they close it, even if a few sends inside it failed. A screenshot of hundreds of green rows doesn't explain your missing one. Ask about your withdrawal ID specifically.

Check FaucetPay properly, once

Sign in on the official FaucetPay site, open your transaction history, pick the coin named on the withdrawal row and look at the right date range in coin units. FaucetPay itself points out that the dollar estimate moves with prices, and a tiny balance can show as roughly zero dollars while the coins are there. A normal refresh is fine. A second withdrawal, a second account or a 'test deposit' aren't.

What to ask the faucet

The faucet wrote Paid, so it should explain it first, unless you already have a valid TXID showing delivery to FaucetPay. A link to its general payment-proof page doesn't answer the question. Ask about your withdrawal ID specifically:

• What made this row change to Paid?
• Did the FaucetPay send succeed or fail?
• Which recipient did it go to (masked is fine)?
• Which coin and how much?
• What's the payout ID or TXID?
• Was it retried or refunded?

When it's FaucetPay's turn

Contact FaucetPay when there's real delivery evidence for your account. That means either a payout reference that should map to you, or a confirmed on-chain deposit that went to your correct deposit address, on a supported network, above the minimum. For on-chain deposits FaucetPay asks for the address, amount, network and TXID. Attach the faucet's withdrawal row as well.

Don't try another payout as a test

A second request can duplicate a delayed payment, repeat the same wrong recipient, or get merged into another batch and muddy the evidence. Wait until the first row is formally failed, refunded or reversed, fix whatever was wrong, and then try again.

Nobody needs a fee to release a payout

If anyone asks for an activation deposit, tax, 'wallet synchronization' fee or account upgrade before your reward appears, that's a new payment from you to them, not a way to recover the old one. Keep your screenshots and stop sending anything. The same goes for anyone offering 'recovery' for an upfront fee or asking for remote access, your seed phrase or private keys.

Rule out an account problem

A zero balance can also mean something left your account. Look at the full history, including withdrawals, transfers, swaps and games. If you see anything you don't recognise, FaucetPay's advice is to change your password, scan your device and turn on app-based 2FA. Keep the 2FA recovery key somewhere separate. That's a security incident, not a missing payout, and it's more urgent.

Four real-world patterns

The same symptom, four different endings.

• The batch closed, the send didn't: a 12 DOGE row is marked Paid at midnight with no payout ID. The operator later confirms the export finished but the API call failed. The faucet has to fix it.
• Paid to the wrong place: an LTC withdrawal went to a saved address that turned out to be the user's linked wallet, not the FaucetPay deposit address. The TXID is valid and the coins are in the external wallet. Nothing is lost.
• Arrived but too small: a tiny on-chain token payment reached the right deposit address with a valid TXID, but under the minimum for that network. It becomes a deposit question for FaucetPay.
• Right money, wrong tab: the faucet displayed satoshi values but paid in LTC. The LTC entry was sitting in FaucetPay all along while the user checked BTC.

The rule to remember

A faucet can say Paid. It can't decide what's in your account. Find out how it paid and to whom, then ask for the matching evidence: a payout ID and a history entry for internal payments, or a valid TXID to the right address, network and minimum for on-chain ones. Until that lines up, stop claiming and leave the burden of proof with the faucet.

Sources

We re-checked FaucetPay's API reference on October 31, 2026, including payout IDs, recipient types and failed-send handling. The help pages below explain deposit and linked addresses, minimums, unsupported tokens, transaction history and 2FA. These describe FaucetPay's own rules. They don't endorse any faucet.

• FaucetPay current API reference: https://beta.faucetpay.io/api-docs
• FaucetPay API service overview: https://faq.faucetpay.io/knowledge-base/what-kind-of-api-does-faucetpay-offer/
• FaucetPay receiving faucet payments: https://faq.faucetpay.io/knowledge-base/how-do-i-start-receiving-payments-claiming-on-faucets/
• 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 Direct Transfer guidance: https://faq.faucetpay.io/knowledge-base/how-do-i-transfer-from-one-account-to-another/
• FaucetPay deposit versus linked addresses: https://faq.faucetpay.io/knowledge-base/whats-the-difference-between-deposit-and-linked-addresses/
• FaucetPay supported coins and networks: https://faq.faucetpay.io/knowledge-base/what-currencies-do-you-work-with/
• FaucetPay minimum-deposit guidance: https://faq.faucetpay.io/knowledge-base/is-there-a-minimum-deposit-at-faucetpay/
• FaucetPay confirmed-deposit troubleshooting: https://faq.faucetpay.io/knowledge-base/my-deposit-wasnt-credited-what-now/
• FaucetPay unsupported-token guidance: https://faq.faucetpay.io/knowledge-base/can-i-deposit-tokens-in-faucetpay/
• FaucetPay app-based 2FA guidance: https://faq.faucetpay.io/knowledge-base/what-is-2fa-and-how-do-i-enable-it-in-my-account/
• Faucet Crypto completed-withdrawal tracking guide: https://knowledge-base.faucetcrypto.com/withdrawals/track-withdrawal
• FTC task-scam and deposit-to-unlock warning: https://consumer.ftc.gov/consumer-alerts/2025/08/how-spot-avoid-task-scams

FAQ