Cash in and cash out: getting money in is easy, getting it out is the part to plan

Why a payment method gets blocked at all

Start with the mechanism, because almost every piece of bad advice on this topic comes from misunderstanding it.

When you sell crypto peer-to-peer, a stranger sends fiat to your bank account or e-wallet. You have no idea where that money was ten minutes earlier. If it turns out to have come from fraud proceeds (a scam victim's transfer, a compromised account, a laundering chain) then at some point a report is filed, and an investigator or an automated system walks the money forward through every account it touched.

Your account is on that path. So it gets restricted, along with everyone else's on the path. The restriction is a property of the funds, not a judgement about you. That is why "but I did nothing wrong" is true and completely beside the point.

The second thing to understand: this is not only a bank phenomenon. Payment processors, e-wallets and card networks all run the same kind of monitoring, and any of them can restrict an account while a case is open. Changing which rail you use changes who is watching; it does not remove the watcher.

The three kinds of block, and why they are not the same problem

They get talked about as one thing. They are not, and the right response differs.

The practically useful distinction: the first is a customer-service problem, the second is a legal-process problem, and the third is a platform-support problem. People lose weeks by taking a legal-process problem to a call centre, over and over.

Read the notice you were given. Whatever text arrives (an SMS, a letter, an in-app message, a screen when a transfer fails) is the most reliable information you will get about which kind you are dealing with. Guessing from symptoms is how people pick the wrong door.

A fourth thing, which is not a block at all

Worth separating out, because it produces the same symptom and a completely different answer: a transfer that fails because of an ordinary limit. Daily and monthly caps on the account, a lower cap on a newly added payee, a cooling-off window after you changed a security setting, a card limit you have never hit before. All of these present as "the transfer did not go through", and none of them is a restriction on you.

The tell is usually that the failure is specific and repeatable (the same amount fails, a smaller one succeeds) and that no notice arrived from anyone. Before you conclude that something serious is happening, check the limits page on both ends. A surprising share of the panic in this area turns out to be a 24-hour cooling window on a newly whitelisted destination, working exactly as designed.

Who is actually watching

One more thing about the mechanism, because it explains why changing rails does not help. Banks, payment processors, e-wallets and card networks all run transaction monitoring, and all of them are required to report certain patterns to a national financial intelligence unit. The reporting obligation is on the institution, not on you, and it is triggered by shapes in the data rather than by anyone forming an opinion about you personally. Moving from a bank to an e-wallet changes which institution is doing the monitoring. It does not remove the monitoring, and the e-wallet's freeze process is often less transparent and slower to reach a human than the bank's.

Routes in, and what each one costs

Ways to turn fiat into crypto, and the real trade-off in each.

Card purchase

The fastest route and the most expensive. The cost is rarely presented as a fee; it is in the exchange rate you are quoted. Some card issuers also treat crypto purchases as cash advances, which adds interest from day one and a separate fee that is not on the exchange's screen at all. Check with your issuer before assuming the quoted price is the price.

Reasonable for a first small amount, when getting started matters more than the spread. Not reasonable as a habit.

Bank transfer to the exchange

Usually the cheapest route where it is available, and the one with the cleanest paper trail: the money moves between two named accounts, which is exactly the record you want to have. The downsides are that availability varies enormously by country, and that the first transfer often takes a day or two while the rail beds in.

Where this route exists for your currency, it is generally the right default.

Peer-to-peer

Often the only route in many markets, and the one that carries the block risk discussed above — though on the way in the risk profile is different: you are sending money and receiving crypto, so the tainted-funds problem mostly does not apply to you. It applies to the person you are paying.

What does apply on the way in is counterparty risk: paying and not receiving. The platform's escrow is what protects you here, which is why the single most important rule is that the payment and the release must both happen inside the platform's flow. Any counterparty who wants to move the conversation and the payment outside it has removed your only protection, and that is the entire scam.

Which numbers on a P2P listing are worth reading is covered in choosing a P2P counterparty.

A worked comparison of what each route really costs

Fee comparisons in this niche are almost always wrong in the same way: they compare the number labelled "fee" and ignore the two costs that are usually larger. Here is the full shape of what you pay, in the order of how much it typically matters.

Run it once with a small amount and write down the real numbers for your own bank, your own card and your own currency. Everything after that is arithmetic on numbers you trust, rather than arithmetic on numbers from an article about somebody else's country. Ours included: we do not know what your issuer charges, and any site that gives you a precise figure for it is guessing.

The exit, and three layers that actually help

Here is the honest framing: none of this reduces the probability that a counterparty sends you tainted money. You cannot see their upstream. What these layers do is reduce how much damage that causes when it happens, and make your position explainable afterwards. That is a smaller claim than most articles make, and it is the true one.

Layer one: do not concentrate the exposure

If all of your fiat life runs through one account, then one investigation freezes all of it, including the money for rent. Many people keep the account they receive P2P proceeds into separate from the account their salary and direct debits run through, and move money between them as ordinary transfers.

Be clear about what this does and does not do. It does not make you harder to trace, and it is not meant to. It means that when one account is restricted, your electricity bill still gets paid. That is the whole benefit, and it is a real one.

Layer two: keep a trail you can explain

If your account is reviewed, the question you will face is some version of: what was this money for? A person who can answer it with records is in a completely different position from one who cannot.

• Keep the platform's order records. Order number, counterparty, amount, timestamp. Export them periodically rather than assuming they will be there forever.
• Keep the corresponding bank records lined up with them.
• Do not accept payment from a name other than the counterparty's verified name. Third-party payment is a red flag in both directions and destroys the coherence of your own records.
• Describe transfers truthfully. Do not go looking for a form of words that keeps a bank reference field from being flagged; that makes not being noticed the objective, and not being noticed is the wrong objective. Write what the transfer actually was, or leave the field as the platform's own flow fills it, and be ready to say the same thing out loud, with the order record beside it.
• Read your own bank's terms. Some banks restrict or prohibit crypto-related transfers on personal accounts, and some say so explicitly in the account agreement. If you do not know where yours stands, ask it. A written answer from your bank is worth more than a forum consensus, and quietly testing the limit is not a substitute for reading the contract you signed.

This layer changes your position after something happens. It does not reduce the chance of it happening. Both halves of that sentence matter.

Layer three: size and timing driven by need, not by appearance

There is a piece of advice that circulates in every forum on this subject, and we want to be explicit that we are not giving it: break a large withdrawal into several smaller ones spread over different days, because it "smooths things out." It is worth saying in public why not.

Deliberately splitting transactions to sit below reporting or monitoring thresholds is called structuring, and it is one of the specific patterns anti-money-laundering systems are built to detect. In many jurisdictions it is an offence in its own right, independent of whether the underlying money was clean. Advice that reads as "here is how to shape your flows so the monitoring does not notice" is bad advice on the merits, and worse advice ethically.

The replacement is simpler: let the amount and timing of your withdrawals be decided by what you actually need the money for. If you need to pay for something, take out what it costs, when you need it. Do not design a rhythm to look a particular way to anyone. A pattern driven by real needs is coherent under questioning; a pattern designed to look unremarkable is exactly what does not survive it.

What a record you can actually explain looks like

"Keep records" is advice everybody gives and almost nobody specifies. Here is the specific version, because the difference between a useful record set and a useless one is not effort; it is whether the pieces line up with each other.

The three things that have to match

For any single peer-to-peer sale, there are three separate records of the same event, held by three different parties:

1. The platform's order record. Order number, asset, quantity, price, counterparty identifier, timestamps for creation and completion.
2. Your bank or wallet record. Incoming amount, sender name, timestamp, reference.
3. The in-platform chat. Whatever was said, inside the platform's own messaging.

A record set is coherent when all three describe the same event without contradiction: the amount in the bank matches the order, the sender name matches the counterparty's verified name, and the timestamps sit in a sensible order. It is incoherent when any of those does not hold — and the most common cause of incoherence is not fraud, it is casualness. Money arriving from a different name. A payment made before the order was created. A conversation held on a messaging app that leaves no trace in the platform.

Export on a schedule, not on demand

Platform histories are not archives. Interfaces change, retention periods exist, and access to an account can be exactly the thing you have lost at the moment you most need the records from it. Export your order history periodically (monthly is plenty for most people) and keep the files somewhere that does not depend on being logged in to anything.

The same goes for bank statements. A PDF statement saved each month costs nothing and is available when online banking is not.

A worked example of a coherent set

To make it concrete, what a single well-recorded transaction looks like when you present it:

• Order 12345678, created 14:02, completed 14:11, selling a stated quantity of a stablecoin at a stated price, counterparty verified name A. B.
• Incoming bank transfer at 14:07, amount matching the order total to the cent, sender name A. B.
• Chat log inside the platform showing the counterparty confirming payment at 14:06 and you releasing at 14:11 after checking the bank app.

Nothing in that set is clever. What makes it work is that a person reading it can reconstruct the event without asking you a single question — and that is the actual goal. A record that requires your narration to make sense is not a record, it is a story.

Third-party payment: the rule people break most

Of everything on this page, this is the one that is violated most often and the one where violating it does the most damage. So it gets its own section.

The rule: the name on the incoming payment must match the counterparty's verified name on the platform. If it does not, do not release. Not "release and note it in the chat." Do not release.

Why the excuse is always plausible

Nobody says "I am paying you with someone else's money". They say the account is their spouse's, or their company's, or that their own card is temporarily blocked, or that they are travelling. Some of those explanations are even true. That does not help you, for two reasons.

First, if the money turns out to be tainted, you have received funds from a person who has no order record with you at all. Your carefully coherent record set now has a hole in exactly the place someone will look.

Second, third-party payment is a standard technique for moving money through unrelated accounts, which means it is a pattern the monitoring is specifically built around. You do not get to be the exception because your particular counterparty had a plausible story.

What to do instead

Cancel or appeal through the platform's own process, and say why. This is precisely the situation escrow exists for: the asset has not left escrow, and the platform's dispute channel is designed to handle a payment that does not match. The cost of cancelling is a few minutes and a slightly worse price on the next order. The cost of releasing is potentially your account.

And on the other side of the same rule: do not pay from an account that is not in your own name either, however convenient it is. The symmetry is not a coincidence. Both directions create the same hole in the same record.

If it happens: the first day

Order matters here, because the two most common instincts are both actively harmful.

1. Find out which kind it is. Read the notification. Call the institution's official number (the one on the back of your card or on their website, not one from a search result) and ask what has been restricted and on whose instruction. This single question separates the three cases above.
2. Gather your records before you need them. Order histories, transfer records, the counterparty details, timestamps. Do this now, while you still have access to the accounts and apps involved.
3. Answer the questions you are actually asked, factually. Where the money came from, what the transactions were. Do not volunteer a theory, and do not embellish. If a large sum or a formal process is involved, get a qualified local lawyer before you give a statement.
4. Stop receiving into that account. Not to hide anything, but because further incoming transfers during an open review complicate it for everyone including you.

The two harmful instincts, stated plainly. Do not immediately try to move everything out of the account — if a hold is in place it will not work, and the attempt itself looks exactly like what it looks like. Do not pay an "unfreezing agent." There is no private party with a channel into a legal process. That market exists because frightened people with blocked accounts will pay anyone; the ones who take your money have, at best, done nothing.

How a restriction unfolds over weeks

Most writing on this subject stops at the first day, which leaves people with no idea what a normal shape looks like afterwards. Here is the rough arc. Durations vary enormously by country, by institution and by which of the three kinds you are dealing with, so read the sequence rather than the timings.

1. Discovery. Usually a failed transfer or a card decline rather than a notification. The first useful action is to find out what has actually been restricted (a channel, an amount, or the account) and on whose instruction.
2. Classification. Within a day or so you should know whether this is the institution's own risk control, an investigative hold, or a platform-side restriction. Each has a different door, and knocking on the wrong one is where weeks disappear.
3. Documentation. Whoever is asking will ask for records. This is the phase where the work you did earlier either pays off or does not exist. Assemble everything before you are asked, not after.
4. Waiting. The longest phase, and the one where people do damage. Repeatedly calling a call centre about a legal-process matter does not accelerate it; opening new accounts to route around it makes the picture worse; and moving remaining balances at speed looks precisely like what it looks like.
5. Resolution, or partial resolution. Frequently the outcome is not binary. A specific amount stays held while the rest of the account returns to normal, or online transfers come back before card payments do. Partial restoration is a normal outcome, not a sign that something has gone wrong.
6. Afterwards. If the institution decided it does not want this activity on your account, it may say so, and it is entitled to. That is a business decision rather than a finding against you, and the practical response is a different institution and a cleaner separation, not an argument.

The honest part: we cannot tell you how long any of this takes, and neither can anybody else writing in general terms. The variables are the jurisdiction, the institution, the amount, the number of accounts on the same chain, and whether an authority is involved. Anyone quoting you a number for that is guessing, and the number is doing a marketing job rather than an informative one.

Talking to the institution

This is the part with the most folklore attached, and the folklore is almost all about what to say. The useful preparation is almost all about what to have.

Prepare four things before the call

• Your record set for the transactions in question, in date order.
• The exact wording of any notice you received, and the date it arrived.
• A one-sentence, true description of what the activity is. Not a script, just a plain answer to "what is this money?" that matches your records.
• The official contact number, taken from the back of your card or the institution's own site. Never from a search result and never from a message, because a person with a blocked account and a search engine is exactly the target profile for the callback scam.

Four things to avoid

• Do not improvise a reason that does not match the records. They already have the records. A mismatch is worse than an incomplete answer.
• Do not promise behaviour you will not follow. Saying it will not happen again and then continuing is how you spend the credibility you will need on the next call.
• Do not empty the account to be safe. Whatever you mean by it, that is not how it reads.
• Do not volunteer analysis. Answer what is asked, specifically and factually. Theories about which counterparty was probably the problem are not evidence and are not helpful.

If the matter is a formal process, or the sum is substantial, get a qualified local lawyer before you give a statement. That is not a hedge to cover ourselves; it is the point at which general information stops being useful and the specifics of your jurisdiction take over entirely.

What your account looks like from the outside

An automated monitoring system does not see your intentions. It sees a shape. Three features of that shape are worth knowing about, not so you can game them, but so you understand why an ordinary person sometimes gets a second look:

• Many small incoming transfers from unrelated individuals, followed promptly by an outgoing transfer of the total. This is the classic pass-through pattern. It is also, unavoidably, what regular P2P selling looks like.
• A sharp change in behaviour. An account that was quiet for years and suddenly turns over large amounts stands out more than one with a consistent history.
• Amounts clustered just below round thresholds. As above: this reads as deliberate, and it is the pattern the systems were built for.

None of this is a checklist to defeat. The useful conclusion is the opposite one: if legitimate P2P activity inherently resembles the pattern, then the thing that distinguishes you is not the shape of your flows — it is whether you can produce a coherent account of each one. Invest there.

Reporting and tax: the part nobody writes

On-ramp guides end at "the money arrived". The obligations that follow have the longest tail of anything on this page, and they are the ones that surface a year later when it is too late to reconstruct the records.

We are not going to give you rules. Treatment differs by country, changes, and depends on facts about you that we do not have. What we can give you is the list of questions whose answers you need, because the questions are stable even where the answers are not:

• Which category of income or gain does your jurisdiction put disposals of crypto assets into?
• Does the obligation arise when you convert back to fiat, or also when you swap one asset for another?
• Is there an allowance, a holding-period rule, or a de minimis threshold?
• Do you have to declare proactively, or only respond when asked?
• What records are you required to keep, and for how long?
• Does receiving payments from many individuals change anything about how the activity is characterised?

That last question is the one people never think to ask and the one most likely to matter. There can be a difference between disposing of your own assets occasionally and doing something that looks like operating a business, and the line is drawn differently in different places.

The one action that is right regardless of the answers: keep complete records from the first transaction. Acquisition dates, costs, disposal dates, amounts. Reconstructing this two years later from partial exports is miserable and often impossible, and the cost of doing it as you go is a few minutes a month.

Things we will not recommend

To be explicit, because plenty of sites in this niche do recommend them:

• No unfreezing intermediaries. Covered above. No exceptions.
• No techniques for making activity "look normal." Anything whose purpose is to shape appearances rather than reflect reality is teaching evasion, and we are not doing that.
• No using someone else's account or documents. This converts a bad afternoon into a serious legal problem, and it is the most common single cause of an unrecoverable account.
• No "guaranteed safe" counterparties. Nobody can see the upstream of the money, so nobody can guarantee this. Anyone claiming to is either mistaken or fishing.

There is a checklist version of the preventive habits on the payment-block self-check. It deliberately does not produce a score: assigning numbers to these items would imply a precision we do not have and cannot get.

Questions people write in with