Merchant Account Underwriting: What Acquirers Check First
Card scheme rules and bank supervisors set the floor for merchant account underwriting. We map what an acquirer reviews before an online store can take cards.
Merchant account underwriting is the acquirer's credit and compliance review of a store before the first card payment. It decides whether a merchant gets an account, on what terms and with what reserve. Pricing comes later. For an online store, most of the outcome is settled by documents prepared before the application is sent.
The checks are not secret. They are simply spread across rulebooks that few merchants read end to end, written for acquirers and examiners rather than for the store owner who has to supply the evidence. Visa publishes its Core Rules, Mastercard documents its terminated merchant database, and the US bank supervisor OCC prints an underwriting checklist for examiners.
We read those sources side by side, because an application built against them leaves the underwriter fewer questions. Fewer questions usually mean a faster decision.
Our advice therefore comes at the start, not at the end. Never send an application before the file agrees with itself. Prepare the website, the processing history and the ownership file before applying, and keep each one consistent with the others.
What is merchant account underwriting actually checking?
It checks a handful of things at once: that the business is real, that it can carry its refunds and chargebacks, and that it sells only what the rules allow. Every other request in the file serves one of those aims.
Visa's Core Rules set the floor in one paragraph. Before signing, "an Acquirer or a Payment Facilitator must ensure that the prospective Merchant is all of the following". The list then names financial responsibility, a lawful jurisdiction and an honest declared location.
One item on that list is broad on purpose. The merchant must be "Not engaged in any activity that could cause harm to the Visa system or the Visa brand".
The acquirer carries the risk if it gets this wrong. When a store disappears with prepaid orders, refunds flow back as chargebacks, and the acquirer pays them if the merchant cannot.
That is why the review looks like credit underwriting. The product is card acceptance, but the exposure is unpaid future refunds.
Category is the quiet part of the check. The OCC asks underwriters to understand the business well enough to place it under the correct merchant category code, and the code chosen at onboarding then follows every transaction the store sends.
Selling one thing on paper and another in practice fails here. Visa's rules add a separate bar. "An Acquirer must not knowingly accept from a Merchant for submission into the Visa payment system any Transaction that is illegal", and so a vague product description reads as a risk, not a shortcut.
Which underwriting documents does an ecommerce store need?
Expect a signed application, a signed processing agreement, identity and ownership papers, financial statements and recent processing statements. The exact pack varies, but the core list is stable across acquirers.
The OCC's handbook for examiners starts from a formal policy. It tells bank management to adopt a written merchant underwriting and approval policy as a control on credit risk, and then sets a minimum.
Its list of underwriting documents for ecommerce and other merchants reads like an application checklist. It includes a signed corporate resolution where relevant, an on-site inspection report or verification of business, and credit bureau reports on the principal within the limits of the Fair Credit Reporting Act.
Trade and bank references are on the list too. And it asks for proof that the merchant is not on the US sanctions list or on Mastercard's MATCH list.
Processing history carries the most weight in our reading. The OCC expects the bank to analyse recent monthly statements from the merchant's current or most recent processor if such statements exist.
Those statements show volumes, refund rates and chargebacks month by month. An underwriter can compare them against the volume the merchant declares on the new application.
Merchants moving from one provider to another should keep their statements ready. A store with none will be judged on its business plan and owner credit instead.
The booklet also mentions a Paydex score from Dun and Bradstreet where one exists. It is listed as extra information, and the OCC states it does not endorse particular vendors.
Why does the acquirer look at ownership and control?
Because the acquirer must know who it is really contracting with, and anti-money laundering law makes that a legal duty for banks. The ownership file is not a formality.
In the United States, the customer due diligence rule requires covered banks to identify anyone owning a quarter or more of a legal entity customer, plus one person with significant control. European acquirers apply their own national anti-money laundering rules to the same question.
Payment facilitators run a similar process. Stripe's documentation says regulators enforce Know Your Customer rules "to make sure that Stripe collects, verifies, and maintains identity information from certain types of businesses and from individuals who ultimately own, control, or direct them."
Mismatches are the common failure, and they are entirely avoidable. A one-page ownership chart that runs from the trading company up to the individuals at the top answers most of these questions before anyone asks them, and it costs the merchant an hour. The owner on the application differs from the company register, or a holding company appears with no explanation of who stands behind it.
What does the website review look for?
The underwriter reads the store's site as a cardholder would, looking for clear contact details, honest policies and a visible merchant location. Missing pages slow the review more than almost any other gap.
Visa's rules list what an ecommerce site must show. The list covers a customer service contact, the address for cardholder correspondence, a policy on split shipments, and the country of the merchant outlet during checkout.
A useful self-test is to walk the site the way a buyer would, adding an item to the basket and going through to the payment page. Anything a buyer cannot find there, an underwriter reading the same pages will miss too.
The country rule is strict about placement. It must appear on the checkout screen or within the checkout pages, and Visa adds: "A link to a separate web page does not meet this requirement."
For internet merchants, the OCC's list overlaps and goes further. It includes a customer service number, the real name of the operating company where an alias is used, delivery methods and timing, refund and return policies, a statement on security controls and a privacy statement.
Every item can be checked in an afternoon. The refund policy and the real name of the operating company appear in both lists, and both are easy to get wrong when a brand name differs from the legal entity.
How do MATCH and terminated merchant lists affect merchant account approval?
A listing does not legally bar approval, but it changes the conversation completely. Acquirers must search these databases before signing, and a match triggers questions the merchant has to answer.
Mastercard describes MATCH Pro as a lookup that shows an acquirer whether another acquirer terminated a merchant earlier, and why. Its page says acquirers can draw on up to five years of termination history.
Visa sets the same duty in its own words. Its database rules run on a three-year clock: a merchant terminated for cause is listed for that period, and the acquirer keeps the termination information for the same span. An acquirer must "Query a common terminated Merchant database before entering into a Merchant Agreement with a prospective Merchant".
The rule then limits how the result is used. Visa treats the terminated merchant file as information for the decision, not as an automatic refusal.
When there is a possible match, Visa's rule has two parts. The acquirer must "Verify that the Merchant identified in the response is the same Merchant for which the inquiry was generated", and it must "Contact the listing Member directly to determine why the Merchant was added to the file". A merchant with a past termination is better off disclosing it with documents than letting the database speak first.
Why do some categories face a longer review?
Some lines of business carry extra scheme registration, and the acquirer needs permission before it can process for them. Visa calls these High-Integrity Risk Merchants and assigns the label by merchant category code, as set out in its Integrity Risk Program Guide.
Before processing for such merchants, Visa requires the acquirer to "Submit to Visa a High-Integrity Risk Acquiring Registration Application and be approved by Visa". The acquirer must also register each such merchant through Visa's program tools.
So a merchant in a listed category can wait longer than a clothing store with identical paperwork. The delay sits at the acquirer and scheme level, not only in the merchant's file.
The file also stays alive after approval. For these merchants Visa expects the acquirer to start daily monitoring from the 31st day after the first deposit, and on request to send Visa a short list of records within a week. First on that list stands the "Original Merchant underwriting package", so the documents a store supplies at onboarding can be read again by the scheme years later.
Visa also requires due diligence before any contract, high risk or not. Its rule asks for "an adequate due diligence review, including a site visit to the business premises (if applicable) or suitable alternative".
For a purely online store, the suitable alternative is usually the website and document review described above, since there may be no premises a visit could usefully show.
What terms come with an approval?
An approval often arrives with conditions. A reserve, a processing limit, a delayed settlement schedule and a security validation requirement are the usual ones.
These terms are part of the underwriting decision itself. They are the price the acquirer sets for the risk it accepted when it said yes, and they are written into the merchant agreement that the store signs before its first transaction goes through.
The OCC names the most common tool directly. Its booklet notes that many banks hold back part of a higher-risk merchant's funds in a reserve account to limit credit risk.
Security validation is the other standing condition. The PCI Security Standards Council states that "Compliance validation requirements are set by brands, acquirers, payment facilitators, etc., which are often referred to as compliance enforcing entities."
So the acquirer decides which self-assessment questionnaire a store files. A store using a hosted payment page typically has a lighter form than one handling card data on its own servers.
Terms are reviewed again as the store grows. A reserve set at approval can be revisited once the merchant has a clean processing record with the new acquirer.
What the data does not show
Acquirers publish no approval rates by category, and the schemes publish none either. No public dataset tells a merchant how likely approval is for its profile.
Decline reasons are thin as well. A merchant refused by one acquirer often learns little about which line of the file caused the refusal, and nothing in the scheme rules we read obliges the acquirer to explain its credit judgment in detail.
Timing is another blank. We found no published service level for underwriting decisions in the scheme rules or the OCC booklet.
We also cannot see each acquirer's internal risk appetite. Two providers reading the same file can reach different answers, and neither is obliged to explain the scoring.
Rules quoted here are the floor. They are also written for the acquirer, not for the merchant. A store owner reading them can find whole sections that skip what the store has to send, even where those sections decide its application. Each acquirer layers its own policy on top, and that policy is rarely public.
Answers for a specific store sit with people rather than rulebooks. The acquirer's underwriting team is the only source for its own document list and reserve policy. A payments lawyer can review the merchant agreement and any reserve clause before signature. The points worth reading twice are how the reserve is calculated, when it is released after termination, and what triggers a change in terms.
An accountant can prepare financial statements in the form underwriters read easily, with revenue split by channel so that card sales can be matched against processor statements line by line. A clean set of accounts that matches the processing statements answers a large part of the review.
Our view
Underwriting rewards consistency more than size. A small store with a tidy file can be an easier yes than a large one with gaps, because the acquirer is pricing uncertainty as much as volume, and uncertainty shows up as reserves. A store whose website, ownership file and processing statements tell one story is a straightforward approval for most acquirers.
The scheme rules and the OCC checklist are public, so the preparation can be done before any application exists. A missing policy page or an unexplained owner is exactly the gap these documents are designed to catch.
What stays opaque is the scoring itself. Nobody in the acquiring chain publishes how much weight a single chargeback month carries. That makes the scoring hard to plan around.
Sources
- Visa Core Rules and Visa Product and Service Rules, October 2026 edition usa.visa.com.
- Mastercard Developers, MATCH Pro developer.mastercard.com.
- OCC Comptroller's Handbook, Merchant Processing occ.gov.
- PCI Security Standards Council blog, updates for merchants validating to SAQ A blog.pcisecuritystandards.org.
- Stripe Docs, Upcoming requirements updates docs.stripe.com.
- 31 CFR 1010.230, Beneficial ownership requirements for legal entity customers ecfr.gov.