Mining Pool Payout Not Received? A Step-by-Step Troubleshooting Checklist
2026-10-19 14:35

If your mining pool payout has not arrived, first identify where the payment has stopped: earnings credited to your pool account, withdrawal processing, blockchain confirmation, or the receiving platform's deposit credit. Each stage has its own rules and timing. This checklist uses Bitcoin as the primary example while noting where the same logic applies to other coins or networks.

Start with the situation that matches your account:

  1. Earnings are missing from the pool account: check worker activity and the selected reward settlement method in Step 1.
  2. Earnings are credited, but no withdrawal appears: check the withdrawal method, auto-withdrawal settings, eligible amount, and schedule in Step 2.
  3. A withdrawal record exists: verify its status and destination in Step 3, then follow the transaction-status checks in Step 4 for an on-chain withdrawal.
  4. The transaction meets the receiving platform's deposit requirements, but no deposit appears: contact the receiving platform with the transaction details. Step 5 explains what to provide.

Step 1: Check Whether Mining Earnings Were Credited

Check the settled-earnings history for the expected account and coin. If those earnings are already credited, continue to Step 2. If they are missing, start with the worker page: is the worker shown as active, and is it submitting shares under the expected account and worker name? A worker with no reported hashrate for an extended period is typically flagged by the pool as offline, and one that stays silent for a longer stretch is reclassified as inactive; on ViaBTC these labels apply after roughly 20 minutes to one day, and after more than one day, respectively. A miner that only recently connected may also need 10–15 minutes before its status and earnings become visible.

It is also normal for the hashrate shown on a mining machine's local interface to differ from the figure shown on the pool dashboard, because the two are calculated over different windows. ViaBTC's real-time pool hashrate reflects a rolling average over the prior 10 minutes, while its daily hashrate statistic is a 24-hour average; neither is a direct, instantaneous reading of the ASIC itself. A temporary gap between the two numbers does not by itself indicate missing earnings. Persistently low pool-side hashrate, however, combined with a high rejection rate, connection errors in the miner's logs, or repeated authorization failures, can genuinely reduce the work credited by the pool. ViaBTC support describes a rejection rate within roughly 3% as a normal reference range for its platform; a rate well above that may point to network latency, overheating, or firmware issues worth investigating directly on the mining hardware.

If the worker is not submitting work to the expected account, check the Stratum URL and worker name against the current mining pool connection information. Correct connection or authorization errors before treating the issue as a missing withdrawal.

Settlement timing also depends on the selected payout method. Under PPS+ and PPLNS calculation rules, ViaBTC's default PPS+ method calculates the block-reward portion under PPS rules and settles it to the pool account on an hourly basis, while the transaction-fee portion follows PPLNS rules: it is distributed only after the pool finds a block, that block reaches six confirmations, and the miner's share of work over the preceding five difficulty rounds has been calculated. Under the standalone PPLNS method, both components follow this same block-dependent, lookback-based process. In either case, an hourly or periodic settlement event is an internal pool-account credit — it is not an external, on-chain transfer, and it should not be mistaken for a withdrawal.

Step 2: Check the Withdrawal Method, Threshold, and Schedule

Once earnings are confirmed as settled, identify how you expect to receive them. ViaBTC distinguishes Auto Withdrawal, Normal Transfer, and Inter-user Transfer in its BTC mining guide. Normal Transfer can be initiated at any time and carries a fee; it does not follow the daily auto-withdrawal schedule. For an internal transfer, check the account transfer records rather than expecting an on-chain transaction ID.

For auto-withdrawal to an external address, check:

  • Auto-withdrawal is enabled for the correct account and coin.
  • A valid destination address is configured. ViaBTC states that an on-chain payout address becomes invalid after 90 consecutive days without a payment; deleting the payout address also turns off auto-withdrawal for that coin.
  • The eligible payout amount meets the threshold actually configured in your account. ViaBTC documents a minimum of 0.001 BTC for external BTC auto-withdrawals, but your selected threshold may be higher.
  • The relevant daily processing window has been reached.

A miner who sees 0.0008 BTC credited but configured for external BTC auto-withdrawal has not yet reached the documented minimum. Check your actual setting using how to set the minimum payment for auto-withdrawal. For auto-withdrawals to your own ViaBTC main or sub-account, the external minimum does not apply, provided the transfer amount is greater than zero.

ViaBTC processes auto-withdrawals once daily between 10:00 and 18:00 (GMT+8). This is a processing window, not a guarantee of when funds will appear at an external destination, since on-chain confirmation and the receiving platform's deposit rules still apply afterward. Review the current rules under Auto Withdrawal setup, thresholds, and processing times.

The selected payout mode determines which amount is compared with your configured threshold:

  • Payout by Account Balance: uses the eligible account balance at processing time.
  • Payout by Daily Earnings: reserves mining earnings settled on the payout day. The calculation is account balance minus today's settled mining earnings; that calculated amount must meet the threshold.

This explains why a displayed balance above the threshold may still produce no auto-withdrawal under Daily Earnings mode. It also explains why the amount paid can be lower than the balance displayed that day. If revenue sharing is enabled, outgoing revenue-sharing deductions also affect the amount available for payout. Details are explained in how to choose a payout mode.

If the relevant conditions are met but no withdrawal appears after the processing window, ask pool support to check the account's payout status. Do not assume network congestion before establishing that an on-chain transaction has been broadcast.

Step 3: Verify the Withdrawal Record, Address, and Network

If a withdrawal record exists, examine it before searching the blockchain. Confirm the withdrawal status, coin, amount, destination address, and timestamp in the pool's withdrawal or asset history. Verify that the destination address recorded for this withdrawal is correct and belongs to the intended wallet or exchange account. Do not rely on the platform to determine whether a valid address belongs to your intended recipient; address-format validation and recipient ownership are different checks.

For coins or tokens that exist on more than one network, confirm that the coin and underlying network selected for withdrawal match what the receiving wallet or exchange actually expects. Sending to a mismatched network is a frequent cause of apparently missing funds, and such transfers are not always recoverable, so this check is worth performing before, not after, initiating a cross-platform withdrawal. If the destination is an exchange account, also confirm that the exchange supports the coin and network in question and that the withdrawal amount exceeds any minimum deposit amount the exchange enforces; an amount below that minimum may not be credited even though the transaction itself is valid.

Step 4: Check the Transaction Status and Confirmations

For an on-chain withdrawal, follow the branch that matches the record:

  • No transaction ID: check whether the withdrawal is still awaiting processing or requires action in your account. If its status is unclear or the expected processing window has passed, contact pool support. If the withdrawal is marked as sent, ask support for its transaction ID.
  • A transaction ID exists, but the explorer cannot find it: confirm that you copied the correct ID and selected an explorer for the correct network. If it remains unavailable, ask pool support to verify the broadcast status and current transaction ID. A missing explorer result alone does not establish congestion or lost funds.
  • The transaction is visible with zero confirmations: it has not yet been included in a block on the chain shown by the explorer. Check whether it is currently visible in that explorer's mempool and review its fee rate alongside current network conditions.
  • The transaction is confirmed: verify the receiving address and amount, then compare its confirmation count with the receiving platform's requirement.

A Bitcoin transaction gains one confirmation when it is included in a block, and additional confirmations accumulate as further blocks are mined on top of it. These stages are described in the Bitcoin Developer Guide's section on payment processing. Zero confirmations alone do not prove that a transaction has been successfully broadcast or remains in a mempool; the Bitcoin transaction reference also distinguishes unconfirmed transactions that are not in the mempool.

For a visible, unconfirmed BTC transaction, a public block explorer such as mempool.space can show its fee rate, commonly expressed in sat/vB. Comparing that rate with current network conditions can help explain a confirmation delay, since confirmation priority is generally tied to the fee paid relative to transaction size. If an on-chain pool withdrawal remains unconfirmed, pool support can help check its transaction status.

It is worth separating this stage clearly from the pool's own confirmation requirement: ViaBTC's six-confirmation condition applies to distributing PPLNS rewards after the pool itself finds a block, which is a different event from the confirmation count of a later withdrawal transaction sent to a miner's address.

If the transaction reaches the correct address and meets the receiving exchange's confirmation, network, and minimum-deposit requirements, but the funds are still not credited, contact that exchange with the transaction ID. For a self-custody wallet, check that the wallet software is fully synchronized. A confirmed transaction paying the expected amount to the correct address is strong evidence that the pool has completed the on-chain transfer.

Step 5: Contact the Right Support Team

Contact pool support for missing settled earnings, withdrawals that have not been processed, or questions about a pool withdrawal's broadcast status. Contact the receiving exchange or wallet support when the transfer reaches the correct address and meets its deposit requirements but is not reflected in the account.

Provide the details relevant to that stage:

  • Account or sub-account identifier and coin involved
  • The approximate time the issue began, including the time zone
  • For missing earnings: worker names, worker-status and settled-earnings screenshots, and relevant connection or authorization errors
  • For a withdrawal issue: the withdrawal method, amount, destination address, timestamp, status, and record or transaction ID
  • For an auto-withdrawal issue: the configured threshold and payout mode
  • For an exchange deposit issue: the network, confirmation count, and the receiving platform's deposit record or status

Do not share account passwords, wallet seed phrases, private keys, or two-factor authentication codes with anyone, including support staff; legitimate support processes do not require them.

FAQ

Why have I not received my mining payout yet?

The cause is usually one of several distinct stages, not a single "missing payout": earnings may not yet be settled to the pool account, auto-withdrawal may be disabled or its eligible payout amount may be below the configured threshold, an auto-withdrawal may not have reached its processing window, the on-chain transaction may still be unconfirmed, or a confirmed transaction may not yet be credited by the receiving wallet or exchange. Checking these in order generally identifies where the delay is occurring.

How long does a mining pool withdrawal take to arrive?

This depends on the pool's processing schedule, current network confirmation times, and the receiving platform's own deposit rules. For example, ViaBTC processes auto-withdrawals once daily between 10:00 and 18:00 (GMT+8). External payouts then depend on on-chain confirmation and any exchange-side requirements. Normal Transfer can be initiated at any time and does not follow that daily schedule; internal transfers do not require blockchain confirmations.

Will I receive a payout if my balance is below the withdrawal threshold?

For auto-withdrawal to an external address, the eligible payout amount must meet your configured threshold. Otherwise, it remains in the pool account and continues to accumulate. Under ViaBTC's Daily Earnings mode, today's settled mining earnings are excluded from the amount checked against that threshold. The external auto-withdrawal threshold does not apply to auto-withdrawals to your own ViaBTC main or sub-account, provided the amount is greater than zero.

What if the transaction ID shows zero confirmations?

Zero confirmations means the transaction has not been included in a block on the chain being checked; it does not by itself prove successful broadcast or current mempool presence. If the transaction is visible in a BTC explorer's mempool, check its fee rate and network conditions. If the explorer cannot find the transaction, verify the network and ID, then ask pool support to check its broadcast status.

Why did my exchange not credit a confirmed deposit?

Check whether the transaction pays the correct address and amount, uses a supported network, and meets the exchange's confirmation and minimum-deposit requirements. If those conditions are met but no credit appears, contact the receiving exchange with the transaction ID and deposit details.

References