There's a conversation that happens in every freelancer WhatsApp group sooner or later. Someone shares their story. They took a job. They delivered. The client approved it, said "good work," maybe even posted it publicly. And then they vanished. No payment. No response. Nothing.

The replies come fast: "Sorry bro," "This is why I collect upfront," "Same thing happened to me." A few people suggest legal threats nobody ever actually follows through on. The conversation moves on. The freelancer doesn't get paid.

Escrow is the thing that changes this story entirely. Not by making clients trustworthy. People are people. But by removing the need to trust anyone at all.

So what actually is escrow?

Escrow is a financial arrangement where a neutral third party holds money until specific conditions are met. That's it. The concept is old. Banks use it for property purchases. Governments use it for contracts. Car dealerships use it. The idea is simple: neither side has to trust the other completely, because nobody controls the money except the middleman, until the agreed conditions are satisfied.

In freelancing, it works like this. A client hires you for a project. Instead of paying you directly (and hoping you deliver) or you starting work directly (and hoping they pay), both of you agree to use escrow. The client deposits the money. It's locked. You can see it's there. You do the work. You deliver. The client confirms delivery. The money releases to you.

Neither side is exposed. The client can't ghost you after you deliver because they already paid. You can't disappear with the money without delivering because you don't have it yet.

The core mechanic: escrow doesn't require trust. It replaces the need for it. The money is already there. The only question is whether the work was delivered to the agreed standard.

Why bank transfers and Paystack links keep failing freelancers

The most common payment setup in Nigerian freelancing goes like this: client says they'll pay. You ask for 50% upfront. Client pays. You deliver. You ask for the remaining 50%. Client ghosts, negotiates it down, drags it out, or invents a problem with the work to avoid paying.

The 50% upfront model is better than nothing, but it still leaves you chasing half your money on every project. And if the client is determined not to pay, your only options are emotional (guilting them), social (public callouts, which carry their own risks), or legal (which almost nobody pursues over small amounts).

What direct payment can't solve: once the money leaves a client's account into yours, disputes get messy. Once you've done the work without payment, you have no leverage at all. The timing problem is the whole problem.

Escrow solves the timing problem. The money moves before the work starts, but it doesn't land in your account until the work is done. Both events happen in the right order, every time.

How the escrow flow works on Kreddlo

Kreddlo's escrow is built directly into every custom project and service order. There's no setup required. No separate account. No third-party integration. Here's the sequence from the moment a client agrees to hire you:

1

Client funds the project

The client pays the agreed amount into Kreddlo's escrow. You get a notification that funds are secured. Work can begin.

2

You do the work

No chasing. No "just checking in on payment." The money is already there. You focus entirely on delivering.

3

You submit delivery

When you're done, you mark the project delivered on Kreddlo. The client receives a notification to review and confirm.

4

Funds release to you

Once the client confirms, the payment releases to your Kreddlo balance immediately. Withdraw on your schedule.

What happens if the client doesn't confirm? That's where the dispute process comes in, and it's worth understanding before you need it.

What happens if there's a dispute?

Disputes happen. Clients have legitimate concerns sometimes. And occasionally a client will try to manufacture a problem to delay or avoid payment. Kreddlo's escrow handles both.

If a client raises a dispute after you submit delivery, Kreddlo holds the funds while both sides present their case. You provide the work you delivered. The client explains their concern. A resolution is reached based on what was actually agreed in the project scope.

This is why the scope matters. Vague projects ("design something nice for my brand") create room for endless revision requests. Specific projects ("design a logo in three concepts, two revision rounds included") have a clear definition of done. Escrow makes this distinction real in a way that a bank transfer never can.

For a detailed walkthrough of the custom project flow including contracts and milestone structures, see our post on escrow-backed custom freelance projects on Kreddlo.

Does escrow protect buyers too?

Yes, and this is the part people underestimate. Escrow isn't a freelancer-only protection. It's symmetric.

When a buyer funds a project, they know two things: their money is secured (not gone, not spent), and it will only release when the work meets the agreed standard. If a freelancer takes payment and disappears, the dispute process covers the buyer. The money hasn't gone anywhere.

This matters for the reputation of the whole ecosystem. Buyers who feel safe taking risks on newer freelancers are the buyers who build long-term relationships. Escrow creates that safety for both sides at once.

If you're a buyer reading this, there's more on this from your angle in our post about why you should never pay a freelancer without buyer protection.

What escrow cannot do

It's worth being honest about the limits.

Escrow does not make bad scope documents good. If you agreed to something vague and the client interprets it differently, escrow holds the money during that disagreement, it doesn't resolve it automatically in your favour.

Escrow does not protect you from clients who refuse to pay at all before work begins. If a client won't fund the escrow upfront, that's a red flag in itself. Any serious client who intends to pay has no reason to refuse.

And escrow does not cover work done outside the platform. If a client asks you to "just use bank transfer for this one because it's faster," you lose all protection the moment you agree. This is one of the most common ways freelancers get burned even when they know better.

Simple rule: if the money isn't in escrow before you start, you are extending credit to someone who hasn't earned it yet. You are the bank, and you have no collateral.

Is this only for large projects?

No. Escrow makes the most psychological difference on medium-sized projects, the ones worth a few days of work but not enough to justify a contract lawyer. The projects where your gut says "I think they'll pay" and you start anyway and find out you were wrong.

For very small amounts, the friction of escrow might feel unnecessary. For very large projects, you'd want a proper contract regardless. But in the middle ground where most freelance work actually happens? Escrow is exactly the right tool.

The question worth asking before your next project

Before you start your next piece of client work, ask yourself one question: if this client decided not to pay after delivery, what would I actually do about it?

If the honest answer is "not much," then you're taking on a financial risk that no amount of good faith should require. Escrow doesn't fix clients. It removes the need for trust entirely. And that's the point.

Read more about what happens when things go wrong and what to watch for before taking a project, in our guide on how to get paid for freelance work without getting scammed.