What is a merchant application? It is a request to an acquiring bank to carry the risk of your business taking card payments, and it is underwritten much the way credit is. Not a signup, not a product purchase. A file about you, read by someone deciding whether to stand behind you.
That framing explains almost everything people find strange about the process.
What is a merchant application? Why a bank underwrites it
When a customer pays you by card, the money moves before the customer has what they bought. If you take the payment and then cannot deliver, somebody has to refund that customer, and if the business is gone, the acquiring bank absorbs it.
So the bank is extending you something closer to credit than to a subscription. That is why it wants ownership details, bank statements, processing history and a look at your live site. Every one of those answers the same underlying question: if this business stops delivering next month, how large is the hole.
Once you see it that way, the requests stop feeling intrusive and start being answerable. How the whole process works lays out the steps around it.
What is inside the document
Three parts, usually bound together as one file.
The business section: legal identity, ownership, banking, what you sell and how, your volume and ticket figures, and your processing history.
The attachments: identification, formation documents, bank statements, processing statements if you have them, and anything your category requires you to hold.
The agreement: the terms you are accepting if approved, including the fee schedule, settlement timing, any reserve, dispute handling and termination provisions. This part is not a formality and it is the part most people skim.
An underwriter does not read those top to bottom. They read for risk in a fairly consistent order, which this walk through of underwriting covers in detail.
What you are actually signing
Worth knowing before the pen moves, because a merchant agreement typically carries three commitments people miss.
A personal guarantee, often, which puts a named individual behind the business obligations. Ask what it covers, how long it lasts, and what would release it after a period of clean processing.
An authorization to debit your bank account. That is how fees, refunds and chargebacks are collected, and it is normal, but it means the processor can pull as well as push.
Terms incorporated by reference. The agreement will point at an operating guide or program terms held elsewhere, and those are as binding as the page in front of you. Ask for them. If a document governs your account, you should be able to read it before you agree to it.
How it differs from signing up with an aggregator
An aggregator signup asks a handful of questions and puts you on an account belonging to the provider. The underwriting has not been skipped, only deferred, and it tends to arrive at the least convenient moment, once there is money in flight to review.
A full file goes the other way. More questions now, in exchange for an account in your own name that is much harder to switch off without warning. Neither is universally right, and the comparison between the two models is the honest version of that choice.
What happens after you send it
It gets screened for category appetite, read for risk, and put in front of the acquiring bank, which makes the decision. Nobody in front of that bank can promise you its answer, and you should be careful of anyone who does.
What comes back is often conditional: a volume ceiling, a maximum ticket, a reserve, or a review date. Those are terms to discuss rather than a verdict to accept silently. Ask what each condition is there to cover and what would relax it, then ask for the whole schedule in writing before you sign anything.
If it is declined, ask what drove it. Category appetite means take the same file elsewhere. Something in the file means fix that first, because an identical submission to a second bank usually earns an identical answer. Our application page covers what a complete file contains, and the FAQ covers the questions worth asking before you commit.
Frequently asked questions
Is a merchant application the same as a merchant agreement? They travel together and they are not the same. The application is what you submit for review. The agreement is what governs the account if the review succeeds. Read the second one as carefully as you completed the first, because it is the part that lasts.
Does submitting one obligate me to anything? Submitting is a request, not a commitment to trade. The commitment starts when you sign the agreement that comes back. That is exactly why the terms in the offer deserve a careful read rather than a glance at the rate line.
Can I be underwritten without processing history? Yes. A thin history means less for the reviewer to judge, which usually shows up as a reserve or a lower initial ceiling rather than a refusal. Clear documentation and an accurate description of the business matter more at that stage than anything else.
Why does the same file get different answers from different banks? Because appetite differs. A bank already heavy in your category can decline a strong file simply because it wants no more of that category, and it will rarely say so. A decline is information about fit as much as about you.
How long do the terms last once signed? As long as you operate within what was underwritten. Material changes, a new product line, a large volume jump, a different sales model, should be disclosed rather than discovered. Undisclosed change is one of the more common reasons a healthy account gets reviewed.