Which Coins Can a Faucet Operator Send Through FaucetPay Right Now?

The FaucetPay API marked fourteen currencies active for operator payouts on July 30, 2026. The complete registry appears below. This is the relevant public catalogue for a faucet payout question, but it does not prove that an individual source funds every entry, that the supplied recipient will validate, or that the later external withdrawal is economical.

The fourteen active payout currencies

The public API marked the following symbols active for faucet sends on the review date.

• Bitcoin — BTC
• Ethereum — ETH
• Tether — USDT
• Litecoin — LTC
• Dogecoin — DOGE
• Bitcoin Cash — BCH
• Dash — DASH
• DigiByte — DGB
• Tron — TRX
• Zcash — ZEC
• Solana — SOL
• BNB — BNB
• Feyorra — FEY
• USD Coin — USDC

What Active means

An Active entry means FaucetPay currently exposes the currency to its payout infrastructure. The currencies endpoint can also supply operator-facing amount limits. It is platform capability, not proof that a named faucet has a positive balance or an enabled button.

Use the Four-Gate Payout Check

A route is ready only when every gate passes.

• Platform gate: the currency appears active in the current FaucetPay payout tools
• Operator gate: the faucet enables and funds that currency
• Recipient gate: the supplied email, username, supported address or payout hash is recognized
• Exit gate: the later withdrawal network and destination are usable

The operator chooses a currency per send

The payout request includes an uppercase currency symbol and an amount in the coin’s smallest unit. A source can pay BTC while leaving DOGE or USDT unavailable. One successful coin does not validate the rest of its menu.

The recipient can be represented in several ways

The current API accepts an email, username, wallet address or payout_user_hash. The faucet’s form determines which identifier the user must provide. A value that worked on one source should still be checked on the next source.

A payout ID is internal evidence

A successful send returns a FaucetPay payout identifier to the operator. That record helps reconcile the source and recipient. It is not automatically a public blockchain hash because the faucet payment can remain inside FaucetPay’s ledger.

Native-chain payout group

Most entries in the registry are native assets whose ticker points directly to one primary chain. They usually require fewer network-identity decisions than a token that can leave through several chains, although live minimums and destination policies still control the result.

Smart-contract and token group

The registry also includes platform assets and tokens. Their payout symbol can identify the internal FaucetPay balance without fixing the external withdrawal network. The receiver and native gas plan therefore remain separate checks.

The payout list is not the deposit list

The deposit catalogue contains additional assets, including Cardano, XRP and Stellar. Their presence on a receiving page does not add them to the operator payout registry. The two documents describe different directions of value movement.

The payout list is not a recommendation list

An active BTC route can be poor for a microscopic balance, while LTC or DOGE can be simpler for another user. Choose by source availability, first threshold, live exit cost and final use. Popularity and unit count are not payout-quality metrics.

How a faucet should prove coin-level support

The current account or withdrawal page should name the coin, recipient type, threshold and request status. After the test, the source should retain a payout record and the user should see the matching native amount in FaucetPay history.

Why an old screenshot is insufficient

Operators can run out of one balance, remove a currency or change processors without closing the site. Use the current form and one dated payment. A platform-wide Active label cannot repair a faucet that no longer funds the coin.

Worked XRP exclusion

A beginner finds an XRP deposit address and an external site advertising XRP rewards. The operator payout registry does not contain XRP on the review date. The source must therefore prove another valid route instead of relying on the deposit page as evidence.

Worked USDT partial pass

USDT passes the platform gate and the faucet pays an internal credit. The destination accepts only a network not currently offered or economical in the withdrawal screen. The payout worked, but the complete route fails the exit gate.

Keep the list dated

Recheck the API and Wallet after a coin addition, suspension, network change or operator problem. A payout article without a verification date will eventually mix current and historical support.

Sources reviewed on July 30, 2026

The payout snapshot comes from the current public API. Deposit documentation is included only to show why the two catalogues should not be merged.

• Payout currencies and send endpoint: https://beta.faucetpay.io/api-docs
• Supported coin overview: https://beta.faucetpay.io/help/wallet/supported-coins
• Broader deposit asset list: https://beta.faucetpay.io/help/wallet/deposit-supported-coins-networks
• Current claiming flow: https://beta.faucetpay.io/help/getting-started/claiming-from-faucets
• Withdrawal conditions: https://faq.faucetpay.io/knowledge-base/what-are-the-withdrawal-fees-on-faucetpay/

FAQ