High-Risk Merchant Account With No Processing History

In brief

• Underwriters ask for statements to see how you handle other people's money. Volume is the least interesting number on the page.
• Visa's Acceptance Risk Standards put processing history on a list with credit history, financial statements, your business plan, your website, delivery and returns. Same clause. Not a pass/fail gate (AACQ.C5.1).
• With no history, you replace the missing file: personal credit, business bank statements, conservative projections, a compliant site, business age, owner experience.
• Stripe and Square are the fastest way to generate real processing data. Neither promises the account stays open, and Square's Payment Terms §3 excludes credit repair, high-risk products, adult entertainment and gambling outright.
• A reserve on a no-history file is normal. What matters is where the money sits, who controls it, and what triggers release.

A high risk merchant account with no processing history isn't a smaller version of a normal application. It's a different exercise. You're asking an underwriter to price a risk they can't see yet, and the only raw material you have is everything except card volume.

That's workable. Thin-history applications do get approved, often with reserves attached, and fat-history applications get declined for a website that contradicted the application. The statements are evidence. They were never the whole case.

Here's what the file looks like when the statements are missing.

Why underwriters ask for statements - and what they're really testing

Statements do one job: they turn your pitch into a pattern. Anyone can claim a hypothetical $180 average ticket and 4% refunds. A statement shows whether that's true, and whether it's been true consistently.

Visa spells out the requirement in the Visa Acceptance Risk Standards. AACQ.C5.1 requires acquirers to set risk-based onboarding criteria and segment merchants into low, medium and high risk, then underwrite each one. The underwriting review is supposed to cover creditworthiness - credit history, financial statements, performance, existing debts, public records - plus the business plan, URLs, goods and services, delivery methods, return policies, and business history including previous merchant accounts and processing history.

Read that list again. Processing history is one clause inside a long sentence. When you have none, the other clauses carry the file.

The four things a statement is really proving

1. Does the volume match the story? A site that looks like a boutique but applies for, say, $2M a year gets questions.
2. Can the account survive its own chargebacks? Under the Visa Acquirer Monitoring Program, a merchant's ratio is fraud (TC40) plus disputes (TC15) divided by settled transactions (TC05). The stakes are concrete: an acquirer portfolio is "above standard" at 50 basis points and "excessive" at 70. An individual merchant hits excessive at 220 basis points, and - since April 1, 2026 - at 150 basis points in the US. Add a monthly count threshold of 1,500 fraud and dispute transactions. The program's advisory period ended September 30, 2025, so those lines are being enforced against real portfolios now. If you want the mechanics in detail, our guide to the Visa Compelling Evidence 3.0 change on October 24, 2026 walks through the evidence bar.
3. Do delivery, refunds and cancellations match the website? An underwriter reads your refund policy while looking at your statement's refund line. Mismatches get flagged.
4. Is there a pattern of terminations? AACQ.C5.1 requires the acquirer to check internal terminated and declined merchant lists and the Terminated Merchant File (VMSS) before contracting. Our MATCH list guide explains what a listing means in practice.

No history is not the same as bad history

A blank file says nothing about your conduct. A file full of chargebacks, refund spikes and a terminated account says plenty - and it's harder to fix. If that's where you are, the post-decline and shutdown playbook is the right starting point, not this page.

For a genuine startup, the honest framing is: we're new, here's why we're safe to bank, here's how you'll know we're performing. Underwriters make decisions on that pitch all the time. Under the same Visa standards, the decision isn't binary anyway - approve, decline, or conditional approval with reserves, holds or guarantees.

What replaces processing statements

Six things. Bring all six and you have a file. Bring two and you have a request for more information.

Personal credit

What the underwriter is looking for: whether the person behind the entity has handled obligations before. AACQ.C5.1 lists credit history, existing debts and public records as part of the creditworthiness review. A personal guaranty is common on high-risk accounts, so the owner's file matters as much as the company's.

What to send: a credit report you pull yourself, plus a one-paragraph explanation for anything on it - a discharged medical collection reads very differently from a string of judgments. Don't make the underwriter ask. Unprompted context is the cheapest credibility you can buy.

Business bank statements

What the underwriter is looking for: money actually moving through the business. Deposits that track with your projections, payroll going out, suppliers getting paid, no bouncing. If you've been selling through an aggregator, those payouts appear here - and that's the closest thing to processing history a new business can produce.

What to send: every month you have, in full, including the pages with nothing on them. Redacted account numbers are fine; whited-out transaction lines are not.

Revenue projections

What the underwriter is looking for: whether you understand your own economics. A credible projection shows monthly card volume, average ticket, expected refund rate, repeat purchase rate, and the assumptions behind each. Round numbers with no logic behind them read as decoration.

What to send: a simple three-column sheet - conservative, expected, stretch - plus one page on how you acquire customers, what you pay for them, and how long they stay. Tie volume to something observable: ad spend, subscriber count, booking calendar, preorders. If your model is subscription, show churn.

A compliant website

What the underwriter is looking for: a site they can underwrite from. The Visa Acceptance Risk Standards include a website review checklist that points at your About, Shipping and Privacy Policy pages for detail on terms and conditions. Square's Payment Terms make the same point from the other direction: §34 states that network rules require you to disclose your return or cancellation policy at the time of purchase.

What to send: a live URL (not a landing page behind a password), a real business address and phone number, clear pricing, terms of service, a refund and cancellation policy written in plain language, and contact details that reach a human. For subscription billing, state the renewal terms and how someone cancels before they're charged. AACQ.C6.2 also expects e-commerce merchants to supply URLs plus verification of domain and website ownership, so keep the domain registration in the business's name.

Business age and formation documents

What the underwriter is looking for: a real legal entity with a paper trail. AACQ.C6.2 requires the acquirer to obtain a business license or registration certificate and verify it with business bureaus. AACQ.C6.1 lists the data they collect: DBA name, legal name, outlet address, phone, merchant category, and business registration or tax ID.

What to send: articles of formation, EIN confirmation letter, state business license, any professional license your vertical requires, and a certificate of good standing if your state issues one. A month-old LLC isn't disqualifying - it just shifts weight onto the other five items.

One thing that no longer needs to be in the packet: FinCEN finalized the beneficial ownership reporting revision on August 14, 2026. The final rule - "Beneficial Ownership Information Reporting Requirement Revision," 91 FR 52508 (FR Doc. 2026-16576) - adopts the March 26, 2025 interim final rule as final. Reporting companies no longer report beneficial ownership information for U.S. person beneficial owners, and U.S. person company applicants are exempt as well. Don't hand over a BOI report as a trust signal if it isn't required - hand over the ownership chart instead, which is what underwriters actually read.

Owner experience

What the underwriter is looking for: evidence that this isn't someone's first month in a regulated vertical. Prior operating roles, licenses, supplier relationships, fulfillment partners, a marketing track record in the category. If you've processed payments in this vertical before - even under a different entity - say so, because AACQ.C5.1 asks about previous merchant accounts and hidden history is worse than thin history.

What to send: a two-page owner resume focused on the vertical, plus names of the partners who do the work you don't do (fulfillment, compliance, customer support). For supplements, telemedicine, adult or dating, the underwriter is really asking: who stops a bad claim from going live?

Building history through an aggregator

An aggregator puts your business under its own master merchant account. You get a checkout, fast onboarding, and a monthly statement with your name on it. Stripe and Square are the two most common versions of this, and both say plainly that they aren't banks - Square does it in one line in Payment Terms §1.

That statement is the asset. Clean aggregator data answers the question a no-history file can't: how do you behave when real customers pay you with real cards?

Where the aggregator route works

Simple products. Transparent checkout. Low average ticket. Refunds you can explain. Card-present volume if you have a storefront. Digital goods that aren't on a prohibited list. If that's you, an aggregator is a sensible first home, and the data you generate is portable.

Where it breaks

High-risk categories run into the fine print fast.

• Square Payment Terms §3 lists the businesses you may not use the Payment Services for, and that list includes credit repair, high-risk products, adult entertainment and gambling.
• §8 states that Square or its acquiring bank may conclude you will not be permitted to use the Payment Services at all.
• §9 covers additional-information requests: refusing them can suspend or terminate the account.
• §14 lets Square require a reserve for any reason related to your use of the Services.
• Square's General Terms §12 allows suspension or termination at any time for any reason, and §1 covers accounts with inaccurate or incomplete information.
• Stripe maintains a restricted-businesses policy that requires pre-approval for certain categories, and its services agreement makes clear Stripe isn't a bank either. Read that list before you build a revenue plan on top of the integration: stripe.com/legal/restricted-businesses and stripe.com/legal/ssa.

So both platforms reserve the right to review your account, hold funds, request more information and decline or close you. That's not a scandal - they're carrying the risk of every merchant underneath them. It does mean an aggregator account is a starting position, not a destination. CBD and hemp merchants should also check the deadline history in our Square CBD and hemp guide before assuming an aggregator will keep the account.

The graduation path

Use the aggregator for what it's good at - data - and plan the exit before you need it.

Keep every statement. Export monthly, save the PDFs, note the dates. When you approach a high-risk processor, those exports become documented processing history with your dispute record attached. That changes the conversation about reserves. If your account gets frozen mid-move, our frozen-account guide covers what to do first.

And don't spike. A sudden volume jump your marketing can't explain is a common trigger for a hold. Ramp in line with what your marketing spend can explain.

How reserves differ when there's no history

With history, a reserve is priced off your numbers. Without it, the reserve is priced off uncertainty - and that changes shape more than size.

Visa's standards allow for exactly this. The underwriting outcome can be an approval conditioned on reserves, holds or guarantees. And AACQ.C3.1 is the clause worth memorizing: merchant reserves are merchant property held in a segregated deposit account. That money is still yours. Whether you can reach it is a contract question, not a bank question.

Which means the useful questions on a no-history offer aren't "what's the percentage?" They're:

• Rolling or upfront? A rolling reserve withholds a slice of each batch for a fixed period. An upfront reserve asks for a lump sum before you process a dollar.
• Where does it sit? Segregated account, whose name, and can you see the balance.
• What releases it? A calendar date, a review, or nothing at all until you close the account.
• What triggers a change? Chargeback thresholds, volume growth, a change of ownership.

Square's Payment Terms §14 gives a good sense of how broadly the right is written on the aggregator side - a reserve for any reason related to your use of the Services - and §21 links excessive chargebacks to reserves, payout delays, suspension or termination. High-risk processors write similar latitude into their contracts, which is why the release language matters more than the headline rate. Our rolling reserves explainer covers reserve types, release mechanics and how to ask for a reduction. For fees that sit alongside the reserve, see Mastercard specialty merchant fees.

The practical point: on a no-history file, a reserve is the price of admission, not an insult. Negotiate the release schedule and the review trigger. That's where the money is.

Documents checklist for a merchant account without processing statements

Document	Why it's in the file
Articles of formation, EIN letter, business license	Business legitimacy (AACQ.C6.2, C6.1)
Government ID for every owner above the threshold	Identity and signatory authority
Ownership chart	Replaces a BOI report for domestic entities
Three months of business bank statements, complete	Cash movement and consistency
Personal credit report, self-pulled, with written explanations	Creditworthiness (AACQ.C5.1)
Monthly projections with stated assumptions	Volume, ticket, refund rate, churn
Live website with terms, refund policy, contact page	Underwriting review, network disclosure rules
Domain registration and hosting proof in the business name	Domain verification (AACQ.C6.2)
Fulfillment, supplier or platform agreements	Delivery proof and dependency risk
Chargeback and refund handling process, in writing	Who does what, and how fast
Prior processor or aggregator statements, if any exist	Processing history - partial counts
Marketing samples and ad accounts	Claims review before launch

Send it as one organized folder. Files named "scan_0043.pdf" tell an underwriter how the rest of the relationship will go.

Telling your business story honestly

Underwriters read your file the way a skeptical customer reads your sales page. Anything that looks inflated in one place makes them doubt everything else.

That's not just underwriting instinct. It's the legal floor for your marketing too. Under 16 CFR 255.2, an advertiser must possess and rely on adequate substantiation for endorsement claims, consumer endorsements aren't competent and reliable scientific evidence, and a "results not typical" disclaimer doesn't cure a misleading testimonial. The same section bars distorting or misrepresenting consumer reviews.

In practice, that means the claims on your site should be ones you can defend with a document:

• Say "customers reported X in a survey of, say, 40 people" instead of "clinically proven."
• Show the range, not just the best outcome.
• Don't publish review screenshots you edited.
• Don't promise approval, income, weight loss or a medical result.

If your website says one thing and your application says another - different refund window, different product, different ticket size - expect a request for more information. Answer it fully and quickly. Square's §9 exists because ignoring that request is the fastest route to a closed account, and high-risk processors treat silence the same way.

Common mistakes on a no-history application

• Applying everywhere at once. Multiple simultaneous applications create multiple credit pulls and a messy story. Sequence them.
• Leading with the vertical instead of the controls. "We're in supplements" is a risk statement. "We're in supplements, here's our claims review process" is an underwriting argument.
• Hiding an aggregator shutdown. It shows up. Disclose it and explain the fix.
• Sending projections with no assumptions. Underwriters assume the worst about numbers that appear from nowhere.
• Ignoring the fee stack. The rate is the smallest part of the bill. Ask about monthly minimums, statement fees, PCI charges and network specialty fees before you sign anything.
• Accepting a reserve with no release language. If the contract doesn't say when the money comes back, assume the answer is "when we decide."
• Choosing on price alone. The cheapest offer on a no-history file is often the one that reprices you once the first review lands. Our offer comparison framework covers what to line up side by side.

How Find a Processor helps

We don't approve anyone, and we can't promise a decision - what we do is shorten the search.

One conversation is enough to introduce your business to a portfolio of processors that actually want to work with it. Not a directory of who "supports high risk" - a matched set of underwriters whose appetite fits your model, your geography and your checkout.

Here's what that looks like in practice:

• We read your file the way an underwriter will. Where the story breaks, where the documents contradict each other, what's missing that you didn't know to send.
• We match on the things that decide outcomes. Business model, ticket size, billing type, refund exposure, countries you sell to, and whether you're pre-launch or already live.
• We walk you through the offer. Pricing, reserves, contract length, termination terms, personal guarantees. We translate what the paperwork actually obliges you to do.
• We help you compare. Two offers that look identical on rate can differ by a large amount of money once reserves and fees land. We put them side by side.
• We stay in the conversation after launch. Reviews, volume increases, reserve reductions, a second acquiring relationship before you need one.

If you have no statements, say so at the start. It doesn't close doors. It tells us which processors to introduce you to first, and which ones will ask for paperwork that doesn't exist.

FAQ

Can I get a high risk merchant account with no processing history?

Yes - plenty of high-risk startups do. Underwriters replace statements with credit history, bank records, projections, a compliant website, entity documents and owner experience. The account often comes with conditions: a reserve, a delayed payout schedule or a personal guaranty. Conditional approval is a normal outcome, not a rejection.

What if I have no statements at all, not even an aggregator?

You'll lean hardest on personal credit, business bank statements and projections. Some processors will ask you to run a few months through an aggregator first, for the sole purpose of generating statements. That's a legitimate path, as long as your category isn't on the aggregator's prohibited list.

Do I need a business bank account before I apply?

Yes, in practice. Underwriters want to see business deposits, not personal ones, and settlement has to land in an account in the entity's name. Open it before you apply, and run real money through it - even small amounts - so the statements aren't empty.

Will a brand-new LLC get declined automatically?

No. Business age is one input among many under Visa's standards (AACQ.C5.1), and the same clause covers credit, financials, plan, website and owner experience. A new entity with a prepared owner and a clean, specific website can clear underwriting an older entity with a sloppy one cannot.

Is it better to start with Stripe or Square and switch later?

It depends on your category. If your product is straightforward and not on Square's §3 unsupported list or Stripe's restricted-businesses list, an aggregator is a cheap way to generate real processing data. If you're in credit repair, adult, gambling, or a high-risk product category, plan for a specialist from day one rather than building on an account that can be closed.

For a startup high risk merchant account in those categories, the aggregator step may not exist at all. Go straight to underwriting with the other six documents.

Why does a processor want a reserve when I have no history?

Because there's no track record to price. A reserve gives the acquirer collateral against chargebacks, refunds and delivery disputes it can't yet forecast. Visa's standards treat reserves as merchant property held in a segregated account (AACQ.C3.1), so the negotiation is about release terms and review triggers, not whether the money is yours.

How long does underwriting take with no history?

There's no fixed clock. What's predictable is that gaps in the file drive the timeline: missing bank pages, an unreachable phone number, a website policy that doesn't match the application. Complete files move. Incomplete files sit.

Can personal credit offset a thin business file?

It can carry real weight on a new entity, since the owner usually signs a personal guaranty anyway. A clean personal record with explained items helps. A file with judgments or a recent bankruptcy needs a written explanation and, often, a different processor than the first one you'd pick.

What if an aggregator already shut me down?

Disclose it and lead with the fix. Under Visa's standards the acquirer checks terminated and declined merchant lists before contracting (AACQ.C5.1), so it will come up. Our declined and shutdown guide walks through the recovery sequence and what to fix before reapplying.

Is this legal advice?

No. This is operational guidance, not legal, tax or accounting advice. If you're dealing with regulatory exposure in your vertical - supplements claims, telemedicine, adult content, crypto - get a lawyer who knows that space.

Sources

• Visa Acceptance Risk Standards (VARS) - AACQ.C2.1 merchant agreement; C3.1 reserves as merchant property; C5.1 risk-based onboarding, underwriting criteria and terminated merchant checks; C6.1 merchant data; C6.2 business license and domain verification; website review checklist.
• Visa Acquirer Monitoring Program fact sheet (2025) - ratio definition (TC40 + TC15 ÷ TC05), 50/70 basis point acquirer thresholds, 220 and 150 basis point merchant thresholds, 1,500 monthly count, advisory period end of September 30, 2025, April 1, 2026 US threshold change.
• Square Payment Terms - §1 "We are not a bank"; §3 unsupported businesses; §8 acquiring bank determination; §9 additional information; §14 reserves; §21 chargeback consequences; §34 return and cancellation disclosure.
• Square General Terms - §1 inaccurate information; §12 suspension or termination at any time.
• Stripe restricted businesses and Stripe Services Agreement - category approval requirements and the platform's non-bank status.
• Beneficial Ownership Information Reporting Requirement Revision, 91 FR 52508 (FR Doc. 2026-16576) - final rule published and effective August 14, 2026, adopting the March 26, 2025 interim final rule: no BOI reporting for U.S. person beneficial owners, and exemption for U.S. person company applicants.
• Beneficial Ownership Information Reporting Requirement Revision and Deadline Extension, 90 FR (FR Doc. 2025-05199) - March 26, 2025 interim final rule, effective March 26, 2025.
• 16 CFR 255.2 - endorsement substantiation, representative results, review integrity.

Ready to see who'll underwrite a file like yours?

No statements isn't a dead end - it's a file that needs building in a specific order. Tell us what you sell, how you bill and where the business stands today, and one conversation puts your application in front of processors whose underwriting actually fits it.

Start with Find a Processor →