Which Clock Started—and Which Provider Deadline Controls the Next Action?

There is no honest universal answer such as wait 24 hours or wait 30 days. Torox permits a missing-reward claim after at least 24 hours; BitLabs says ordinary reward processing can take up to two days and some explicitly pending offers require seven to thirty days; AdGate can display an offer-specific confirmation period such as seven days; RevU investigations may take twenty-one days or longer. Start the clock named by the provider and the status shown for this offer.

Use the Five-Clock Pending Timeline

Only one clock should control the next action.

• Clock 1 — completion not tracked
• Clock 2 — provider marks the reward pending
• Clock 3 — support ticket under investigation
• Clock 4 — provider approved but host balance is missing
• Clock 5 — host balance exists but crypto payout is pending

Start every timeline with four timestamps

Save the click time, completion time, first pending or missing status and ticket time. Do not measure a seven-day review from the day the user later noticed the problem.

Clock 1 — completion has not appeared

The offer may still be waiting for an advertiser event or tracking update. Torox currently allows a missing-reward application after at least twenty-four hours. BitLabs says reward processing can take up to two days before the report-a-problem route is used.

Clock 2 — the provider explicitly says pending

A pending state often means an advertiser event was recorded but requires review. Use the offer’s written confirmation period. Do not replace an explicit twenty-one-day or thirty-day window with a generic twenty-four-hour rule.

BitLabs current pending range

BitLabs states that some manually reviewed offers can take seven to thirty days and normally include a note in the description. Once the offer is marked pending, it says no further completion action is required.

AdGate current pending labels

AdGate explains that a pending reward can display a phrase such as Confirms after 7 days. A separate Pending phone verification state requires phone verification; its help says the SMS should arrive twenty-four hours after starting the offer.

Torox current missing-reward threshold

Torox says a user can apply for a missing reward when at least twenty-four hours have passed, the offer was completed inside its deadline and all eligibility conditions were followed. A pending status means Torox has contacted the advertiser for investigation.

Clock 3 — the support investigation has started

The waiting baseline resets when the ticket is accepted. RevU says its initial review and advertiser validation may take twenty-one days or longer. Keep the ticket number and provider account ID; repeated duplicate cases can fragment the investigation.

Do not miss the evidence deadline

RevU advises filing missing-reward reports within thirty days because it retains tracking information for a limited period of about forty-five days. A long pending period is not permission to ignore the last date for opening a case.

Clock 4 — approved provider reward, missing host credit

When the offerwall says credited or approved but the website balance has not changed, the provider decision is complete. Contact the host platform with the provider record and ticket. Starting another provider ticket usually targets the wrong ledger.

Clock 5 — host balance to crypto payout

The offerwall is no longer pending when the host balance is approved and withdrawable. A later FaucetPay or wallet payment has its own request, coin, threshold and processing clock. Do not ask the advertiser to diagnose a host withdrawal.

Save proof immediately, not at the deadline

Offer descriptions can disappear and apps can change after completion. Save the offer ID, terms, advertiser account ID, exact milestone, completion screen, receipt where applicable, pending status and timestamps as soon as the task finishes.

Do not repeat the task while any clock is active

A reinstall, second account, another purchase or alternate tracking link can create duplicate signals and destroy new-user eligibility. Repeat only after the original case is closed and the provider explicitly permits another attempt.

Use the one-ticket escalation sequence

After the correct waiting window, open one provider ticket through the offer history. Wait for the stated response period. Escalate to the host only with the original ticket reference and proof that the provider stage is complete or unresponsive.

Worked Torox clock

A game milestone was completed twelve hours ago but remains Clicked. Torox requires at least twenty-four hours before the missing-reward application. The user saves proof and waits another twelve hours without reinstalling.

Worked BitLabs clock

An offer states that it will pend for fourteen days and BitLabs marks it pending. The user saves the terms on day zero. A missing-credit ticket on day two would ignore the offer-specific review period.

Worked RevU support clock

The contact option becomes available, the user submits complete proof on day three and receives a ticket. The active clock is now RevU’s investigation, which can take twenty-one days or longer. The user preserves the case rather than opening daily duplicates.

When waiting becomes unreasonable

Move to the pending-too-long workflow when the published review period and support response window have expired, the provider cannot locate the offer, the required proof keeps changing or a payment is demanded to release the reward.

The waiting rule

Wait while the named clock remains inside its documented period and the case is traceable. Escalate once after the threshold. Stop new tasks when the provider has no deadline, the evidence route disappears or the cost of further attention exceeds the reward.

Waiting-time sources reviewed on July 30, 2026

Provider-specific documentation is the source of truth. The examples below demonstrate why a single universal waiting period would be inaccurate.

• Torox missing reward and 24-hour threshold: https://torox.io/faq-missing-your-reward/
• BitLabs uncredited reward timing: https://bitlabssupport.zendesk.com/hc/en-us/articles/12497003552925-I-have-completed-a-game-or-task-but-didn-t-receive-any-reward
• BitLabs seven-to-thirty-day pending review: https://bitlabssupport.zendesk.com/hc/en-us/articles/14182188604189-Why-is-my-offer-reward-pending
• AdGate pending and phone-verification states: https://adgate.zendesk.com/hc/en-us/articles/23974394230292-My-Reward-is-Pending-What-does-this-mean
• AdGate in-wall support route: https://adgate.zendesk.com/hc/en-us/articles/23993436652052-I-completed-an-offer-but-didn-t-receive-my-reward
• RevU ticket timing and evidence-retention deadline: https://help.revu.co/en/articles/9462535-how-do-i-request-support-for-missing-rewards
• RevU proof requirements: https://help.revu.co/en/articles/9462537-what-proof-do-i-need-to-submit

FAQ