The High-Risk Underwriting Checklist: The Document Pack That Gets a MID Approved

The application went in eleven days ago. Since then you have answered four rounds of questions from someone you have never spoken to, sent the same bank statements twice, and been asked to explain a refund policy already on your site. Nobody has said no. Nobody has said yes either. Meanwhile your existing processor is sitting on a reserve and you are trying to open a second account before you need it. Almost none of that delay is about risk appetite. It is about a document pack that arrived incomplete and got underwritten one email at a time. This post covers what high-risk underwriters actually need, why files get stuck, and how to assemble a pack that gets a decision in days instead of weeks.

What underwriting is actually deciding

An underwriter is not deciding whether your business is good. They are deciding who eats the loss if you stop shipping tomorrow.

That is the whole frame, and it explains every question you will be asked. When a card transaction is disputed and the merchant cannot fund the refund, the acquirer covers it. So the underwriter is pricing one thing: the size and likelihood of unfunded liability sitting on their books after you are gone.

Everything in the document pack maps to a piece of that estimate. Financials and bank statements say whether you can absorb a bad month. Processing history says how often your customers dispute. Fulfillment timelines say how much money you hold before you have delivered anything. Your website, claims, and marketing say how likely a regulator or a card brand is to make this a problem for reasons unrelated to your solvency.

Merchants lose weeks treating the application as a credibility contest and writing persuasive narrative. Underwriters do not read narrative. They tick boxes, and a missing box stops the file.

The core pack

Assemble all of this before you apply anywhere. The same set works across most domestic high-risk ISOs and acquirers, with minor variations.

Entity and ownership

• Certificate of incorporation or formation, current and matching the legal name on the application exactly
• EIN letter or equivalent tax registration
• Government photo ID for every beneficial owner at 25 percent or more, plus the control person
• Ownership breakdown that adds to 100 percent, including any holding entity in the chain
• Any relevant state or federal licenses for your vertical

Banking

• Voided check or a bank letter on letterhead for the settlement account, in the legal entity's name
• Three to six months of business bank statements, complete PDFs, not screenshots of a balance

Processing

• Three to six months of processing statements from your current or most recent provider, with monthly volume, average ticket, chargeback count, and refund count visible
• If you have never processed, a written volume projection with the assumptions behind it
• If you were terminated somewhere, the termination notice and a plain explanation of what happened

Operations

• Product list with pricing, and for regulated products, ingredient panels or specifications
• Fulfillment model: who ships, from where, how long from charge to delivery
• Supplier or manufacturer agreements where the product is not made in-house
• Refund and cancellation policy as it appears live on the site
• Customer service contact details that a cardholder can actually reach

Website

• The live URL, working, with a real checkout and no password wall
• Terms of service, privacy policy, refund policy, shipping policy, and contact page all reachable from the footer
• Age gates, geo-blocking, or disclaimers where your vertical requires them

That is the pack. A file with all of it arrives complete, and complete files get read in one sitting.

Why files stall

Almost every delay traces back to one of five things.

Mismatch. The legal name on the incorporation certificate, the bank account, the application, and the website footer must be the same string. A DBA is fine when it is disclosed as a DBA. Three different variants of a company name across four documents reads as sloppiness at best and as an undisclosed entity at worst, and it always triggers a question round.

Statements that hide the numbers. Underwriters need chargeback and refund counts, not just deposits. A summary page or a bank feed showing net deposits will be sent back. Send the full monthly processing statements.

Undisclosed history. If you have been terminated or listed, say so in the application. The acquirer will find a MATCH listing during onboarding regardless, and a listing you disclosed is a conversation while a listing they discover is a decline. The same goes for prior processors you left on bad terms.

A website that contradicts the application. This is the most common one and the easiest to fix. The application says one-time sales and the checkout has a pre-checked subscription box. The application says a 30-day refund policy and the site says all sales final. The application says supplements and the landing page makes a disease claim. Underwriters open the site, and any gap between what you wrote and what they see costs you a round.

Vague projections. A first-time merchant writing 500,000 dollars a month with no basis gets underwritten as if the number is fictional. Give a number you can support from ad spend, list size, or existing revenue, and expect a volume cap near it.

The three things that decide your terms

Once the file is complete, three variables set your reserve, your cap, and your rate.

Variable	What the underwriter looks at	What moves it in your favor
Dispute exposure	Chargeback ratio and count over the last 3-6 months, refund rate, dispute reasons	Ratio under the program thresholds, a documented prevention stack, descriptors customers recognize
Delivery risk	Days from charge to delivery, whether you presell, subscription versus one-time	Short fulfillment, in-stock inventory, no long preorder windows
Financial depth	Bank balances, processing history length, personal guarantee, prior terminations	Real reserves in the bank, a clean statement history, disclosed and explained past problems

Dispute exposure is the one you can move fastest. Getting your ratio under program thresholds before you apply is worth more than any other single change, and the mechanics of how that ratio is calculated are covered in the chargeback ratio guide. Fixing your billing descriptor is the cheapest lever in that stack, since unrecognized-charge disputes count against you exactly like fraud disputes do.

Delivery risk is structural. If you charge on order and ship in three weeks, you are holding customer money for three weeks, and the acquirer prices that with a reserve. That is arithmetic rather than hostility, and the rest of the reserve math is in the rolling reserves post.

Fixes to make before you send the file

Do these in the week before you apply, not after the first question round.

Match every name string across entity documents, bank account, application, and site footer. Put the refund policy, shipping timelines, and a working contact method in the footer of every page. Make sure the checkout discloses recurring billing in plain language next to the button if you rebill, with the amount, the interval, and how to cancel. Remove any claim you cannot support, which in supplements and similar verticals means removing disease and outcome claims entirely, as covered on the nutraceuticals and supplements page. Turn on the geo-blocking and age gating your vertical requires, and be ready to show it working. Pull the last six months of processing statements as full PDFs and read them yourself first, so you can explain any month that looks strange before you are asked.

Write a one-page cover summary: entity, product, monthly volume, average ticket, current ratio, fulfillment time, and one paragraph on any prior termination. It is not required anywhere and it consistently shortens the review.

What a realistic timeline looks like

A complete pack for a merchant with clean processing history is usually a decision in two to five business days at a domestic high-risk ISO. An incomplete pack with rolling question rounds is two to four weeks, and the delay compounds because each round waits on someone's queue on both sides.

Apply to two or three providers at once rather than sequentially. Underwriting is not exclusive, applying in parallel costs nothing, and the second and third approvals are the beginning of the redundancy described in the MID load balancing guide. Expect terms to differ for the same file, since appetite varies by acquirer and by month.

Expect an initial volume cap, a reserve, and a review at 90 days. Process inside the cap, keep the ratio clean, and ask for a reserve reduction at the review with your own numbers in hand. The first account you open on honest terms is the reference the next one underwrites against, and the full landscape of what those terms look like is in the high-risk merchant account guide.

Practical takeaway

The path that fails is applying early with a thin file and letting underwriting discover things. Every undisclosed termination, every mismatched name, every claim on the site that the application does not mention turns into a question round, and enough question rounds turn into a decline that follows you to the next application.

The path that lasts is boring. Assemble the full pack before you apply, make the website and the application say the same thing, disclose the bad history yourself with an explanation attached, and send it to three providers on the same day. Underwriters approve files they can finish reading, and the merchants who get approved fastest are almost never the lowest-risk ones, they are the ones who answered the questions before they were asked. If you want your pack reviewed against what underwriters in your vertical actually ask for, apply for an architecture review.