Two sides, one check in the middle
A worker does a task and sends proof. It is checked, then accepted or rejected with a reason. Disputed rejections come to us. Pick the side you are on.
The advertiser path
Write the task and its proof rules
State what a worker must do and what proof you will accept. Tight rules mean fewer disputes and a faster review queue.
Set the rate and the number of slots
Your campaign cost is the rate multiplied by the number of slots, and that is the whole figure. Nothing is added at checkout. Unused slots stay in your balance.
Fund the campaign
Funds sit against the campaign and are released per approved completion. Nothing is released for work that failed review, and nothing can be released beyond what you funded.
Check the work
Open each submission, approve it, or reject it with a reason written out. Workers can appeal a rejection to FiniTasks, and our decision is final.
Close the campaign and export the ledger
A CSV of every completion, its proof, its reviewer, and its timestamp. That is the audit trail if anyone questions the spend.
The stamp means it was settled
Every approved submission carries one, dated and tied to its own reference, recording who approved it and when. Where it is missing, no money has moved.
What gets rejected, and why we say so
Account name mismatch
The screenshot shows an account that is not the one you signed up with. Resubmit from your own account.
Action undone
The follow or comment was removed after the screenshot. Each task says how long the action has to stay live, and it is on the task before you start it.
Right category, wrong campaign. Check the task reference on your submission against the one you opened.
Rejections are written by the advertiser who made the call, not chosen from a dropdown of codes. If you think one is wrong, appeal it. FiniTasks staff open the proof and decide, and that decision is final.