High Risk Merchant Account Documents: The Full Checklist
Quick answer: A typical high-risk merchant account application asks for a lot: photo ID and Social Security numbers for every owner with 25%+ equity, a certificate of incorporation or business license, 3 to 6 months of bank statements, one to two years of tax returns, a voided check, a processing history if you've had a merchant account before, and a live website with pricing, refund policy, and contact information already in place. Missing any one of those is a common reason applications sit for weeks or get declined outright. ePayVista skips that file entirely. There's no underwriting packet to assemble because there's no underwriter deciding whether to approve you; you install the WooCommerce plugin, connect an account only you control, and you're live in about 5 minutes.
If you've ever stared at a high-risk processor's application portal wondering why a payment account needs the same paperwork as a small business loan, here's exactly what's usually requested, why, and what changes when approval isn't a lending decision in disguise.
What documents does a high-risk merchant account actually require?
Most high-risk processors build their application around proving three things: who you are, that your business legally exists, and that it has stable cash flow. That translates into:
- Personal identification for every owner. A valid government-issued photo ID, proof of address, and the Social Security number of each beneficial owner holding 25% or more of the business.
- Business formation documents. A certificate of incorporation, articles of organization, or a valid business license, plus a description of your structure (sole proprietorship, LLC, corporation, DBA).
- Bank statements. Typically 3 to 6 months, sometimes a full year for higher-volume applicants, used to verify the business is operational and cash flow is stable.
- Tax returns. One to two years of business tax returns for established businesses; startups may be asked for financial projections instead.
- A voided check or bank letter confirming where payouts will land.
- Processing history, if you've held a merchant account before, including chargeback and refund ratios from the prior processor.
- A live, compliant website with visible pricing, a refund/return policy, terms of service, and working contact information. Underwriters review this directly, and a site missing any of those is one of the most common reasons an application stalls.
Why does a payment account need this much paperwork?
Because a high-risk merchant account application isn't really an application to move money, it's an application for the processor's own risk exposure. When a processor approves you, they're personally on the hook if your customers file chargebacks faster than expected or your business turns out not to be what the application said. Every document on that list exists to let an underwriter estimate that risk before they take it on, the same way a bank underwrites a loan before handing over money it might not get back. That's why the packet looks financial rather than operational: it's built to answer "will this account cost us money," not "can this business process a card."
How long does gathering all of it usually take?
Longer than most first-time applicants expect, and it stacks on top of the review time itself:
- A first-time applicant without existing bank statements or tax returns organized in one place often spends 1 to 2 weeks just assembling the packet, before underwriting review even starts.
- A missing document restarts the clock. Processors commonly pause the file the moment one item is incomplete, and re-review after resubmission isn't instant.
- A thin processing history invites more questions. No prior merchant account, or a short one, often triggers a request for additional financials that weren't on the original checklist.
- Vertical category adds scrutiny. CBD, vape, forex, gambling, adult, supplements, and peptides businesses frequently get asked for extra documentation, like lab results, licensing, or age-verification proof, on top of the standard file, purely because of the category code.
What happens if a document is missing or a detail doesn't match?
The file typically goes back into a queue, not forward. A tax return that doesn't match the bank statements, a website missing a refund policy, or an owner listed inconsistently across documents are common reasons underwriters pause a file rather than reject it outright, which can quietly add days or weeks without ever producing a clear decline. Applicants rarely get a full list of everything wrong at once; documents often come back one at a time, each round adding its own review cycle.
Traditional application file vs. ePayVista setup
| What's required | Traditional high-risk merchant account | ePayVista |
|---|---|---|
| Personal ID + SSN for 25%+ owners | Yes | No |
| Certificate of incorporation / business license | Yes | No |
| 3-6 months bank statements | Yes | No |
| 1-2 years tax returns | Yes | No |
| Prior processing history / chargeback ratios | Often requested | No |
| Website compliance review by an underwriter | Yes | No |
| What's actually needed | A completed underwriting packet | A WooCommerce plugin install and an account only you control |
| Decision-maker | A human underwriter assessing risk | Nobody deciding whether to approve you |
| Typical time to live | Days to weeks, longer if a document is missing | About 5 minutes |
Why ePayVista doesn't ask for an underwriting file
The traditional document list exists because a processor is deciding whether to take on your chargeback and fraud risk with their own money. ePayVista's rail removes that exposure structurally: customers pay by card at checkout, and settlement moves through our managed, non-custodial layer straight into an account only the merchant controls, on a flat 1%, with no chargebacks landing on anyone's books to underwrite against. There's no risk file to build because there's no lending-style decision being made. Getting started is a WooCommerce plugin install, not a document checklist.
FAQ
Do I need tax returns to accept payments with ePayVista?
No. ePayVista doesn't run an underwriting review, so there's no tax return, bank statement, or processing-history requirement to submit before you can go live.
Why do high-risk merchant accounts ask for personal Social Security numbers?
Processors require SSNs for any owner holding 25% or more of the business as part of standard KYC and underwriting practice, since they're personally guaranteeing the risk they're taking on by approving the account.
What's the single most common reason a high-risk application gets delayed?
A website missing pricing, a refund policy, or contact information. Underwriters review the live site directly, and gaps there are flagged as often as missing financial documents.
Is a longer processing history required to get approved faster?
It helps but isn't required. A thin or nonexistent processing history usually means more follow-up questions on a traditional application, which is a different problem on ePayVista since there's no processing-history review at all.
How does approval work if there's no underwriting file?
Approval is setup, not underwriting. You connect an account only you control and install the plugin; there's no risk decision being made about your business because there's no chargeback exposure being extended to a processor.
Stop renting your revenue.
Install the WooCommerce plugin, connect your payout account, and get paid in about 5 minutes. Flat 1%. No freezes.
Download the WordPress plugin