A frozen merchant account or a held deposit is usually a risk decision, not a fault. Who decides, what to request, what to prepare, and how to lower the odds.
Key takeaways
- This is a risk decision. Reopening runs through documents, not through persuasion.
- Responding fast with the right documents shortens the time more than anything else.
- Most blocks follow a changed pattern: a turnover jump, an unusual transaction, many refunds, or chargebacks.
- You can lower the risk in advance - far cheaper than handling it afterwards.
A blocked merchant account or a deposit that never arrived is almost always a decision by whoever holds the money, not a technical fault. So the first step is not opening a support ticket but establishing who exactly made the decision - the acquirer, the payment provider, or their risk function - because each has a different process.
What actually happens, in order
| What happened | Who decides | What is needed from you |
|---|---|---|
| A single transaction held for review | Risk at the acquirer or provider | Evidence for that transaction: order, delivery, customer details |
| One deposit delayed | Whoever holds the money | Usually an explanation of unusual transactions that day |
| The account frozen for new transactions | The acquirer or provider | A full document pack, and sometimes a call |
| A deposit or rolling reserve required | Risk management | Written agreement, and a release date |
The last row surprises businesses: sometimes the account reopens on terms - holding a percentage of turnover for a period, or a deposit. That is legitimate and common in higher-risk sectors, and worth knowing as one of the possible outcomes.
What to do in the first hour
- Establish who holds the money - the acquirer or the provider. That is the address.
- Ask in writing for the reason and the list of documents required.
- Stop taking payments on that rail until you understand what happened. Transactions continuing into a blocked account complicate matters.
- Switch on an alternative collection channel - a link from another provider, a bank transfer - so the business does not stop.
- Tell customers waiting on a payment or a refund, before they find out themselves.
- Assemble the document pack and send it in one go, not in dribs and drabs.
Item six is what shortens the time. A partial answer starts another round of requests; a complete one reaches the right desk faster.
Which documents are usually requested
This is not a secret list - it is a pack you can prepare in advance:
- Business documents: registration certificate or company number, bank details in the business name.
- Samples of unusual transactions: the order, the invoice, correspondence with the customer.
- Proof of delivery: a waybill, a delivery confirmation, or confirmation that the service was provided.
- Your sale terms: cancellation and returns policy, and what the site says.
- An explanation of the change in pattern: a campaign that raised turnover, a new product, a season.
The last item is the most important and is usually not requested explicitly. A risk function seeing an unexplained jump assumes the worst; a short explanation with numbers removes the assumption.
Why is this happening now?
- A sudden turnover jump. A successful campaign looks exactly like anomalous activity.
- A transaction at an unusual amount relative to the business's history.
- Many refunds in a short period, which reads as a product or fulfilment problem.
- Chargebacks above a certain rate.
- A change in the nature of the activity - a new product, a new audience, selling abroad - without prior notice.
The fifth is the only one entirely preventable with one conversation: telling the provider before a material change avoids a review afterwards.
How to lower the risk in advance
- Tell the provider before a large campaign, a special sale or a launch that doubles turnover.
- Keep proof of delivery for every significant transaction - not only an invoice.
- Handle refunds properly, from inside the system and linked to the original transaction.
- Publish a cancellation and returns policy on the site and honour it.
- Answer chargeback enquiries fast, because silence counts against you.
- Keep a second collection channel ready - not active, but existing.
That last one is cheap insurance. A business with a single provider that gets blocked stops collecting; a business with a second channel is working again within an hour, even if less comfortably.
What to prepare in advance, in one folder
A ready pack turns a week into an hour of work. Put these in one folder before anything happens:
- Business documents and proof the bank account belongs to the business.
- Your cancellation and returns policy as it appears on the site, with a dated screenshot.
- One complete example: order, invoice, delivery confirmation, and correspondence with the customer.
- A turnover report for the last six months, by month.
- The contact details of your account manager at the provider, not only the support desk.
The last item is worth more than it seems: with a specific name, your enquiry bypasses the general queue. You ask for the account manager's name on the day the account opens, not on the day it is blocked - like the rest of what is worth recording in advance in the difference between a payment provider and a credit card company.
What not to do
- Do not open a new account with another provider to bypass a block without disclosing it. That makes things worse.
- Do not ask customers to transfer to a personal account. It damages both records and trust.
- Do not argue before you understand exactly what the reason is and who decided.
- Do not promise customers a date outside your control, particularly on refunds.
What to tell customers meanwhile
This is the part forgotten under pressure, and it decides how much damage remains afterwards. Three types of customer, three different messages:
- Paid and waiting for delivery: nothing to update if delivery is unaffected. Do not tell them about a problem that does not touch them.
- Waiting for a refund: do update, without committing to a date outside your control. "I will update you on Sunday" beats a promise you will break.
- Trying to pay and failing: offer an alternative channel immediately. A customer who wants to pay and cannot is the most expensive damage in this whole story.
The rule: update whoever is affected, on what is relevant to them, without detailing your dealings with the provider. That is not concealment - it is simply not the information the customer needs.
Sources
Frequently asked questions
How long does it take to release a blocked account?
It depends on the reason, the documents and who decides, so no range can be promised. What is in your control and does matter: the speed and completeness of your response. A full pack in the first reply shortens the process more than any amount of chasing by phone.
Can I withdraw money that has already cleared?
It depends on the decision and the reason. Sometimes funds are held temporarily and released after review, and sometimes they are held as security against possible refunds and chargebacks. Ask in writing what the status of the funds is and what condition releases them.
Can this happen to a completely legitimate business?
Yes, and it does. A block is not an accusation - it is usually a response to a changed pattern. That is exactly why it is worth giving notice before a campaign or a launch and keeping proof of delivery: those two turn a long review into a short one.
Do I need two payment providers?
Not necessarily, but it is worth having an alternative collection channel ready - even a payment link from another provider or the option of a bank transfer. The cost of holding it is close to zero, measured against the day the business cannot collect at all.
Keep reading
Related service
Integrations
Make the systems you already pay for talk to each other.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.
