Money Transmission & Payments · October 31, 2026

What Banks Require From Money Services Businesses: U.S. Banking Readiness

Banks evaluate more than an MSB’s FinCEN registration. Learn about the licensing, AML, transaction flow, ownership, and operational documents that can support U.S. banking onboarding.

A retro-futuristic illustration of a friendly robot reviewing U.S. money services business banking requirements, surrounded by AML compliance documents, KYC verification checklists, risk assessments, transaction monitoring dashboards, and digital banking systems.

For a money services business (MSB), finding a banking partner can be as consequential as obtaining regulatory registration or state licenses. Banks may review an MSB’s ownership, products, licensing, compliance program, customer base, and movement of funds before deciding whether to establish an account relationship.

There is no universal “MSB-friendly bank” checklist that guarantees approval. Federal guidance calls for risk-based due diligence rather than treating every MSB as equally risky, while each bank makes its own commercial and risk decisions. A well-prepared application helps the bank understand the business and evaluate the relationship on its actual facts.

This guide explains what banks commonly examine, which requirements come from regulatory guidance, and how fintech and payment businesses can prepare a credible banking-readiness package.

1. Start by defining the banking relationship

Before assembling documents, identify exactly what the MSB is asking the bank to provide. Different arrangements create different operational and oversight questions:

  • Ordinary operating account: Accounts for the company’s own payroll, vendors, fees, and operating expenses.
  • Settlement and payment services: Accounts and payment rails used in connection with the movement, receipt, or disbursement of transaction funds.
  • Customer-funds or custodial arrangements: Structures in which customer balances, beneficial interests, reconciliations, and account titling require careful analysis.
  • Bank-led fintech program or sponsorship: A wider commercial arrangement through which a fintech helps deliver bank products or services, potentially requiring extensive third-party governance and monitoring.

An ordinary account-opening review is not the same as negotiating a sponsor-bank program. Nor does the existence of a banking relationship, by itself, exempt a nonbank company from otherwise applicable FinCEN obligations or state money transmission requirements.

2. Verify the MSB’s identity, registration, and licensing position

FinCEN and federal banking agencies identified baseline due-diligence steps for banks that open or maintain MSB accounts. Those steps include customer identification, confirmation of FinCEN registration when required, confirmation of applicable state licensing or agent status, and a basic BSA/AML risk assessment.

An MSB should be ready to present:

  • Entity and ownership records: Formation documents, employer identification number, principal place of business, ownership chart, control persons, and identifying information requested under the bank’s onboarding procedures.
  • FinCEN status: Evidence of registration if the business must register, or a clear explanation of why registration does not apply. FinCEN registration is not a federal operating license or regulatory endorsement.
  • State authorization map: Licenses held, jurisdictions served, application status, and relevant exemptions or authorized-delegate relationships, supported by documentation where appropriate.
  • Consistent activity description: A plain-language account of the products, entities, countries, customer segments, and specific role performed in transferring value.

The bank may ask for more evidence when the licensing position is complex. An exemption assertion should be tied to facts and applicable law, not offered as a generic statement that “we do not need any licenses.”

3. Demonstrate a functioning AML/CFT compliance program

A written policy is useful, but banks will also want to understand how a business manages actual money-laundering, terrorist-financing, fraud, and sanctions risks. The precise legal obligations depend on the MSB category, services, and transactions; the bank’s review will also reflect its own risk assessment.

Common areas of inquiry include:

  • Risk assessment: Identification of risks associated with customers, products, delivery methods, geography, and transaction activity; a description of how controls respond to those risks.
  • Governance and accountability: The designated compliance function, reporting lines, escalation procedures, management oversight, and relevant staffing or vendor arrangements.
  • Customer verification and due diligence: Procedures appropriate to the business’s applicable duties, including higher-risk customers, business customers, beneficial owners, and counterparties where relevant.
  • Transaction monitoring: Rules, review processes, alert disposition, investigation documentation, and the ability to identify unusual activity in expected transaction flows.
  • Reporting and recordkeeping: Controls for applicable Suspicious Activity Reports, Currency Transaction Reports, funds-transfer records, and other BSA obligations.
  • Training and independent review: Records of relevant employee training and independent testing as required by applicable rules and proportionate to the business’s operations.
  • Sanctions controls: Risk-appropriate screening, escalation, blocking or rejecting processes where applicable, and procedures to address sanctions matches.

The purpose is not to prove that every MSB uses the same procedures. It is to show that the company understands its legal obligations, implements appropriate controls, and can provide evidence that the controls operate.

4. Explain customers, products, jurisdictions, and transaction activity

Banks evaluate the expected behavior of an account in order to detect activity inconsistent with its stated purpose. An MSB that can describe its transaction profile accurately is better positioned to answer onboarding questions and avoid unnecessary follow-up.

Prepare a concise operating profile covering:

  • Products and channels, including remittances, foreign exchange, stored value, bill payments, merchant payments, or virtual asset-related services where applicable.
  • Customer segments, such as consumers, merchants, small businesses, platforms, or financial institutions, and how those customers are onboarded.
  • Countries and U.S. states served; material corridors, counterparties, and any heightened geographic or sanctions exposure.
  • Expected monthly transaction count and value, average and maximum ticket sizes, funding methods, cash exposure, refunds, and transaction peaks.
  • Source of funds and expected destinations, including any third-party processors, agents, liquidity providers, or settlement partners.

Avoid unsupported transaction forecasts. Banks may compare initial projections with the account’s actual activity after opening, so estimates should be reasonable and updated when the business materially changes.

5. Provide a transparent flow-of-funds explanation

For a payment or remittance business, the flow-of-funds narrative is often one of the most useful diligence materials. It should answer: who pays, who receives value, which legal entity controls the funds at each stage, where funds are held, and when the customer’s payment obligation is discharged.

A practical written explanation or separate diagram should identify:

  • Each participating entity: customer, MSB, bank, processor, agent, correspondent, and beneficiary.
  • The accounts used at each stage, including whether balances are proprietary, settlement-related, or customer-associated.
  • When funds are accepted, credited, transmitted, converted, held, or returned; who can initiate each action.
  • Reconciliation frequency, segregation or safeguarding measures where required, and treatment of exceptions, disputes, and failed transfers.
  • How the company monitors the end-to-end transaction when multiple providers perform parts of the service.

A bank may also request sample transactions, contracts, account statements, processor information, or a controlled walkthrough. Disclose the full arrangement; omitting a material intermediary can undermine confidence in the risk assessment.

6. Show financial capacity and operational maturity

Banks may review whether the business is sufficiently funded and operationally prepared for the proposed service. The review is not identical to a state regulator’s financial examination, and no single universal minimum balance applies to all MSB banking relationships.

Depending on the bank and proposed services, the evidence may include:

  • Recent financial statements, opening balance sheet, capitalization sources, runway, and realistic forecasts.
  • State-mandated surety bonds, minimum net worth or permissible investment documentation where applicable.
  • Policies for access controls, cybersecurity, business continuity, incident response, and vendor oversight.
  • Payment operations procedures, daily reconciliations, exception handling, complaints, and escalation contacts.
  • Management biographies, relevant operating experience, organizational responsibilities, and third-party service agreements.

Pre-launch businesses may not have transaction history or historical audit results. They should identify which controls are implemented, which are being tested, and what remains to be completed-rather than presenting draft procedures as fully operational.

7. Expect additional diligence for sponsor-bank and embedded-finance programs

When a bank is asked to support a fintech program rather than provide a conventional account, the relationship can require materially greater diligence. The 2023 interagency third-party risk management guidance addresses due diligence, contracts, ongoing monitoring, and termination. A 2024 joint statement discusses risks where third parties help deliver bank deposit products and services; it did not establish new supervisory expectations.

A prospective program partner may need to document:

  • The proposed product, customer experience, contractual parties, and regulatory responsibilities of the bank and fintech.
  • Allocation of onboarding, monitoring, sanctions, complaint handling, reporting, reconciliations, information security, and customer disclosures.
  • Data access, audit rights, management reporting, service levels, subcontractor controls, and escalation responsibilities.
  • Operational resiliency, funds and ledger reconciliation, incident management, business continuity, and an orderly wind-down plan.

Importantly, bank oversight does not erase the fintech’s own legal obligations. A sponsorship agreement must match the actual service model and applicable law; a generic “covered by the bank” statement is not an adequate licensing analysis.

8. Digital assets and cross-border activity require tailored explanations

A digital asset business or cross-border remittance provider may face additional questions about custody and control, exchange and conversion partners, wallet or counterparty screening, foreign corridors, settlement methods, and exposure to fraud or sanctions. The underlying diligence remains risk-based; federal guidance does not require banks to reject an entire category of MSB customer solely because of its label.

Where a virtual asset or stablecoin is involved, distinguish the company’s actual function-software developer, exchanger, custodian, issuer, payment facilitator, or agent-rather than treating every crypto-related business as performing the same regulated activity. Separate analyses may be needed under digital asset, banking, and money transmission rules.

9. Practical MSB banking-readiness checklist

Before approaching banks, assemble one indexed package that is internally consistent and easy to maintain:

  1. A one-page business and product overview identifying the entity requesting services.
  2. A corporate structure chart, ownership records, and management identification information.
  3. FinCEN registration evidence or documented applicability explanation.
  4. A state-by-state license, exemption, or authorized-delegate status schedule.
  5. An AML/CFT risk assessment, current policies, compliance ownership, and relevant testing or training evidence.
  6. Sanctions and fraud control descriptions, including monitoring and escalation workflows.
  7. An end-to-end flow-of-funds narrative with all banks, processors, agents, and counterparties identified.
  8. An expected activity profile covering volumes, value, funding methods, corridors, and customer types.
  9. Financial statements, capital and funding sources, and operating forecasts proportionate to the business stage.
  10. Material third-party contracts or summaries, security controls, reconciliations, and incident procedures.
  11. A clear explanation of the banking services requested, account purposes, and launch timeline.
  12. A named contact who can respond consistently to compliance, operations, legal, and commercial questions.

This is a preparation checklist, not a claim that every bank is legally required to collect each item. A bank may request fewer or more documents based on its assessment of the specific relationship.

10. Why MSB banking applications get delayed or declined

Many delays are avoidable, although some decisions reflect a bank’s products, appetite, policies, or business priorities rather than a defect in the applicant.

  • Unclear licensing position: The company cannot reconcile its activities and geographic footprint with its registrations, licenses, or claimed exemptions.
  • Incomplete funds-flow disclosure: The bank learns late in the process about an additional intermediary, high-risk corridor, or customer-funds arrangement.
  • Generic compliance documents: Policies describe controls that do not match actual products, vendors, monitoring capabilities, or staff responsibilities.
  • Inconsistent projections: Expected flows differ substantially across the business plan, application, bank questionnaire, and financial model.
  • Unresolved third-party dependencies: Important processors, delegates, banking partners, or vendors lack a clear role or documented oversight.
  • Premature application: A pre-launch entity seeks sophisticated settlement or sponsorship services before its operating structure and control framework are defined.

A rejection does not automatically mean the business is unlawful or unbankable. The appropriate next step is to identify whether the issue is legal status, documentation quality, product fit, operational readiness, or the bank’s discretionary risk decision.

11. A practical onboarding sequence for fintech and MSB founders

Phase 1 - Regulatory and product assessment

Classify the business, determine federal and state obligations, identify the required banking products, and select institutions whose capabilities reasonably match the business model.

Phase 2 - Documentation and control readiness

Align corporate records, regulatory status, financials, AML/CFT procedures, projected activity, and flow-of-funds materials. Resolve internal inconsistencies before submitting the package.

Phase 3 - Bank diligence and program negotiation

Respond to bank questions with evidence, not general assurances. For a bank-led fintech program, negotiate responsibilities, monitoring, controls, data rights, contingency plans, and commercial terms appropriate to the arrangement.

Phase 4 - Launch and continuing relationship management

Maintain the agreed controls, monitor activity against stated expectations, update licensing and ownership information, and communicate material changes to products, customers, jurisdictions, or transaction volumes as appropriate.

12. Frequently asked questions

Is FinCEN MSB registration enough to open a business bank account?

Not necessarily. Registration may be one part of the bank’s review when required, but the bank may also assess state authorization, the business model, ownership, AML/CFT controls, expected activity, and its own commercial requirements. Registration does not guarantee an account.

Must an MSB hold a money transmitter license in every U.S. state before a bank will work with it?

Not categorically. Licensing depends on the business’s activities and the states involved. The bank may seek evidence that the company is appropriately licensed, exempt, or otherwise authorized for its actual footprint.

Can a newly formed MSB obtain banking without transaction history?

It may be possible, but the bank will need other reliable evidence: a clear business plan, funding sources, responsible leadership, operating procedures, credible projections, and a realistic readiness timeline. Availability varies by institution and service.

Does every bank require a separate independent AML audit before onboarding?

No uniform federal onboarding rule requires a newly established MSB to provide the same audit package to every bank. Independent review or testing requirements can arise under applicable MSB rules, and banks may request evidence of such testing in light of the relationship’s risk and maturity.

Are cryptocurrency or international remittance businesses automatically excluded from banking?

No blanket federal prohibition applies solely because a business is an MSB, has international flows, or uses digital assets. However, individual banks may have restrictions, heightened diligence, or decisions based on risk appetite and the specific services requested.

Does a sponsor bank remove the need for the fintech’s own licenses?

Not automatically. The legal treatment depends on the activities and contracts, the role of each party, and the jurisdictions involved. Bank sponsorship, authorized delegation, and direct licensing are distinct structures that require separate analysis.

How Fidamont helps with MSB banking readiness

Fidamont supports money services businesses and fintech operators in preparing the regulatory and operational materials banks need to evaluate a proposed relationship. Services may include:

  • FinCEN and state money transmission registration or licensing applicability assessments.
  • Banking-readiness reviews and identification of gaps in applications, supporting documents, and operating models.
  • AML/CFT program design, control documentation, and remediation planning.
  • Flow-of-funds mapping, third-party role analysis, and preparation for bank diligence conversations.
  • Regulatory and operational preparation for bank partnerships and payment programs.

Planning to open an MSB account or launch a bank-supported fintech product? A structured readiness assessment can help clarify what to prepare before approaching prospective financial institutions. Banking approval and commercial terms remain within each bank’s discretion.

This article is general information about regulatory requirements, current as of its publication date. It is not legal advice and does not create a client relationship. Fidamont is not a law firm. For advice on your specific situation, consult counsel.

← All Insights

Have a regulatory question?

Tell us what you're building and which states you're looking at.

Schedule a Call