
Industry
Part of Online Business Banks: Audit the Branch Jobs You Would Lose
Online business banks requirements: six prep lessons
Online business banks requirements: six lessons on entity records, identity and ownership, addresses, permissions, and remote application readiness.
A branchless provider asks for what any institution asks for: proof the entity exists, proof you may act for it, and enough information to decide whether it wants your business. Execution is different. A branch can look at a document and ask a question. A remote flow either matches your data or stops, often without telling you which field failed.
That difference is the subject of this page. This guide to online business banks requirements focuses on that difference. The six lessons explain what a fully digital application may demand beyond the usual paperwork, why applications stall, and how to prepare. Examples of providers with online business-account applications include Chase, Bluevine, Mercury, and Relay. This guide covers common evidence, not a guarantee of any provider's current requirements; confirm eligibility, documents, and deposit arrangements directly before applying.
What to take away
- The evidence is the same. The tolerance for inconsistency is much lower, because the first pass is automated.
- Every person who must be verified needs to be reachable, with their own identification and their own device, in the same short window.
- Set up authority deliberately at opening. Without a branch conversation, permissions are whatever the default screen gave you.
Lesson 1: Prepare entity and tax documents
Expect to provide your entity's formation documents and employer identification number (EIN) confirmation. Depending on your entity and the provider's request, formation documents may include Articles of Incorporation, a Certificate of Formation, or an Operating Agreement; a Certificate of Good Standing may also be requested. The IRS issues a CP 575 notice when it assigns an EIN and can provide a 147C letter to verify it. Form SS-4 is the EIN application, not confirmation that an EIN was assigned. See the IRS information on the employer identification number.
You provide identification for the individuals involved, details on who owns and controls the business, and a description of what the business does. Under FinCEN's Customer Due Diligence (CDD) Rule, covered financial institutions generally identify and verify beneficial owners of legal-entity customers, subject to exceptions. Applications may ask for a beneficial-owner certification; the exact request depends on the institution. The rule requires banks to collect beneficial ownership information at the 25 percent ownership threshold, regardless of the customer's risk profile.
Lesson 2: Capture complete, consistent records
Capture is where remote applications differ. A few practical points save most of the delay. Assemble clear, complete records—the full formation document, EIN confirmation, requested identity documents, and address evidence—and check the provider's accepted-ID list; a driver's license or passport are examples of photo ID. Avoid cropped pages and glare. Before submitting, compare the application with the source records for the exact legal name, addresses, and ownership details, then save a copy of what you sent.
Document capture rules
- Photograph flat, full, all four corners
- Use the requested document type
- Check names and dates are legible
- Confirm ID is current, check expiry
- Keep file names and formats standard
Lesson 3: Match addresses and complete identity checks
Exact matching. Automated checks compare what you typed against registry and reference data. A suffix present in one place and absent in another, a trading name in a legal name field, or an address written in a different format can produce a mismatch that a person would have resolved in a sentence. Copy the legal name character for character from the filed document.
Remote flow vs counter
Remote flow
- Name matching
- Exact, automated
- Addresses
- Assumed identical
- Identity check
- Live photo required
- People timing
- Short window
Counter
- Name matching
- Person resolves
- Addresses
- Explained verbally
- Identity check
- Document shown
- People timing
- Whenever present
Address handling. Registered address, mailing address and place of business are different things, and remote forms often assume they are the same. Know which is which before you fill anything in, and expect evidence to be requested for the trading address.
Identity verification of people. Banks must maintain a Customer Identification Program (CIP) under the Bank Secrecy Act (BSA), as amended by the USA PATRIOT Act. FinCEN administers the BSA, while bank regulators oversee compliance. CIP rules require identity-verification procedures, but do not make a live photo the universal legal method. A provider may use a photograph taken at that moment and matched against identification as its remote method. This needs a decent camera, decent light, and a person who is actually available. It is a frequent cause of an application sitting untouched.
Everyone at once. Where several owners or controllers must be verified, remote flows tend to want them within a short window. Find out early who is required, tell them what to expect, and check that nobody is traveling. This is the part that is easy to arrange in advance and painful to arrange retrospectively.
Activity and sanctions screening at signup. Providers decide at application time whether they will serve your industry, and the answer can be a flat no with no route to discuss it. Providers may also screen applicants and related parties against sanctions lists maintained by the U.S. Treasury Department's Office of Foreign Assets Control (OFAC). Ask about industry eligibility before assembling documents, and get the answer in writing from a named person.
Lesson 4: Configure account authority and permissions
Without a conversation at a counter, permissions default to whatever the software does. Treat setup as a required step rather than an afterthought.
Authority setup checklist
- Separate view, initiate, approve permissions
- Set approval threshold above chosen amount
- Bind access to more than one device
- Record recovery access in writing
- Review permissions when people join or leave
Authority is configured
- Decide who may view, who may initiate, and who may approve, and configure those separately if the provider allows it.
- Set an approval requirement above a threshold you choose, if the feature exists. If it does not, that is a finding about the provider.
- Bind access to more than one person's device. An account whose only second factor lives on one phone has a single point of failure that becomes obvious at the worst possible time.
- Record who holds recovery access and how account recovery actually works, in writing, before you need it.
- Review the permission list whenever someone joins or leaves. Remote accounts accumulate stale access because nobody walks past the person who left.
Lesson 5: Respond to an automated decision
Applications are sometimes declined without a stated reason, and there may be no person to ask on the day. That is frustrating and it is worth handling methodically.
Keep a record of exactly what you submitted and when. Ask in writing whether the application can be reconsidered and what additional evidence would help.
Correct anything you know is inconsistent across your own documents, because that is the most common cause and the only one entirely within your control. If your industry is the issue, no amount of documentation fixes it, and you need a provider whose policy accepts your activity.
Meanwhile, do not stall your operations behind one application. The general path an application takes, and what happens after approval, is set out in how applications are assessed.
Lesson 6: Check readiness before you begin
A readiness list
- The legal name copied exactly from the filed document, with the same suffix everywhere.
- Registered address, mailing address and trading address separated, each with evidence.
- The entity tax identifier, and the formation document as a clean full page scan.
- Current identification for every person who must be verified, checked for expiry.
- A confirmed window when all those people are available with a working camera.
- A written statement of what the business does, including secondary activity, that matches your registrations.
- Realistic expectations of volumes, cash use and payment types, since these get asked and later compared against behavior.
- Written confirmation that the provider serves your industry.
Before you start
Spend an hour making your own documents agree with each other, confirm your industry is accepted, and line up every person who must be verified. That hour prevents most of the delays that make remote onboarding feel arbitrary.
Common questions
Is a remote application faster than a branch one?
Sometimes much faster, and sometimes slower in a way you cannot influence. A clean application with consistent data can complete quickly. One that trips an automated check may sit in a queue with no visible progress, which is a real risk to weigh if you have a deadline.
Do I need a physical business address?
Providers generally want a real address for the business rather than a mail forwarding service alone, and some ask for evidence of it. Requirements vary, so ask before applying if your arrangement is unusual.
Will they check my personal credit?
Deposit account applications do not always involve a credit check, though screening against records of prior account misconduct is common. Any credit product attached to the account is a separate assessment with its own requirements.
What if the provider is not a bank?
Then ask which institution holds the money and whether the balance is a deposit, because the answer determines what protects it. Coverage exists at insured banks and insured credit unions with limits and conditions that depend on titling, and the FDIC and NCUA are the sources for the current rules.
The distinction between a bank account and a balance held by a payment provider is set out in where a balance actually sits, and what a branchless relationship changes more broadly is in banking without a branch.







