What Does the Faucet Withdrawal Record Say Happened?

After a faucet withdrawal, begin with the faucet's own record. If no request exists, nothing was sent. If it is pending, the source still controls the queue. If it failed, correct the stated cause before trying again. Only a completed payout with operator evidence should be compared against the matching FaucetPay coin history. This page is the quick triage; the full reconciliation belongs to the dedicated missing-reward guide.

Save the withdrawal screen before refreshing

Record the faucet account, coin, gross amount, deduction, recipient, request time, status and request ID. A disappearing source balance without a withdrawal row is not proof that a FaucetPay payment was created.

Use the Source-State Triage Card

Place the request in one state.

• Not created: no withdrawal record or request identifier exists
• Queued or pending: the faucet still owns the processing clock
• Failed or rejected: the source has returned an error or final negative state
• Completed without operator proof: the label exists but no traceable send record is available
• Completed with payout evidence: coin, amount, recipient and FaucetPay payout identifier can be matched

Not created means the form did not finish

Check whether an email confirmation, checkbox, minimum balance or final button was missed. Do not contact FaucetPay because it has no source request to investigate. Correct the form only after confirming that another request was not silently created.

Pending means the faucet clock is still running

Use the schedule saved from the source: instant, fixed batch, daily processing or manual review. FaucetPay cannot release a request that the operator has not sent. Avoid repeated withdrawal clicks while the first item remains active.

Failed requires the exact reason

Common source-level causes include an invalid recipient, unsupported coin, insufficient eligible balance or operator funding issue. Save the wording. A generic failure should be clarified by the faucet before the user edits several fields at once.

Completed needs more than a green badge

FaucetPay's API can return a successful payout response and a payout ID. Ask the faucet for the coin, native amount, masked recipient, completion time and identifier. That record is stronger than a screenshot that says paid without identifying the transfer.

Check the exact FaucetPay coin history

Open the individual asset history and compare the native amount around the saved time. Do not rely on the total USD estimate. An internal faucet payment may have no public blockchain hash, so the account ledger is the expected recipient evidence.

Use the full reconciliation only after triage

When the source state and FaucetPay history disagree, move to the detailed four-record guide. It compares the original claim, faucet payout log, FaucetPay history and operator response. Repeating that entire process inside every short troubleshooting page would create duplicate content rather than help the reader.

Pause further claiming

Do not build a larger faucet balance while the smallest withdrawal is unresolved. Another payout can overlap with the same coin and recipient, making the first dispute harder to trace.

Compact support handoff

Contact the faucet first with the request ID, status, coin, amount, masked recipient and time. Contact FaucetPay only when the operator supplies matching successful payout evidence but the correct account history remains empty.

Never send account secrets

Neither support team needs the FaucetPay password, authenticator code, seed phrase or private key to trace an internal payout. The faucet operator's API key also belongs only on its server.

Evidence boundary

A source status tells you which system currently owns the request. It does not by itself prove receipt. The final result is either a matching FaucetPay history entry, a documented failure or an unresolved mismatch handed to the correct support team.

Evidence sources for payout triage

The current FaucetPay API and help material was reviewed on July 30, 2026 to distinguish operator-side payout records, internal coin history and later blockchain withdrawals.

• FaucetPay send response and payout identifiers: https://beta.faucetpay.io/api-docs
• Claiming and receiving guidance: https://faq.faucetpay.io/knowledge-base/how-do-i-start-receiving-payments-claiming-on-faucets/
• 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 support portal: https://faucetpay.io/page/open-ticket

FAQ