Supported for Which Action: Faucet Payout, Deposit, Swap or Withdrawal?

FaucetPay does not have one universal meaning of ‘supported coin.’ A currency can appear in the deposit catalogue, the faucet payout API, an account balance or an external withdrawal screen without every route being identical. The current public documents show a broader deposit catalogue than the operator payout catalogue. A faucet user should verify the function being used, not copy the longest list.

Use the Five-Function Coin Passport

Record a separate yes, no or not confirmed result for each function. A single Supported label is too broad for a real route.

• Faucet receipt: can an operator currently send this coin through the FaucetPay payout system?
• Blockchain deposit: can the user send this asset into FaucetPay on the required network?
• Internal transfer: can the balance move between FaucetPay users without an on-chain transaction?
• Coin Swap: can the balance be exchanged now with adequate liquidity and an acceptable quote?
• External withdrawal: can the asset leave on a network accepted by the intended wallet or exchange?

The current deposit snapshot contains twenty-one assets

The June 2026 deposit documentation contains twenty-one assets. It covers established native coins, smart-contract platform assets, stablecoins and several currencies absent from the current operator payout catalogue. The page answers what can enter FaucetPay, not what every faucet can send internally.

The faucet payout snapshot is shorter

The public API marks fourteen currencies active for operator payouts. Seven assets shown in the deposit catalogue were not present in that payout snapshot. That numerical gap is the practical reason to maintain separate fields in the Coin Passport.

Deposit support does not promise faucet receipt

An XRP address in the Wallet can accept a supported XRP blockchain deposit. It does not prove that a third-party faucet can call FaucetPay’s payout endpoint with XRP. The source must show a current payout option and the platform payout tools must permit the currency.

Payout support does not promise a usable exit

An internal USDT reward can reach the FaucetPay ledger while the later external route remains unsuitable. The withdrawal screen must offer a network accepted by the destination, and a self-custody wallet may need another native asset for future gas.

Multi-network assets need one passport per network

FaucetPay documents USDT deposits over several chains. Treat USDT on TRON, Ethereum, Polygon and BNB Smart Chain as separate route rows because their addresses, costs, receiver support and future gas plans differ.

Native coins usually have a simpler network identity

A native asset normally identifies its own chain more directly than a token issued on several networks. This reduces contract and gas ambiguity, but it does not remove FaucetPay minimums, platform charges or receiver rules.

Internal transfers are another platform function

FaucetPay describes instant transfers between platform users for supported balances. That feature does not make the balance self-custodial and does not guarantee that every external withdrawal network is available.

Coin Swap must be checked at execution

A visible balance is not proof that a swap pair has enough liquidity. The conversion is re-quoted, and the current platform fee and premium rate affect the result. Record the actual output before using a swap in the route.

A dollar estimate is not a capability field

The displayed portfolio value can move with market prices while the native balance remains unchanged. It cannot confirm payout activation, withdrawal readiness or swap liquidity. Keep the passport in native units and platform states.

Worked deposit-only difference

A user sees Cardano in the deposit catalogue and finds a source advertising ADA rewards. The operator payout snapshot does not include that symbol. The accurate conclusion is that an ADA deposit route is documented while the advertised faucet payout remains unverified.

Worked full-pass route

A faucet offers DOGE through FaucetPay, the user receives a matching DOGE history entry, and the current withdrawal route is accepted by a personal Dogecoin wallet. Deposit and swap functions are irrelevant. The passport passes because every function actually needed is confirmed.

Do not research functions the route does not use

A user who wants only internal LTC faucet payments and one later LTC withdrawal does not need to test LTC deposits, swaps or peer transfers. A smaller capability set is easier to verify and maintain.

Refresh the passport after material changes

Review the row after a coin is added or removed, a network changes, a faucet disables the asset, a fee changes or the destination updates its deposit policy. Store the verification date beside every capability claim.

Authoritative sources checked on July 30, 2026

The live Wallet remains the final operational source. The documents below support the distinction between the broader deposit catalogue and the shorter payout interface.

• Supported coin overview: https://beta.faucetpay.io/help/wallet/supported-coins
• Deposit assets and networks: https://beta.faucetpay.io/help/wallet/deposit-supported-coins-networks
• Faucet payout currencies and API functions: https://beta.faucetpay.io/api-docs
• Wallet functions and transaction history: https://beta.faucetpay.io/help/getting-started/navigating-your-dashboard
• Coin Swap fee guidance: https://faq.faucetpay.io/knowledge-base/what-are-the-fees-on-exchange-coin-swap/
• Withdrawal conditions: https://faq.faucetpay.io/knowledge-base/what-are-the-withdrawal-fees-on-faucetpay/

FAQ