Skip to content
← All insights

Merchant Application Fields That Kill Deals

Ownership %, SSNs, MATCH hits, mismatched DBA, and unsigned pages. Pre-fill beats a stalled 10-pager.

Merchant applications stall on incomplete or inconsistent fields, not on the rate you quoted. The five that kill deals in underwriting are ownership percentages that omit a 25 percent owner or fail to add to 100, missing Social Security numbers, MATCH hits you did not surface, a legal name that does not match the DBA, and unsigned required pages. Pre-fill the packet before the merchant ever sees a 10-pager. A priced deal with a hollow application is not a deal.

The acquirer, the bank-side network member that will sponsor the merchant ID, is underwriting a credit and BSA file. The OCC tells banks to define what each application contains, including type of business, location, and Social Security number or tax ID for the entity and the principal owners, and to require a signed application and a signed processing agreement (OCC, Comptroller's Handbook, Merchant Processing, August 2014). FinCEN's Customer Due Diligence Rule requires covered banks to identify and verify beneficial owners: each individual who owns 25 percent or more, plus one individual who controls the entity (FinCEN CDD Rule; FinCEN CDD Rule FAQs, consolidated 6 May 2026). Those are not processor preferences. They are how a bank is allowed to open the account.

FinCEN defines two prongs. The ownership prong is each natural person who, directly or indirectly, owns 25 percent or more of the equity. The control prong is one individual with significant responsibility to control, manage, or direct the entity: a CEO, managing member, general partner, president, or anyone who actually runs it. Under that definition a legal entity has between one and five beneficial owners: one control person, and zero to four owners (FinCEN CDD Rule FAQs, B.5, consolidated 6 May 2026). Nominees and straw owners do not count. The institution may rely on what the customer's representative certifies unless it has reason to doubt it.

That is why "she's my spouse, we file jointly, list me at 100" fails when both own 50 percent, and why "the silent partner is only 25, leave them off" fails on the ownership prong. Percentages that sum to 80, or to 120, are the same class of error: the bank cannot tell who owns the risk. Banks may collect below 25 percent on a risk basis (FinCEN CDD Rule FAQs, B.11). Do not assume your acquirer's form stops at the federal floor. Ask what the packet actually requires, then collect that set in the room.

Illustrative. Four members: 30 percent, 30 percent, 25 percent, 15 percent. The application lists the two 30 percent owners as "the partners." FinCEN still needs the 25 percent owner, plus one control person. The 15 percent owner is below the ownership prong and still may be the control person. If you send the two-name version, underwriting sends it back. Days die there, not on interchange.

SSNs are how the bank knows the person

For each beneficial owner and the control person, covered institutions collect name, date of birth, address, and Social Security number or another government identification number (passport or similar for a foreign person) (FinCEN CDD Rule FAQs, B.7). That is the same element set a bank uses under its customer identification program. A missing SSN is not a privacy flourish the merchant can skip. It is an identity the bank cannot verify.

The same string is what screening runs on. The OCC's underwriting minimums include evidence the merchant is not on OFAC's Specially Designated Nationals list and not on the bank card industry MATCH list (OCC, August 2014). A transposed SSN, a store listed as a home address, or a maiden name that does not match the ID produces a false miss or a false hit. Collect legal name as it appears on the government ID, residential street address, date of birth, and SSN in the first sitting. "Come back later for the numbers" is how the incumbent keeps the deposits while your file sits in a queue.

MATCH hits you did not pre-screen

Mastercard Alert To Control High-risk Merchants (MATCH) Pro is Mastercard's terminated-merchant file. Before executing a merchant agreement, the acquirer must inquire on the merchant and associated principal owners. MATCH Pro then searches additions other acquirers made during the past five years, a 60-month window, and returns an exact or phonetic possible match (Mastercard MATCH Pro documentation). It supports 1 to 5 principals on a single inquiry (Mastercard MATCH Pro support FAQ). You cannot query it from a browser. The merchant cannot Google themselves off it. The longer merchant-facing version is the MATCH list.

A possible-match is not an automatic decline. Mastercard describes MATCH Pro as a tool for the acquirer to make an independent risk determination. The OCC says MATCH is the starting point, and the bank still does its own due diligence (OCC, August 2014). What kills the deal is surprise. Underwriting finds a phonetic match on an owner you did not list, or a prior DBA you described as "we just switched." The file stops. If the merchant never told you they were terminated, you promised a MID you cannot board on the timeline you sold.

Ask before the demo: have you or any owner been terminated by a processor, had a reserve seized, or been told you were on MATCH? A yes is an underwriting fact. A documented no is still not a MATCH clearance. Only the acquirer can inquire. Your job is not to clear the list. It is to stop treating a MATCH-eligible history as a first-week surprise.

How to keep a merchant application from stalling
  1. 1
    Collect the identity set first. Legal name, DBA, EIN, address, and every owner at 25 percent plus one control person, with SSN, date of birth, and home address.
  2. 2
    Reconcile the names. Legal name matches IRS and formation documents. DBA matches signage and the cardholder descriptor. Ownership percentages add to 100.
  3. 3
    Screen the story before you promise a MID. Prior closures, MATCH, OFAC, and a wrong MCC are underwriting facts. Ask before the demo.
  4. 4
    Get a signature on every required page. OCC underwriting expects a signed application and a signed processing agreement. An unsigned last page is a return, not a queue.

Mismatched DBA is a different business on paper

Legal name is the entity the Secretary of State and the IRS know. DBA is the trade name on the awning. MATCH Pro stores both (name and doingBusinessAsName) because acquirers inquire on both (Mastercard MATCH Pro). The merchant category code is assigned from the actual business by sales volume. If the legal name is an LLC holding company, the DBA is a restaurant, and the application describes retail gift shops, underwriting does not know which file it is opening.

Three strings have to agree with the documents you attach:

  • Legal name matches the EIN letter, articles, and the signature block on the merchant agreement.
  • DBA matches signage, the website, and the descriptor cardholders will see.
  • Address is the operating location, not a PO box you used on a flyer.

A one-character miss ("Riverstone Hospitality LLC" vs "River Stone Hospitality, LLC") is enough for a TIN match to fail and for MATCH to phonetic-match the wrong record. Do not "clean up" the name to look nicer. Copy it from the IRS document.

Unsigned pages send the file home

OCC underwriting standards require, at a minimum, a signed application and a signed processing agreement, plus a signed corporate resolution when the entity type calls for one (OCC, August 2014). The last page is where deals go to die. The owner initialed page 1 on a phone, never opened the personal guarantee, and the packet sits as "received, incomplete." E-sign is fine when the platform records a signature on every required document. A screenshot on the wrong entity name is not.

Personal guarantees, PCI acknowledgements, and ACH origination authorizations are separate signatures on many packets. Count them. If the 25 percent owner is not in the room, you do not have a complete file. "They will sign Friday" is how a residual you already spent in your head stays with the incumbent.

Pre-fill beats a stalled 10-pager

A useful onboarding workflow collects the required information clearly, identifies missing documents, and makes the next step visible. Ask the partner to demonstrate the actual workflow and explain underwriting responsibilities. Approval and timing depend on the merchant, the completed application, and the applicable review.

Illustrative sequence, not a case study. Tuesday you leave a paper application. Thursday two of four owners filled page 1. Next Tuesday underwriting asks for the missing 25 percent owner, an SSN, and a voided check that matches the legal name. The merchant is still live with the current processor. That gap is attrition on a book you never boarded.

Do the work in the first meeting: legal name, DBA, EIN, owners at 25 percent, control person, SSNs, dates of birth, home addresses, operating address, MCC that matches what they sell, prior processor statements, and a yes-or-no on prior terminations. Then send a complete, signed file. Pricing arguments happen after the bank can see who it is sponsoring.

The sales-rep page is the front door for how Relyon boards. Residuals start when the MID is live. Incomplete fields are how a sold deal never becomes one.

FAQ

Why do merchant applications get declined or stalled? Underwriting is identity and risk first. Incomplete ownership, missing SSNs, a MATCH possible-match, a legal-name or DBA mismatch, or an unsigned application will stall or decline a file before anyone prices the account.

What ownership percentage must be listed on a merchant application? FinCEN's CDD Rule requires covered banks to identify each individual who owns 25 percent or more of the legal entity, plus one control person. Percentages on the application should add to 100 percent. Leaving off a 25 percent owner is not a shortcut.

Why does a merchant application ask for Social Security numbers? Covered banks must collect name, date of birth, address, and SSN or another government identification number for those beneficial owners and the control person. The same identity set is what MATCH Pro and OFAC screening run on.

Does a MATCH hit automatically decline a merchant application? No. MATCH Pro is a mandatory acquirer inquiry before the merchant agreement. Mastercard describes it as an input to an independent risk determination, not an automatic ban. A hit you did not disclose still stalls the file.

What is a DBA mismatch on a merchant application? Legal name is the entity on IRS and formation documents. DBA is the name on the door and often on the cardholder descriptor. When those strings do not match the documents attached, underwriting stops to ask which one is real.

How do I keep a merchant application from stalling in underwriting? Collect the identity set before the demo. Reconcile legal name, DBA, EIN, and ownership to 100 percent. Ask about prior MID closures. Do not send a file with unsigned required pages.

Sources

Questions about how this applies to your business?

Talk it through

Your next move

Clarity looks good
on your business.

Analyze a statement