What escrow actually is, and why freelance work needs it
Escrow is not a guarantee that the work will be good. It is a guarantee that nobody can disappear with the money while the question is still open.
By The Nepal Can Work team · Updated
Escrow is one of those words that appears on every marketplace's homepage and is almost never explained. It is worth understanding properly, because what it protects you from is quite specific — and what it does not protect you from is where people get caught out.
The plain definition
Escrow means a neutral third party holds the money while two people who do not trust each other complete a transaction. The buyer pays in. The seller can see the payment exists. Neither of them can take it. It is released when an agreed condition is met.
It is the same mechanism used when buying property — the money sits with a lawyer, not with the seller, until the title actually transfers. Freelance work has exactly the same problem in miniature: one side has to go first, and whoever goes first carries all the risk.
The problem it solves
Without escrow there are only two arrangements, and both are bad:
| Arrangement | Who carries the risk | How it fails |
|---|---|---|
| Client pays up front | The client | Freelancer takes the money and stops replying |
| Client pays on delivery | The freelancer | Work is delivered, then the client goes quiet |
| Split 50/50 | Both, halved | Both failure modes, at half scale |
Escrow removes the question of who goes first. The client's money leaves their account before work starts, so the freelancer knows it is real and committed. It does not reach the freelancer until the client approves, so the client keeps control. Neither side has to extend trust they have no basis for.
How it works here, step by step
- The client pays at checkout. The money goes to the platform, not to the freelancer. It is held.
- The freelancer sees the order is funded and starts work. This is the point at which it is safe to begin.
- The freelancer delivers inside the order thread, where the delivery is timestamped and visible to both sides.
- The client reviews. They approve, or they request a revision, or — if something is genuinely wrong — they raise a dispute.
- Approval releases the money. After a short hold, the payout is queued to the freelancer.
Why there is a hold after approval
There is a short window — 6 hours by default — between approval and the payout being queued. It exists because people sometimes approve a delivery and only then open the file properly. Once a payout has left the platform it cannot be pulled back, so the hold is the last moment where a mistake is still cheap to fix.
What happens when the two sides disagree
This is the part that matters, because escrow without a resolution process is just a delay. Three levels, in order:
- A revision. Most disagreements are a misunderstanding of the brief, and the agreed revision rounds exist precisely for this. It is the fastest path and it resolves the majority of cases.
- A settlement. Either side can propose splitting the escrow — release 60%, refund 40%, whatever reflects the reality. If the other side accepts, it executes immediately with no staff involvement. This is often the honest answer when work is partly right.
- A formal dispute. Staff read the brief, the delivery, and the message thread, and decide. The money stays in escrow throughout. Nobody can move it while the question is open.
The whole design rests on the money being immobile while the disagreement is live. That is the actual protection — not that you will win, but that the funds cannot vanish while it is being worked out.
What escrow does not do
Being honest about the limits is more useful than overselling it:
- It does not make the work good. Escrow protects the transaction, not the quality. Checking a portfolio is still your job.
- It does not protect a vague brief. A dispute is judged against what was agreed. If the agreement was 'design me something nice', there is nothing to judge against and no process can rescue that.
- It does not cover off-platform payment. This is the big one. If you pay a freelancer directly — bank transfer, eSewa, cash — there is no escrow, no dispute process, and no record. Every protection described here stops existing the moment money moves outside the platform.
- It does not make the service fee refundable. The escrowed work amount can be refunded to you. The platform's fee for handling the transaction is not refunded, including on a cancelled order.
Why this matters more in Nepal than elsewhere
Cross-border freelancing has an asymmetry: the client is often abroad, the freelancer is here, and if something goes wrong there is no shared legal system either of them can practically use. Nobody is flying to Kathmandu over a Rs. 30,000 logo, and nobody is filing in a foreign court over it either.
When legal recourse is theoretically available but practically useless, the structure of the payment is the only real protection there is. That is the argument for escrow, and it is why it is not an optional extra here.