Merchant account opening is a sequence rather than a single event, and knowing the order tells you exactly where you are standing. A file moves through category screening, underwriting, a sponsor bank decision, boarding, and then a first settlement. Most of the waiting collects at two of those points, and only one of them is yours to control.
Stage one: does anyone board your category at all?
Before a single document gets read, somebody checks whether the acquirer takes businesses like yours. This is a portfolio decision made above the underwriting desk, and it is the fastest answer in the whole process.
It is also the answer you should force first, because it costs you nothing. Ask one question before you assemble anything: do you board this category, yes or no. A no here has nothing to do with the quality of your business. It usually means the acquirer already holds as much of that category as it wants. Our industries pages cover the categories that get screened this way most often.
Owners lose weeks by skipping this step, sending a complete file to a processor who was never going to board them, and reading the eventual decline as a verdict on their business.
Stage two: someone actually reads the file
Now the documents matter. An underwriter reads for risk signals in a fairly fixed order, starting with your model and your processing history rather than with your revenue. What they are testing is whether the story holds together across every document you sent.
The most common finding at this stage is not risk. It is contradiction: a website selling something the application never mentioned, or projected volume that the bank statements do not support. What an underwriter reads, and in what order goes through this in detail.
Stage three: the bank makes the decision
We place accounts and we market processing under our own brand. The approval itself belongs to the acquiring bank behind the account, and nobody in front of that bank can promise you its answer. Anyone who does is selling you something they cannot deliver.
What comes back is often not a plain yes or no. It is a yes with structure attached: a monthly volume ceiling, a maximum ticket size, a reserve, or a review at an agreed point. None of those are punishments. They are how a bank says yes to a file it has questions about. Ask what each condition would take to relax, and read how rolling reserves actually work before you agree to one.
Stage four: boarding, descriptor, gateway
Approval is not the same as being able to charge a card. Boarding is the technical work that follows: your account number is issued, gateway credentials are generated, and your billing descriptor gets set.
Pay attention to that descriptor. It is the text a cardholder sees on their statement, and when it looks nothing like the name they bought from, they call their bank instead of you. That single field quietly drives a share of disputes that never needed to exist. If your setup involves a gateway built for harder categories, this is also when its fraud tools get configured, and it is worth doing properly rather than later.
Run a small live transaction and refund it before you send any real traffic.
Stage five: money actually moves
Your first batch settles and lands in the business bank account you named on the application. Check three things on that first deposit: that the amount matches what you expect after fees, that the timing matches what your agreement says, and that the descriptor appeared the way you set it.
If any of the three surprises you, raise it in week one rather than month three. Settlement questions are far easier to sort out while the relationship is new and small.
What slows a merchant account opening down
Almost never the acquirer. Four things, in order of how often they cause the delay.
An incomplete file, which is by far the most common. Send everything the first time, including the things you were not asked for but know will come up. A website that contradicts the application, which stalls the review until somebody explains it. A prior termination that surfaces in screening rather than in your own words. And unanswered follow-up questions, because a file with an open question sits still.
If a previous processor dropped you, say so at the start and explain what changed. The first week after a processor drops you covers how to write that explanation. The full assembly checklist sits on our merchant account application page, and working through it before you submit removes most of the delay you would otherwise be sitting through.
Frequently asked questions
Can I keep my old processor running while the new one boards? Yes, and you generally should. Overlapping the two lets you test the new account with small live transactions before you move real volume, and it means a hiccup in boarding does not stop you taking money.
Do I need a business bank account first? Yes. Settlement goes to an account in the business name, and a mismatch between the name on the bank account and the name on the application is a routine cause of a stalled file. Sort the banking before you apply.
What if I get declined at stage three? Ask what specifically drove it. A decline on category appetite means find a different acquirer with the same file. A decline on something in the file means fix that thing first, because sending the identical file elsewhere will usually produce the identical answer.
Does a reserve mean they distrust me? Not personally. A reserve is how an acquirer covers the gap between when you take money and when a dispute could arrive. Ask for the release schedule in writing, and ask what would reduce or end it after a clean period of processing.
Should I disclose a MATCH listing before they find it? Yes, always. Screening picks it up regardless, and volunteering it with context reads completely differently than having it discovered. Our MATCH list page explains what the listing does and does not mean.