How Long Does Merchant Account Underwriting Take, and What Slows It Down

The IBO package ships the same day the setup payment confirms. From a complete application, the acquirer's underwriting typically takes 3 to 10 business days, and only the acquirer controls that clock. Files pause on missing documents, an unreachable signer, a website that is not live and bank proof that does not match. Prepare the website, description and projections before delivery, file on day one, and answer every pend the same day.

Merchant account underwriting on a US high-risk file typically takes 3 to 10 business days, counted from the day the acquirer receives a complete application. That window belongs to the acquirer: its queue, its policy for the vertical and how fast pends are answered decide where in the range a file lands, and no provider outside the acquirer can promise a shorter window or the outcome. An IBOCore package ships the same day the setup payment confirms, with the entity, the director and the bank account already built, so the application can go in on delivery day. Below: where the days go, what pauses a file, and what to prepare so the acquirer's time is spent reviewing rather than waiting.

Two clocks: what IBOCore controls and what the acquirer controls

Merchants who ask how long underwriting takes are usually asking about two clocks at once. The first runs from first contact to a delivered package, and IBOCore controls most of it: packages are permanently in stock, and the bundle is released the same day the payment confirms. The second runs from a complete application to an issued MID, and the acquirer controls it.

Where the 3 to 10 business days go

Underwriting is a sequence, and the days are spent moving the file from one desk to the next. The order varies by acquirer and by whether an ISO agent sits between you and the risk team; the underwriting checks guide on this blog explains what each stage examines. The question here is where the time goes.

1. Intake. The ISO or the acquirer's sales desk checks that the application is complete and signed. An incomplete file does not start the clock; it is returned.
2. Document review and KYB. The entity documents and the bank proof are read against the application. On a package they show the director on the state filing and on the EIN letter, with one legal name and one state throughout; a file that reads the same everywhere moves on the first pass.
3. KYC, credit pull and screening. The signer is verified on the government ID and proof of address, the credit file is pulled, and the sanctions lists and MATCH are queried.
4. Website review. The underwriter opens the site with the application next to it. A site that is not live stops the file here.
5. Risk assessment. Projected volume, average ticket, billing model and vertical set the exposure; the acquirer decides on a processing cap and whether a reserve applies.
6. The verification call. The risk team calls the authorized signer by phone. On a package that is the director, the Independent Business Operator (IBO) named on the entity; you coordinate the timing with the director through your private Telegram group. The verification call guide covers the questions.
7. Decision and MID issuance. Approval, decline, or a counter-offer with conditions. Once accepted, the MID is issued and the gateway is configured, through your ISO when one submitted the file.

What pauses a file

A pend is the acquirer's request for something more before it decides. Every pend stops the clock until the answer lands and reopens the review of whatever the answer touches, so a file that pends twice can spend more time waiting than being read. Underwriters pend for two reasons: something is missing, or two things disagree.

• Missing documents. No bank proof, no EIN letter, an unsigned personal guarantee, a business description that was never written. The document checklist guide lists the full file.
• An unreachable signer. The analyst calls the number on the application and nobody answers. This one usually ends the file rather than delaying it; the verification call guide explains how.
• A website that is not live. A parked domain, a store in password mode, a checkout that fails or missing policy pages. The underwriter cannot review what does not load.
• Bank proof that does not match. A bank letter or voided check in a personal name, a legal name spelled differently from the EIN letter, or account numbers typed on the form that differ from the document.
• Projections out of scale. A monthly volume the website could not plausibly produce, a highest ticket that does not exist on the site, or rebills in the projection of a one-time offer.
• Unexplained history. Processing statements from another entity attached without a sentence on the relationship, or a past termination the underwriter finds on MATCH rather than in the application.

Why business days, queues and the ISO relay change the number

The range is counted in business days, and for a US merchant account the acquirer is a US institution: weekends and US federal holidays do not count, so a file submitted on a Friday before a long weekend can lose three calendar days before an analyst opens it. The acquirer's queue matters as much as the file: a risk team boarding many high-risk merchants in the same week works through them in order. If an ISO agent submitted the file, every pend travels twice, from the underwriter to the ISO and then to you, and the answer travels back the same way. None of this is visible from outside, which is why an honest answer to the timing question is a range, not a date.

What to prepare before delivery day so the clock starts on day one

The package side is ready when it arrives: the entity documents, the EIN letter, the director's ID and proof of address, the bank account at Bluebanc or Relay with full operational access, and the company email. What delays the start of underwriting is the part only you can produce. Prepare it before you order, not after delivery.

1. Put the website live first. Terms, privacy policy, a refund and cancellation policy, visible prices, a contact page carrying the company email and legal name, a working HTTPS checkout. For a subscription, the price, the frequency and the cancellation method appear before checkout.
2. Write the business description once and use it twice. What is sold, to whom, how it is fulfilled, how it is billed, where the traffic comes from and how refunds work. The same text goes to the acquirer and to the director, who has to explain it on the call.
3. Build projections from the site. Monthly volume, average ticket, highest ticket, the share of recurring billing and the expected refund rate, each traceable to a product page.
4. Choose the channel before delivery. Your own ISO agent or a direct application; IBOCore is processor-agnostic. Have the form ready so the bundle can be copied into it on delivery day.
5. The IBO package costs $999 setup, then $2,999 per month from 30 days after delivery, whatever the vertical or the billing model.
6. Decide on the add-ons with the order. The document template pack ($499 one-time) covers agreements, invoices and policy templates; bank pages ($2,499 one-time, twelve pages) serve acquirer due diligence in sensitive verticals; merchant account consulting ($899 per month) covers acquirer choice and application structure. None is required.
7. Answer pends the same day. Anything the director must sign or say goes through the private Telegram group; anything the business must write stays with you. A pend answered in hours costs hours; one answered next week costs the week.

How the timeline fits the 30-day billing window

The IBO package costs $999 setup, then $2,999 per month from 30 days after delivery, whatever the vertical or the billing model. The clock is anchored on delivery, not on the first settlement, so the acquirer's 3 to 10 business days sit inside that window when the application is filed early. Filed on delivery day, a file at the long end of the range is decided with about two weeks of grace left; filed after two weeks spent building the website, it can still be in underwriting when the first invoice arrives. The window also carries an operating condition: a package sitting idle with no merchant account opened after 30 days can be reclaimed and reassigned, and the setup fee is not refunded. If the acquirer declines, or terminates the MID later, there are no clawbacks and no penalties; the package stays yours and can be presented to another acquirer.

Questions merchants ask

Does a fresh entity take longer to underwrite than one with processing history?

Not necessarily. A fresh entity has no processing statements, so the underwriter reads the signer, the website, the projections and the description instead; that is a different review, not a longer one. What adds time is a fresh entity presented as something else: borrowed statements, an inflated history or projections nobody can trace to the site, each of which triggers a pend. Say the entity is new, project from the website and let the file speak.

Can I shorten underwriting by applying to several acquirers at once?

Parallel applications do not make any one acquirer faster, and each acquirer that pulls the guarantor's credit sees the inquiries the others left in the same week, which raises questions of its own. One IBOCore package is designed to open one MID at a time, for clean underwriting. Pick one acquirer or one ISO and file one coherent application. Once that MID is live, further MIDs can be stacked on the same entity with compatible acquirers; parallel MIDs on different processors take a second package.

What if the acquirer has not answered after 10 business days?

Ask, through the ISO if one submitted the file, and ask a specific question: is the file complete, is it pended, and on what. Silence past the range usually means a pend that never reached you, a call that went unanswered, or a queue. If it is a pend, close it the same day. If it is a decline, the reason matters more than the date, because a coherent file can go to another acquirer while the package's 30-day window is still open.

High-risk MID metrics acquirers watch

Once live, your chargeback ratio (CB ratio) is chargebacks divided by transactions; Visa VDMP and Mastercard ECP programs trigger when you breach network thresholds. Rolling reserves (often 10% for 180 days) protect the acquirer against future disputes. MATCH (Terminated Merchant File) is the industry blacklist after a forced termination. MCC (Merchant Category Code) must reflect your real vertical; miscoding is a scheme violation.

• Representment: fighting a chargeback with delivery proof and logs.
• RDR / Ethoca alerts: pre-chargeback refund tools that protect your CB ratio.
• Statement descriptor: keep it recognizable to cut "friendly fraud" disputes.
• Processing cap: volume limit until the acquirer trusts your history.

MID stacking without structure

Spreading volume across many MIDs without separate entities looks like ratio gaming or transaction laundering to risk teams. The durable pattern is one IBO package per MID, clean descriptors, honest MCC, and reserves treated as a cost of doing high-risk volume.

FAQ: quick answers

How fast can I get an IBO package on IBOCore?

Available inventory ships the same day after payment. You receive Articles, EIN letter, registered agent details, bank onboarding pack and signer contact through your merchant dashboard. Processor onboarding typically follows over the next one to two weeks.

Where can I look up payment-processing jargon?

Use the Resources glossary on IBOCore (/resources) for 580+ definitions: MID, chargeback ratio, MATCH, rolling reserve, MCC, RDR, KYB and high-risk vertical vocabulary.