Escrow does one job and does it well: the moment a P2P order opens, the seller’s crypto is locked by the marketplace. The seller cannot move it, cannot sell the same coins to somebody else, and cannot walk away with them. The buyer cannot get at them either, not until payment is confirmed. That lock is the entire protection, and it covers the crypto leg only. The money sitting in your EasyPaisa, bKash or M-PESA wallet never enters escrow at all.

Nearly everything people misunderstand about P2P falls out of that one sentence. Buyers assume escrow protects them, and are broadly right. Sellers assume the same thing, and are broadly wrong. This page is about the mechanism itself, and about what happens once a trade stops going smoothly — it is not a walkthrough of how to place an order.

Anyone who has watched an order timer run down with no reply from the other side knows the feeling that pushes people into the wrong decision: release early, just to make the discomfort stop. Knowing what escrow is actually doing during those minutes is the cheapest way to stop yourself.

What escrow is holding, and what it is not

Escrow on a P2P marketplace is a conditional lock, held by the venue, over coins that were already sitting inside that venue. The second half of that sentence usually gets skipped, and it explains everything else. A seller’s balance lives in the marketplace’s own system to begin with, so freezing part of it is instant and cheap — nothing is transferred anywhere, no blockchain confirmation is waited on, a flag is set and the balance becomes untouchable until the order resolves.

The money leg has no equivalent. When a buyer sends funds from a mobile wallet, that transfer runs on rails belonging to a telecom or a bank. The marketplace holds no account there, has no view into it, and cannot freeze or claw back anything on it. It only learns that a payment supposedly happened because a human tapped a button on an order screen. That button is a notification. It is not evidence, and it certainly is not money.

Escrow is a lock on crypto, held by the venue that already has custody of the crypto. It is not a guarantee that money will arrive, and it cannot reach into a wallet app to undo anything that happens there.

Framed that way, escrow stops being a vague safety net and turns into something narrower and far more useful: it removes counterparty risk from exactly one half of a two-sided trade. Which half you are standing on decides how much protection you actually received.

The order of operations

The sequence is fixed, and learning it removes most of the anxiety, because at any given second you can say whose turn it is and what is currently exposed.

1

The order opens and the crypto locks

Automatic, the instant the offer is accepted. The seller gets no step at which they could decline to fund escrow, and there is no version of this flow where a buyer is paying against coins that were never locked in the first place.

2

The buyer pays on the local rail

EasyPaisa, JazzCash, bKash, M-PESA, UPI, eZ Cash or a bank transfer — whatever the offer specified. The buyer then marks the order paid, which sends the seller a notification and does nothing else at all.

3

The seller checks their own app

Not the screenshot pasted into the chat. Their own wallet or bank app, showing the right amount, actually available rather than pending, sent from a name that matches the person on the order.

4

The seller releases

Escrow unlocks and the crypto moves. This step cannot be undone by either party or by the marketplace, which is precisely why step three is the one that deserves your patience.

What if the buyer never pays at all — no scam involved, just a wallet outage or somebody who got distracted? The order carries a payment timer. If it runs out with nothing marked, the order closes and the locked crypto unlocks straight back into the seller’s balance. Neither side loses anything; the trade simply did not happen. That is the ordinary, boring failure mode, and it is worth recognising so you do not treat it as an emergency.

Notice where the irreversible step sits. It is at the end, it belongs to the seller, and it is taken on the strength of the seller’s own judgement about whether money has really arrived. Every hard case in this article lives in that gap.

Buyer risk and seller risk are not the same risk

The two sides of a P2P order are not mirror images, and most bad outcomes trace back to somebody assuming they were. Escrow sits squarely on the buyer’s side of the table.

Your roleWhat escrow covers for youWhat you are still carrying
BuyerThe seller cannot take your payment and keep the coins as well — they were locked before you sent a rupeeDelay. A seller who is asleep, distracted or slow to check their app, leaving your money gone and your coins not yet released
SellerNothing. Your coins are the thing being held, and you release them yourselfA payment that looks received and later is not — reversed, recalled, or sent from an account that should not have sent it

For a buyer, the worst realistic case in a normal trade is an uncomfortable wait followed by an appeal, because the crypto is already locked and cannot be spirited away. Annoying, occasionally stressful, rarely fatal. For a seller, the worst case is that the trade completes perfectly, the money shows in the wallet app, the coins go out, and days later the money leaves again. Escrow has nothing to say about that, because by then escrow has already done its job and closed.

That second scenario deserves its own treatment, and it has one: our page on whether a mobile money payment can be reversed after you release goes through the routes a payment can be undone and what a seller can realistically do about it.

The practical consequence is that the two roles need different habits. A buyer’s discipline is mostly about paying from the right account and keeping the paper trail. A seller’s discipline is entirely about the release decision — what they check before it, and how long they are willing to wait.

What an appeal actually is

An appeal — some marketplaces call it a dispute — is a request for a person at the venue to look at one stuck order and decide it. Three things about it are worth internalising before you ever need one.

It is a human reading a file, not an algorithm. Somebody opens the order record, reads the chat, looks at whatever both sides have uploaded, and makes a call. They were not there. They cannot see inside your wallet app. Everything they know about your payment comes from what you show them.

It is decided on evidence, not on volume. Whoever complains first, complains loudest, or writes the longest message does not win on that basis. A buyer with a transaction reference and a matching account name is in a stronger position than a seller flatly insisting nothing arrived, and the reverse holds just as firmly.

It runs on a clock. Response windows exist, and missing one can decide the case by default. This is the failure mode that stings most, because it has nothing to do with the merits — somebody just did not check their phone.

Do not cancel a problem order to “tidy it up” before appealing. On many marketplaces cancelling closes the order and takes the appeal route with it. Raise the appeal from the live order.

The plausible outcomes are narrow: the crypto is released to the buyer, the crypto is returned to the seller, or one side is asked for more evidence and the clock restarts. There is no outcome in which the venue reimburses anyone out of its own pocket, and no outcome in which it retrieves money that already left a mobile wallet. It can only decide where the locked coins go. Anyone telling you otherwise is describing something P2P escrow does not do.

What counts as evidence

Evidence in a P2P dispute means anything that ties one specific payment to one specific order. That link is the whole game — reviewers see plenty of proof that a payment happened somewhere and no proof at all that it was this payment, for this trade, from this person.

What to keepWhy a reviewer can use it
The transaction reference or confirmation code from the mobile money appIt is the one string that exists on both the provider’s records and your screenshot. Nothing else identifies a payment as precisely
The exact timestampPlaces the payment inside or outside the order window, which decides a surprising share of cases
The full name on the sending account, as it appears in the appAnswers the reviewer’s first question about any payment: did this come from the person on the order
The amount, uncroppedPart-payments and rounded-down transfers are common, and a cropped figure looks like something being hidden
The order chat, left intactShows what each side said they would do, in sequence, with times attached

A distinction that matters more than it sounds: take the screenshots while the trade is live, not afterwards. A capture made at the time carries the details you were not thinking about — the balance line, the notification banner, the reference sitting in the corner. One reconstructed later carries only what you remembered to go back and look for, and it often arrives cropped to exactly the part that supports your story, which is the least persuasive form of evidence there is.

A statement export or the transaction history screen inside your own app is usually stronger than a single confirmation popup, because it shows the payment sitting in context alongside the transfers around it.

Things that carry very little weight: a screenshot the other party sent you, a promise made in a messaging app outside the order, and a payment reference typed out by hand instead of shown on screen. None of those can be checked, and a reviewer who cannot check something has to set it aside.

The single most common way people lose

If there is one line to take away from this page, it is this: pay from an account in your own name, matching the name on your verified profile. The most frequent reason a person who genuinely paid still loses an appeal is that the money left somebody else’s account.

The situation is usually innocent. A woman trades on a profile in her own name but the household wallet is registered to her husband. A student uses a parent’s account because their own wallet is capped at a level too low for the transfer. A small trader pays out of the shop’s account because that is where the float sits. In every one of those cases the money really did move, and the sender really did intend to pay for that order.

None of that is visible to a reviewer. What they see is a payment from a name that does not appear anywhere on the order — which is exactly what a payment from a stolen or borrowed account also looks like. Marketplaces generally refuse third-party payments outright for that reason, and the refusal does not bend for a sympathetic explanation, because the explanation is unverifiable.

Sellers: if the name on the incoming payment does not match the buyer on the order, do not release. Ask in the order chat, and if it cannot be resolved there, appeal rather than releasing and hoping.

The same rule runs in the other direction. A seller receiving into an account that is not theirs is just as exposed, and has fewer ways to explain it afterwards.

There is a legitimate version of this problem worth sorting out in advance: names that genuinely differ across documents. Spelling variants such as Muhammad and Mohammad, a maiden name on one record and a married name on another, initials expanded on a national ID but abbreviated in a wallet registration, transliterations from Sinhala, Tamil, Bangla or Urdu that landed differently on different forms. These are ordinary, they are fixable, and the time to fix them is before you trade, by updating the records with the provider and with your verified profile — not in the middle of a dispute when the mismatch has already cost you the argument.

Wallet-side name and tier problems have their own page: mobile money limits and KYC tiers covers why the wallet, the bank account and the trading profile all need to agree, and what happens on the rail when they do not.

Before you pay, before you release

Two short lists. They are short deliberately — a checklist you will actually run is worth more than a thorough one you skip.

As a buyer, before you send anything:

As a seller, before you release:

If you find yourself reasoning towards releasing early — they seem trustworthy, the screenshot looks real, they are being nice about it — that is the moment the list exists for. Escrow protected the buyer. Nothing is protecting you except this step.

What this page does not cover

Some deliberate omissions, so you know where to look instead.

Crypto assets are volatile and P2P trading carries a real risk of loss. Nothing on this page is financial or legal advice.

The mechanism, condensed: escrow locks the coins when the order opens and unlocks them when it closes, the money leg is never inside it, and a dispute is a person deciding which way those locked coins go based on what you can show them. Buyers need to worry about paying correctly. Sellers need to worry about releasing too early. Almost everything else is detail.

Questions people ask

Does escrow protect my money as well as the crypto?

No. Escrow holds the crypto leg only. The moment an order opens, the seller’s coins are locked by the marketplace and neither side can move them until the order resolves. The rupees, taka or shillings sitting in your mobile money wallet never enter escrow at all — that leg runs on the payment provider’s rails, which the marketplace cannot see and cannot touch.

What is the difference between cancelling an order and appealing it?

A cancellation ends the order and unlocks the crypto back to the seller, which is the normal outcome when a buyer simply never pays inside the payment window. An appeal asks a person at the marketplace to look at a disputed order and decide it on evidence. Cancelling first can close off the appeal route, so raise the appeal while the order is still open.

What evidence actually helps in an appeal?

Anything that ties one specific payment to one specific order: the transaction reference from your mobile money app, the timestamp, the exact account name the money left from, the amount, and the messages inside the order chat. Screenshots taken while the trade was live carry more detail than anything reassembled from memory afterwards.

Why do people lose appeals when they genuinely did pay?

Most often because of a name mismatch. The money moved, but it left an account in somebody else’s name — a spouse, a sibling, a shop account — so the reviewer has no way to connect that payment to the person on the order. From the outside it is indistinguishable from a third-party payment, which marketplaces generally refuse.

How long does a dispute take?

There is a clock on it, but the length varies by marketplace and by how tangled the case is, so we are not going to quote a number. The timer on your own order screen is the only figure that applies to you. What is under your control is answering inside that window and uploading your evidence in one go rather than in instalments.

Can I just settle it directly with the other trader?

You can talk to them in the order chat, and plenty of small mix-ups clear up there. What you should not do is move the conversation to a messaging app and settle privately, because then there is no record for a reviewer to read and no locked crypto to fall back on. Keep every part of it inside the order.

Is escrow enough on its own to make P2P safe?

It removes one risk very cleanly: a seller cannot take your payment and keep the crypto too. It does nothing at all about a payment that lands and then reverses days later, which is the risk carried by the seller. Treating escrow as complete protection is precisely how sellers get caught out.