What Underwriters Actually Check

A merchant account application contains fields to fill in. What it is actually doing is assembling a risk file that an underwriter will read the way a bank reads a loan application. The fields are prompts. The documents behind them are the evidence. What the underwriter is doing is building a picture of the business, the people who own it, and the probability that processing this merchant will cost the acquirer money.

Understanding what that picture needs to look like is the most useful preparation a merchant can do before applying. Most application problems are not discovered by underwriters. They are created by merchants who submitted incomplete or mismatched information because they did not know what the underwriter was looking for.

Table 1 — What underwriters review

Item	Why it is requested	What a weak answer looks like
Business formation documents	Confirms the legal entity is real, registered, and matches the name on the application	Entity name on the application differs from the registered name; no EIN confirmation letter
Government-issued photo ID	KYC identity verification for all beneficial owners holding 25 percent or more	Missing for a secondary owner; expired; name does not match entity documents
Business bank statements (3 to 6 months)	Confirms cash flow, operating activity, and capacity to cover a rolling reserve	Thin activity, large unexplained outflows, average balance insufficient for the requested volume
Processing statements (3 to 6 months)	Shows real transaction volume, average ticket, refund rate, and chargeback history	Chargeback ratio above 1 percent with no explanation; declining volume trend
MATCH database check	Standard screen for prior account terminations across all acquiring banks	Any active MATCH listing under the principal’s name, tax ID, or entity
Personal credit of principal owner	Indicates financial responsibility and capacity to guarantee obligations	Sub-600 credit score with no mitigating processing history or business financials
Website review	Confirms the business operates legally, sells what it says, and meets card brand disclosure requirements	Missing refund policy, no working contact page, deceptive product claims, pricing not visible
Business model description	Verifies the described model matches what the website and financials show	Vague product descriptions that do not match the MCC requested; fulfillment timeline unclear
Volume and ticket projections	Ensures the projected processing matches the business’s financial profile	Projected volume far exceeds what the bank statements can support
Industry-specific licenses	Required for regulated verticals to confirm legal authority to sell the product	No license submitted for a regulated category such as supplements, telemedicine, or firearms

One line applies to the whole table: underwriters find inconsistencies. A name that matches on the ID but not the bank account, a chargeback ratio in the statements that contradicts the projections, or a website that describes a different product than the application document all produce the same outcome. The file goes on hold or gets declined.

For merchants who need processing while a traditional underwriting application is in progress, RiskPay operates on non-custodial rails that do not require the traditional underwriting package described above. It does not require processing history, does not pull personal credit, and does not have a MATCH exclusion. It settles directly to a merchant wallet in USDC on Polygon and is available to most of the categories that standard and high-risk acquirers decline.

Processing History

If the merchant has accepted cards before, the prior processing statements are the most informative document in the file. They show the actual track record rather than the projected one. An underwriter reading three to six months of prior statements can see transaction volume by month, average ticket size, refund rate as a percentage of settled volume, and the chargeback ratio at the end of each period.

A clean prior history with steady volume, average ticket consistent with the business description, and a chargeback ratio well below 1 percent is the strongest single document a merchant can submit. It converts the underwriter’s risk assessment from a projection into a track record.

A history with chargebacks above 1 percent does not automatically kill an application, but it requires an explanation. Underwriters at high-risk acquirers are experienced readers of problematic histories. A spike that has a documented cause, a demonstrable correction, and a current ratio well below the peak is a manageable file. A history showing a ratio that rose and stayed elevated, or that the merchant cannot explain, is not.

Merchants who have no prior processing history face a different challenge. The underwriter cannot assess actual performance, which means everything else in the file carries more weight. Business financials, the owner’s credit, the quality of the website, and the specificity of the business model description all become more important when there is no processing record to anchor the evaluation. The guidance on what underwriters look for when there is no processing history is covered in the merchant accounts section of this site.

Business Bank Statements

Bank statements confirm the business is operationally active and financially capable of meeting reserve obligations. An underwriter reading bank statements is looking for three things: consistent revenue deposits that match the business’s described activity, no large unexplained outflows that suggest undisclosed liabilities or unusual transactions, and an average daily balance that is sufficient to cover the rolling reserve the acquirer will require.

The rolling reserve for a high-risk merchant account typically runs 5 to 10 percent of settled monthly volume, held for 90 to 180 days, though exact terms vary by acquirer, jurisdiction, and merchant profile. A business with a requested monthly processing volume of $100,000 and a 10 percent reserve requirement needs to demonstrate the cash flow capacity to have $10,000 withheld from each month’s settlements without disrupting operations. A business whose bank statements show average balances of $800 cannot credibly support that capacity.

Bank statements must be bank-originated PDFs. Screenshots are routinely rejected on format grounds at most acquirers even when the underlying numbers would have passed review.

Website and Compliance Review

The website review is the most frequently failed part of a high-risk application and the one merchants most commonly underestimate. Card brand rules require specific disclosures on any merchant website that accepts card payments. An underwriter who cannot find these disclosures on a live site will flag the application before looking at the financials.

The minimum required disclosures for a compliant merchant website are: a clearly labeled refund and return policy that matches what the merchant intends to honor, terms of service or terms and conditions that govern the transaction, a privacy policy that covers how customer data is handled, a working contact page or contact information that a customer could use to reach the merchant before filing a dispute, and accurate product or service descriptions that match what the business is actually selling.

For subscription and recurring billing merchants, the disclosure requirements extend to the billing frequency, the amount charged at each interval, and the mechanism by which a customer can cancel. A subscription checkout page that does not make these terms clearly visible before the customer enters their card information will not pass a website review at most high-risk acquirers.

Merchants who want to understand the full website compliance checklist that underwriters expect to see, and what specific elements prevent approval, will find it covered in the operations section of this site.

MATCH and Prior Terminations

The MATCH database check is automated and runs as part of every application at every acquirer that operates on Visa and Mastercard rails. It screens the principal owner’s name, personal tax identification number, and the business entity name and tax ID against the database of merchants terminated for specific cause. The FDIC’s examination procedures for credit card related merchant activities, published at fdic.gov, confirm that reviewing prospective merchants against the MATCH system is a documented underwriting standard requirement at acquiring banks.

An active MATCH listing is a hard stop at most standard acquiring banks, including most dedicated high-risk acquirers. The listing remains in the database for five years from the date of submission and can only be removed by the acquirer that placed it. A merchant with a MATCH listing who applies to a standard channel will be declined automatically before a human underwriter reviews any other element of the file.

The path forward for MATCH-listed merchants, and how to identify which acquiring channels do not rely on MATCH as a hard exclusion criterion, is covered in the guide to declined, shut down, and terminated merchant accounts.

The Owner’s Credit and Background

Personal credit pulls on the principal owner are standard for high-risk applications and common for standard applications as well. The underwriter is not assessing the owner’s personal financial situation as a primary risk factor. They are using it as one data point in a broader picture of whether this person has a track record of meeting financial obligations.

A sub-600 personal credit score is a negative factor. It is more meaningful when it is accompanied by no processing history and thin business financials, which means all three risk signals are pointing in the same direction. A merchant with weak personal credit but three years of clean processing history and strong bank statements presents a materially different file.

Background checks at high-risk acquirers extend beyond credit. Sanctions screening through OFAC and other regulatory databases is standard. Some acquirers run background checks that surface prior criminal history or regulatory actions relevant to financial services. For principals who have had prior regulatory issues, disclosure upfront is consistently more productive than concealment. Underwriters find most issues through their own checks. Voluntary disclosure reads as professionalism. Concealment reads as fraud risk.

Volume Projections and Ticket Size

Volume projections that do not match the financial profile of the business are a common application problem. A startup merchant with no processing history, two months of bank statements showing modest deposits, and a request for a $500,000 monthly processing limit will not receive that limit regardless of how legitimate the business is.

Underwriters use volume projections to set initial processing limits, not to approve or decline the application on their own. A realistic projection that matches the financial evidence available produces a faster approval and avoids a renegotiation conversation about limits after the fact. Acquiring banks adjust limits upward as the merchant establishes a track record. Starting with a realistic number is a better strategy than requesting a ceiling and receiving a conditional approval with a limit 80 percent lower.

What a Strong File Looks Like

A strong underwriting file has internal consistency. The business name on the application matches the entity documents, which match the bank account, which match the website. The processing history shows a track record that matches the volume projections. The website describes the same product the application describes. The owner’s identity is clear and verified.

The complete overview of what a high-risk merchant account involves, how underwriting fits into the approval process, and what happens after approval, including reserves, contract terms, and ongoing monitoring, is covered in the merchant accounts hub of this site.

Frequently Asked Questions

What do underwriters check on a high-risk merchant account application?

Underwriters review business formation documents, government-issued photo ID for beneficial owners, three to six months of business bank statements, prior processing statements if available, the business website for compliance disclosures, the MATCH database for prior terminations, and the personal credit of the principal owner. They are looking for internal consistency across all of these elements and for a financial profile that supports the requested processing volume.

Does a high chargeback ratio automatically decline a merchant account application?

A prior chargeback ratio above 1 percent raises a flag but does not automatically produce a decline at high-risk acquirers. It requires an explanation: what caused the spike, what operational change addressed it, and what the current ratio looks like. A history that shows a documented cause and a demonstrable correction is a manageable file. A history showing an elevated ratio the merchant cannot explain is not.

Does personal credit affect merchant account approval?

Yes, but it is one factor among several. A sub-600 personal credit score is a negative signal. It becomes more significant when it is accompanied by no prior processing history and thin business financials. A merchant with weak personal credit but strong processing history and healthy bank statements presents a materially different file than one where all three factors are negative.

What website disclosures does an underwriter check?

An underwriter checks for a clearly labeled refund and return policy, terms of service or terms and conditions, a privacy policy, a working contact page, and accurate product or service descriptions that match the business description in the application. Subscription merchants must also have visible billing frequency, amount, and cancellation mechanism on the checkout page before the customer enters card details.