Why Did Money Start Moving From You to the Reward Platform?

Do not send the deposit. A requirement introduced after an offerwall task—recharge, tax, verification transfer, negative-balance payment or wallet activation—does not prove the reward is real. It reverses the expected direction of value: the participant is now paying the system that claims to owe them. Preserve the original terms and stop before a small first transfer becomes a sequence of larger demands.

The direct decision

Do not make a test payment, even when the amount is small or described as refundable. FTC task-scam guidance explains that platforms can display fake earnings, pay a small amount to build trust and then demand crypto to unlock later tasks or withdrawals.

Freeze the account evidence

Before the platform changes or deletes the page, save the URL, account ID, offer ID, original terms, completion proof, reward balance, status, deposit message, requested amount, coin, network, recipient address and timestamps. Export text where possible instead of relying only on cropped screenshots.

Use the Deposit Demand Incident Ledger

Compare the promise with the new request.

• What action was required before the task began?
• Was any purchase or deposit disclosed in the saved terms?
• Which party now asks for money: advertiser, offerwall, host or unrelated account?
• What is the claimed purpose: activation, tax, liquidity, verification or negative balance?
• Where would the payment go and who controls that address?
• What new condition is promised after payment?
• Has the requested amount increased after an earlier payment?

A legitimate offerwall reward chain does not require user-funded callback processing

Normal offerwall systems record the user's click and advertiser event, validate completion, send a server-side reward callback and credit the host-site balance. The participant does not need to transfer crypto to make the callback work or prove that a receiving wallet exists.

Separate the advertiser, offerwall and host

The advertiser defines the task. The offerwall tracks and validates it. The host site displays the balance and normally controls the later payout. Record which domain and support channel produced the deposit demand. A Telegram or WhatsApp account using an offerwall logo may belong to none of them.

Refundable does not reduce the risk

The requester controls both the displayed reward and the refund promise. A first payment can be followed by a larger tax, account correction or minimum-liquidity demand. A paid offer disclosed before starting is different; a new fee introduced after completion is the incident. Do not use more money to recover an earlier transfer.

Wallet verification does not require a payment

Ownership of a public address can be checked through a narrow message signature when genuinely necessary. It does not require sending crypto, sharing a seed phrase or approving token spending. A reward site can also pay a small test amount toward the participant.

If you have not paid

Stop communication outside official channels, change any reused password and contact the host platform through its verified site. Provide the incident ledger and ask whether the offer and requester are genuine. Do not continue tasks while the reward is held behind the payment.

If you already sent crypto

Do not send another transfer. Save the TXID and receiving address, notify the sending exchange or wallet provider and report the incident through applicable fraud channels. A confirmed blockchain payment may not be reversible, but the evidence can support address tracing and account protection.

If you shared login or wallet authority

Change compromised account passwords from a clean device, secure the associated email and review two-factor authentication. Inspect wallet approvals and signatures on the correct network. If a seed phrase or private key was exposed, treat the wallet as compromised and move remaining assets through a newly secured route.

Worked incident

A game offer promises a $9 equivalent reward with no purchase. After completion, the host balance shows $9 pending and a chat account requests $3 in USDT to verify the withdrawal wallet. The payment condition was absent from the saved terms, the recipient is a newly supplied private address and the reward remains operator-controlled. The user stops, preserves the request and reports it.

The correct end state

Success means no more money leaves, account and wallet access are protected, the incident is documented and the offer is rejected or investigated by the responsible platform. Recovering the displayed reward is secondary to stopping real losses.

Fraud and reward-flow sources — July 30, 2026

Current consumer-protection guidance supports the task-scam analysis. Primary offerwall documentation supports a server-side validation and rewarding flow without participant-funded unlock transfers.

• FTC task-scam warning: https://consumer.ftc.gov/consumer-alerts/2025/08/how-spot-avoid-task-scams
• FTC explanation of fake task earnings and deposits: https://consumer.ftc.gov/consumer-alerts/2024/11/task-scams-create-illusion-making-money
• Digital Turbine server-side reward callbacks: https://docs.digitalturbine.com/dt-offer-wall/publishers/task-specific-guides/rewarding-your-users/server-side-rewarding
• Unity offerwall campaign events and milestones: https://docs.unity.com/en-us/grow/offerwall/user-acquisition/dashboard/introduction-to-cpe-campaigns

FAQ