The Banking Problem: Why It Is Harder Than the License
You have your money transmitter license. You have your compliance program. You have your audit ready. What you may not have, the moment that license is issued, is a bank account.
This reality shocks most first-time licensees. The licensing process—though it can be brutal—follows clear rules. You know what regulators want. You build it. You wait. You get the approval. But banking access is different. It operates in a parallel system where no official rulebook exists, where decisions are made on criteria you cannot fully predict, and where a bank that approved you last month can terminate you next week without cause.
I have seen companies with impeccable licenses, zero compliance violations, and excellent financial profiles get rejected by bank after bank. I have seen companies with marginal compliance frameworks and moderately questionable practices maintain banking relationships for years. The licensing problem is surmountable. The banking problem is structural.
The Reality of De-Risking and Its Impact on MSBs
De-risking is the financial industry's response to regulatory pressure and reputational risk. It works like this: a bank calculates that serving a particular customer segment—even legal customers in regulated segments—costs more in compliance, in regulatory scrutiny, and in reputational risk than that customer generates in revenue and profit. The bank then exits that segment.
Money transmitter businesses fall into a de-risking category that became especially pronounced after 2015. Banks looked at MSBs and saw three simultaneous problems. First, MSBs by definition handle customer funds. That triggers deposit insurance considerations, reserve requirements, and heightened regulatory examination. Second, MSBs create exposure to sanctions violations, money laundering, and terrorist financing if the MSB itself is negligent or complicit. Third, banks cannot easily monitor what the MSB is actually doing with customer funds beyond the bank's own account. If the MSB's customer is sending money to Iran, the bank technically shouldn't process it. But if the MSB's platform doesn't properly screen that customer, the bank's transaction rails could be used for sanctions violations.
So a bank faces a choice. It can serve MSBs by implementing intense due diligence, continuous transaction monitoring, and frequent examination of the MSB's own customer base. This costs money. Or it can simply decline to serve MSBs at all. For most large banks, this calculation has resolved in favor of exit.
The impact on MSBs is material. A company that cannot maintain banking access cannot operate. An MSB without a bank account cannot move money. It cannot settle with its agents. It cannot pay its expenses. It cannot exist as a functioning business. So the licensing achievement, while real, is incomplete without banking.
Why Banks Close MSB Accounts
Banks close MSB accounts for reasons that range from explicit policy decisions to gradual relationship erosion. Understanding the difference matters, because your response differs depending on the cause.
Some banks have simply decided they do not serve money transmitters anymore, period. This is not personal. This is category-level de-risking. If your bank implements this policy, nothing you do will retain the account. The bank will give you sixty to ninety days notice and recommend you find alternative banking. There is no escalation path. This happens regularly. I had a client with five years of clean compliance history and fewer than fifty monthly transactions get exited from a regional bank because the bank decided to close all its payment services division, of which MSBs were a small part.
More commonly, banks close MSB accounts because of specific transaction or customer concerns. A bank sees a pattern of transactions to high-risk jurisdictions. A customer gets flagged by external intelligence. A transaction size or frequency pattern breaks the bank's risk appetite. The bank may not tell you exactly why. It will cite risk management, regulatory compliance, or business strategy. But the underlying reason is usually transactional.
Banks also close accounts because of compliance deficiencies they discover during the onboarding process. An MSB represents itself as having certain controls. The bank's due diligence uncovers that those controls either do not exist or are not functioning. The bank then faces a choice between accepting higher risk or exiting. Most exit.
Some banks close MSB accounts because the relationship became unprofitable or administratively burdensome relative to deposit size. An MSB generates $50,000 in annual monthly flows, which amounts to maybe $2,000 in annual revenue for the bank. But the MSB requires quarterly compliance reviews, special transaction monitoring, and regular officer calls. After two years of this, the bank reassesses and decides the economics do not work. Exit.
And some banks close accounts because of pressure from their own regulators. A bank gets a compliance directive suggesting that its monitoring of MSBs is inadequate. Rather than improving the monitoring, the bank simply exits the segment. This is rational from the bank's perspective.
The Gap Between "Licensed" and "Bankable"
Licensing and banking access are independent achievements. A state will grant you a money transmitter license if you meet the licensing criteria. A bank will grant you a deposit account if you meet the bank's criteria. These are not the same criteria, and they are not equivalent.
A state license requires you to demonstrate net worth, operational controls, compliance frameworks, and a clean background. A bank requires you to demonstrate low operational risk, strong transaction profiles, clean customer bases, and manageable compliance overhead.
An MSB can be fully licensed in every state and unable to get a single bank account. I have seen this happen. A company invests $400,000 to build a licensing application package, goes through multistate licensing, emerges with twelve active licenses—and then cannot find a bank that will serve it, because the company's business model involves high-velocity customer flows to specific high-risk jurisdictions, and the bank simply cannot accept that risk profile regardless of the company's licensing status.
Conversely, an MSB can operate with banking relationships but still be working on licensing. Many fintechs operate in this posture for months or even years, serving customers through banking relationships while they build out their licensing applications. The bank accepts the higher risk because the company either has other relationships that justify the bank's patience, or the company accepts a higher fee structure that compensates the bank for its incremental risk.
The gap between licensed and bankable is real, and it is not obvious until you start trying to get banking. Plan for this. Budget for it. Expect it. Treat banking access as a separate workstream from licensing, with its own timeline, its own requirements, and its own relationship management process.
The Cost of Banking Instability
Banking instability is expensive. When your bank relationship is fragile or threatened, you have several direct costs. You may pay higher fees to retain the relationship. You may need to hire a banking consultant to manage the relationship. You may need to reduce transaction volumes or reorient your business model to meet the bank's risk appetite. You may need to diversify into multiple banking relationships, each of which requires its own onboarding, its own compliance infrastructure, and its own management overhead.
But the indirect costs are steeper. Banking instability creates operational uncertainty. You cannot reliably plan customer service levels because you cannot guarantee settlement velocity. You cannot build features or expand geographic reach because you cannot be certain your banking will support it. You cannot raise capital easily because investors see banking as a fundamental operational risk. You cannot hire confidently because your cost structure is unstable.
I have seen companies with $5 million in monthly volume maintain three separate banking relationships just to hedge against the risk that any one bank might exit. The cost of maintaining three relationships—compliance teams, dedicated contact relationships, different onboarding procedures, fee negotiations across multiple partners—is substantial. But the cost of having a single banking relationship terminate unexpectedly is worse, because it can shut the company down entirely.
A company I worked with had a single bank relationship for three years. The company was profitable, in compliance, and stable. The bank decided to exit payment services. The company got ninety days notice. In those ninety days, the company had to find a new primary bank, migrate all customer settlement processes to the new bank's infrastructure, update all customer-facing materials and documentation, and reconfigure its operational processes. The company managed to do this, but just barely, and it cost $200,000 in direct consulting fees plus significant management time. If the company had not successfully transitioned within the window, it would have had to shut down operations.
Plan for banking instability. Budget for it. Build redundancy into your banking architecture from day one, even if you only use one bank initially. The cost of doing this is a small fraction of the cost of being forced to transition under deadline pressure.
How Regulators Inadvertently Created the Banking Problem
The banking problem exists because of well-intentioned regulatory decisions that have created misaligned incentives across the financial system.
Regulators decided that banks had insufficient visibility into transaction patterns and customer bases of money transmitters. This was a correct assessment. A bank processing wire transfers for an MSB has limited transparency into who the MSB's actual customers are, what they are doing, and whether they pose sanctions or AML risk. To address this, regulators imposed increasing compliance obligations on banks that serve higher-risk customer segments. This includes MSBs.
The compliance obligations are reasonable in isolation. They require banks to conduct enhanced due diligence on MSBs, conduct periodic transaction reviews, maintain documentation, and file suspicious activity reports. These are standard requirements.
But the compliance obligations, applied in the context of lower profit margins and higher regulatory oversight, created a calculation for banks that looked like this: "If I serve MSBs, I have to assign compliance staff to monitor them. I have to conduct enhanced due diligence. I have to defend my decisions to regulators. The regulatory scrutiny adds risk to the rest of my business, because regulators will ask why I am doing this. The compliance work costs money. The profit from MSB accounts is relatively low because the account sizes are usually smaller, the transaction volumes are moderate, and the price competition is fierce. Therefore, I should not serve this segment at all."
This is a rational response to the regulatory environment. But it is not the response regulators intended. Regulators wanted better monitoring of MSBs, not the disappearance of MSB banking relationships. Yet the regulatory pressure applied to banks created an exit incentive that was stronger than the incentive to improve compliance.
Regulators have belatedly recognized this problem and in some cases reversed course. Some regulatory guidance now explicitly recognizes that de-risking is problematic and that banks should not reflexively exit segments. But the damage is done. The banking problem exists because the regulatory system made it economically rational for banks to stop serving MSBs.
What Banks Actually Evaluate When Onboarding an MSB
Banks evaluate MSBs across multiple dimensions, but they rarely weight these dimensions the same way or apply them consistently. Understanding what banks are looking for—and what they are implicitly avoiding—is essential to getting and keeping banking relationships.
Banks evaluate the MSB's ownership and management. They want to know that the company is legitimate, that the owners are not in the sanctions lists or watch lists, and that the management team has relevant financial services experience. A bank is much more comfortable with an MSB run by someone with five years of operational experience at another licensed MSB than with an MSB run by a startup founder who is getting into payments for the first time. This is not because either person is necessarily incapable, but because the experienced person has demonstrated survivability in the industry.
Banks evaluate the MSB's business model and customer base. They want to understand what the MSB actually does. Does it serve consumers or businesses? Does it move money domestically or internationally? What are the transaction sizes? What are the geographies? What are the customer types? Banks have implicit risk appetites for different customer segments. A bank might be comfortable with a domestic money transmitter serving small transfers to Latin America, but uncomfortable with a money transmitter serving cross-border transfers to the Middle East, regardless of compliance controls.
Banks evaluate the MSB's transaction profiles. They want to understand the actual flow of money through the MSB's system. What percentage of transactions are inbound versus outbound? What are the typical transaction sizes? What are the destination geographies? What are the velocity patterns? Are transactions concentrated in certain time periods or geographies? A bank will model what it expects to see based on the MSB's stated business model, and then it will monitor actual transactions against that model.
Banks evaluate the MSB's compliance framework. They want to know that the company has controls in place to prevent sanctions violations, money laundering, and terrorist financing. They want to see policies, procedures, training, audits, and SAR filings. But they also want to see that the compliance framework is actually functioning, not just documented. A bank will review a sample of transactions and customer files to determine whether the MSB's compliance controls are real or merely theoretical.
Banks evaluate the MSB's financial condition. They want to know that the company is solvent and profitable. They want to see tax returns, financial statements, and projections. They want to understand whether the company is stable or whether it is rapidly burning through capital. A company with strong compliance controls but deteriorating financials will look risky to a bank, because a struggling company might cut corners or take shortcuts.
Banks evaluate the MSB's regulatory history. They want to know whether the company has ever been examined by regulators, whether it has ever received enforcement actions, and whether it has ever had licenses suspended or revoked. A company that has never been examined is less trustworthy than a company that has been examined and passed, because the bank cannot assess the company's actual operational reality.
And banks evaluate the relationship economics. They want to know whether the account will be profitable for the bank and whether the relationship will generate fee income that justifies the compliance overhead. An MSB that promises to generate $100,000 in annual monthly flows but requires a dedicated compliance officer to monitor is less attractive than an MSB that promises $50,000 in monthly flows but requires minimal oversight.
The Difference Between What Banks Say and What They Do
Banks have official policies about serving money transmitters. These policies usually state something like: "We serve properly licensed money transmitters that meet our risk criteria."
What banks actually do is apply those risk criteria inconsistently and sometimes reflexively exclude MSBs because they do not want to go through the effort of evaluating them properly.
Many banks will tell you that they do not serve money transmitters at all. When you press them, it turns out they mean they do not serve certain types of money transmitters—typically crypto-adjacent MSBs or MSBs with higher-risk geographies. But they will serve domestic-focused MSBs under certain conditions.
Some banks will state that they require MSBs to maintain minimum balances. These minimums vary wildly—from $50,000 to $500,000—and they are rarely documented in the bank's official pricing. The bank discovers the requirement during onboarding or applies it retroactively.
Other banks will state that they do not serve MSBs in certain categories or that they do not serve startups. What they actually mean is they do not want the compliance overhead of evaluating startups, so they use the startup status as a proxy for risk.
Banks also misrepresent their transaction monitoring capabilities. An MSB will ask a bank: "Can you monitor my transaction flows to ensure they comply with sanctions?" The bank will say yes. What the bank actually can do is apply standard transaction screening and flag high-risk jurisdictions. What the bank cannot do is understand whether a transaction is legitimate within the context of the MSB's business model. A $50,000 transfer to Pakistan might be normal for a money transmitter serving remittances to Pakistan, or it might be completely anomalous for a money transmitter serving domestic payments. The bank's screening cannot distinguish this. So when the bank says it can monitor your transactions, understand that it means it will screen against sanctions lists and watch lists, not that it will intelligently monitor your actual business flows.
The difference between what banks say and do matters because it means you cannot trust bank statements about their appetite for MSBs. You need to test the market yourself, and you need to understand that rejection from one bank does not mean you are unbankable—it means you are not what that bank wants right now.