TLDR
- A stablecoin vendor operating legally in the US does not automatically cover your platform’s compliance obligations. The licenses that matter depend on the activity, not just the vendor’s existence.
- Money transmitter licenses, the GENIUS Act’s federal payment stablecoin framework, and FinCEN registration are the three license categories every platform evaluator must verify before signing a vendor contract.
- License gaps at the infrastructure layer flow upstream. If your vendor cannot transmit funds in Texas, your users in Texas cannot transact, and you carry the regulatory exposure for the gap.
- The safest shortlisting approach is activity-first: map what your platform does, then match each activity to the license required, then verify whether your shortlisted vendor holds it.
- The GENIUS Act, signed into law in 2025, created a federal licensing track for payment stablecoin issuers, but it does not replace state money transmitter requirements for non-issuers transmitting stablecoin value.
Stablecoin infrastructure licenses your provider needs include state money transmitter licenses (MTLs) for all states where users transact, FinCEN registration as a money services business, and, for issuers, a federal payment stablecoin issuer license or qualifying state trust charter under the GENIUS Act. Platforms that transmit stablecoin value without holding or delegating all required licenses face direct regulatory exposure, regardless of their vendor’s live status in the US market.
Why “Live in the US” Tells You Almost Nothing About a Vendor’s License Coverage
A stablecoin infrastructure vendor can be fully operational, have real enterprise customers, and still hold zero state money transmitter licenses. That happens because the regulatory question is not whether a company is licensed somewhere. It is whether the company is licensed for the specific activity, in the specific state, for the specific user the platform is onboarding.
Some infrastructure providers operate under a bank partnership structure, where the sponsor bank holds the licenses and the vendor rides the bank’s charter. Others hold their own MTLs across 40-plus states. A few operate under a trust company charter, which carries different permissions than an MTL. These are not equivalent. A vendor relying on a bank partner may lose that coverage if the partnership terms change, a dynamic well-documented in the 2026 BaaS consolidation wave.
Platforms that assume vendor live status equals full coverage are taking on undisclosed regulatory liability. That liability does not stay theoretical. State regulators can issue cease-and-desist orders against platforms whose vendors lacked jurisdiction-specific authorization, even when the platform itself was not the licensed entity.
What Is the GENIUS Act and What Licenses Does It Actually Create?
The Guiding and Establishing National Innovation for US Stablecoins Act, signed in 2025, established the first federal licensing framework specifically for payment stablecoin issuers. It created two primary authorization pathways: a federal charter issued by the Office of the Comptroller of the Currency (OCC) for non-bank payment stablecoin issuers, and a state-level pathway for stablecoin issuers whose outstanding stablecoin value stays below the $10 billion threshold set in the statute.
The OCC acted quickly. In mid-2026, the agency approved national trust bank charters for Bastion, Catena, and Agora on a single day, as covered in detail in the OCC digital-asset trust bank charter announcement. Those charters allow the holders to issue and custody digital assets under federal supervision without a full commercial bank charter. That is a meaningfully different permission set than an MTL.
What the GENIUS Act does not do is replace state money transmitter licenses for vendors that transmit stablecoin value but do not issue it. A stablecoin payment API that moves USDC between wallets is performing a money transmission activity in most state definitions. The GENIUS Act’s federal issuer license does not cover that activity unless the vendor is also the issuer and the transmission falls within the scope of that license. Most infrastructure providers are not issuers. They need MTLs.
The Federal Reserve’s September 2026 proposed rules under the GENIUS Act clarified reserve, capital, and supervisory requirements for federally licensed payment stablecoin issuers. Those rules are in the proposal stage as of October 2026, which means the compliance picture for federal issuers is still moving. Platforms evaluating issuance-layer vendors should track the Fed’s GENIUS Act reserve rules specifically, because reserve composition requirements will affect which issuers can scale and which cannot.
Does a Stablecoin Provider Need a Money Transmitter License?
Yes, in most cases. If a vendor moves stablecoin value on behalf of a third party from one wallet or account to another, that activity fits the definition of money transmission under the Bank Secrecy Act and under most state money transmission statutes. FinCEN’s 2019 guidance on convertible virtual currency made clear that exchanging or transmitting value denominated in cryptocurrency or stablecoin requires registration as a money services business (MSB) at the federal level.
State-level MTL requirements are separate from federal MSB registration and more operationally demanding. Each state sets its own application requirements, surety bond minimums, net worth thresholds, and examination cycles. As of October 2026, money transmitter license costs vary significantly by state, with some states requiring surety bonds that exceed $1 million and net worth requirements above $500,000 before an application is considered complete.
Two states matter disproportionately in vendor due diligence: New York and California. New York’s BitLicense, administered by the Department of Financial Services (NYDFS), is a separate virtual currency business activity license required in addition to, or sometimes instead of, a standard MTL for companies engaged in digital asset activity involving New York residents. California’s Money Transmission Act covers stablecoin transmission and the California Department of Financial Protection and Innovation (DFPI) has actively enforced it. A vendor without NYDFS authorization and without California MTA coverage cannot legally serve your New York or California users.
The FintechSpecs License-by-Activity Matrix for Stablecoin Infrastructure
The most reliable way to audit a vendor shortlist is to start with what your platform does, not with what the vendor says it holds. The following matrix maps common platform activities to the license or registration the infrastructure layer must hold to support them legally in the US.
| Platform Activity | Required at Vendor Level | Notes |
|---|---|---|
| Transmitting stablecoin between user wallets | MTL in each user’s state + FinCEN MSB registration | Covers USDC, USDT, and other dollar-pegged tokens; New York also requires BitLicense or NYDFS approval |
| Issuing a branded stablecoin or digital dollar | GENIUS Act federal issuer license (OCC) or qualifying state trust charter, plus FinCEN MSB registration | Below $10B outstanding: state pathway permitted; above $10B: federal charter required under GENIUS Act |
| Fiat on-ramp / off-ramp (USD to stablecoin) | MTL in each user’s state + FinCEN MSB registration; California DFPI license | Conversion activity is typically treated as currency exchange and money transmission together |
| Stablecoin custody (holding keys on behalf of users) | State trust charter or qualified custodian status; NYDFS approval for NY users | OCC national trust charter also qualifies; some states permit under existing MTL |
| Cross-border stablecoin payouts | US MTL coverage + FinCEN MSB + receiving country’s payment license | Treasury’s OFAC sanctions screening required regardless of license type |
| Stablecoin card spending (debit/prepaid) | MTL + card network membership or sponsorship + state-specific prepaid card licenses | Visa and Mastercard network rules layer on top of regulatory requirements |
| Stablecoin-denominated lending | State lending license in each user’s state; possibly federal bank charter | Distinct from transmission licensing; CFPB oversight may apply depending on consumer vs. business use |
This matrix applies to the infrastructure provider, not to your platform directly. Your own licensing obligations depend on how your platform is classified relative to the vendor’s activity, which is a separate legal analysis. What the matrix tells you is the minimum the vendor must hold for you to build on them without absorbing unmitigated regulatory risk.
What the FintechSpecs Vendor License Stress Test Actually Checks
Generic vendor due diligence checklists ask whether a vendor is licensed. That is the wrong question. The FintechSpecs Vendor License Stress Test is a four-point verification sequence designed for platforms actively shortlisting stablecoin infrastructure providers. It moves from state coverage to federal registration to charter type to gap ownership, in that order, because each step reveals a different category of risk.
Step 1: State Coverage Map Verification
Ask the vendor for their current MTL registry list and cross-reference it against the states where your users are located today and in your 12-month growth plan. Do not accept a verbal assurance. Request the actual license numbers and verify them against each state’s public licensing database. Most state banking regulators publish these online. If a vendor holds 38 state MTLs but not New York, California, or Texas, that gap covers three of the five most populous US states.
Step 2: Federal MSB Registration Confirmation
FinCEN’s MSB Registration database is publicly searchable. Any company transmitting stablecoin value in the US must register as a money services business. Search the vendor’s legal entity name directly. If they are not in the database, they are operating without federal registration, which is an independent violation regardless of state license status.
Step 3: Charter Type and Activity Scope Alignment
Verify that the license type the vendor holds actually covers the activity you are building. A trust company charter permits custody but may not permit transmission. An MTL permits transmission but not custody. A BitLicense in New York permits virtual currency business activity but has its own scope definitions. Charter type determines activity scope, and activity scope determines whether your specific use case is covered.
Step 4: Gap Ownership Clause in the Contract
Request the vendor’s standard service agreement and look specifically for language that assigns responsibility when a license is suspended, revoked, or not yet obtained in a new state. Responsible vendors write explicit gap-coverage provisions or service limitation clauses that define what happens if their license lapses in a jurisdiction. If no such clause exists, the contract is silent on who absorbs the regulatory risk when a gap appears. That silence transfers the risk to you by default.
Which License Gaps Are Actually Likely to Surface in Vendor Due Diligence?
Based on how the stablecoin infrastructure market has developed, three gap patterns appear consistently in vendor evaluations.
The first is the New York gap. NYDFS licensing is the most demanding state-level process for digital asset companies, typically requiring 12 to 24 months for a full BitLicense approval. Many infrastructure providers that launched after 2021 have not completed the NYDFS process. They serve non-New York users legally while New York remains blocked. If your platform has users in New York, this is an immediate disqualifying gap unless the vendor can demonstrate a clear timeline to approval or a bank partnership that covers New York specifically.
The second gap pattern is the bank partnership dependency risk. Some vendors operate entirely under a sponsor bank’s charter rather than holding their own MTLs. This structure can work, but it creates a single point of failure. If the sponsor bank exits the stablecoin space, restricts the partnership scope, or faces its own regulatory action, the vendor’s license coverage can disappear overnight with limited contractual remedies for your platform.
The third gap is the custody-transmission boundary confusion. Vendors sometimes present a single license as covering both custody and transmission. In most states and under most regulatory frameworks, these are distinct activities requiring distinct authorizations. A vendor that conflates them in a sales conversation is either misinformed about their own license scope or is not being precise. Either way, verify independently.
How to Read a Vendor’s License Disclosure in Practice
Most stablecoin infrastructure providers publish some form of legal or compliance disclosure on their website. The quality of that disclosure is itself a due diligence signal. A provider that lists specific license numbers, the issuing state, the license type, and the expiration date for each is demonstrating operational maturity. A provider whose compliance page says “licensed in required jurisdictions” without specifics is giving you a marketing statement, not a compliance disclosure.
For providers building on the stablecoin layer specifically, the leading stablecoin infrastructure providers each take different structural approaches to licensing: some hold their own MTL stacks, others operate through bank partnerships, and a smaller number have pursued OCC trust charters. Those structural differences are not apparent from product demos. They only surface in legal disclosure review.
A useful comparison point: established players like Zero Hash and Bridge (now part of Stripe) both publish compliance documentation that includes license types by state, as of their publicly accessible legal pages at the time of writing. That level of disclosure sets a reasonable baseline for what a mature vendor should provide. If a vendor on your shortlist provides less transparency than that baseline, treat it as a negotiation point before any contract is signed.
GENIUS Act Licensing Requirements: What Platforms Evaluating Issuance Vendors Need to Verify
If your platform is evaluating a vendor for stablecoin issuance, meaning the vendor would create and manage a dollar-pegged token on your behalf or for your users, the GENIUS Act licensing requirements are the primary filter.
Under the GENIUS Act, a vendor issuing a payment stablecoin with less than $10 billion outstanding can operate under a qualifying state trust charter with a state regulatory approval. Above that threshold, a federal OCC charter is required. For early-stage platforms, the $10 billion ceiling is not immediately relevant. What matters is whether the vendor holds a qualifying state charter from a regulator that has issued specific stablecoin guidance, rather than relying on a general trust charter that predates the stablecoin regulatory framework.
The GENIUS Act also imposes reserve requirements on payment stablecoin issuers: assets backing the stablecoin must be held in a defined set of high-quality liquid assets, with specific composition rules that the Fed’s September 2026 proposed rules are still clarifying. A vendor that cannot demonstrate reserve compliance cannot be a compliant issuance partner post-GENIUS Act, regardless of what their charter says. When reviewing issuance vendors, ask specifically for their reserve attestation process and whether they engage a third-party auditor.
For platforms building out a stablecoin issuance program, the leading stablecoin issuance platforms vary significantly in how they approach GENIUS Act alignment, reserve structure, and charter type. That variation is material to your vendor choice.
How Does This Affect Stablecoin-as-a-Service Vendor Selection?
The practical effect on vendor selection is that license coverage should become a hard filter before any technical evaluation. Most platforms run vendor selection the wrong way: they assess the API first, negotiate the commercial terms, and then ask legal to review the license coverage at the contract stage. By that point, there is organizational momentum behind the vendor, legal faces pressure to approve, and gaps get papered over with indemnification language that does not actually solve the regulatory problem.
Running the FintechSpecs Vendor License Stress Test before the API demo reverses that sequence. It eliminates vendors with structural license gaps before anyone builds a preference for their product. The 10 critical mistakes when choosing fintech infrastructure include exactly this pattern of delaying compliance review until after vendor preference is established, a mistake with outsized downstream costs in the stablecoin context specifically because regulatory exposure compounds with user volume.
For a broader framework on vendor evaluation before you sign, the 7-point fintech vendor buyer framework covers the full due diligence sequence, of which licensing is one layer. In the stablecoin context, licensing carries more weight than any other single factor because no API quality compensates for geographic coverage gaps that block user transactions.
What Questions Should You Ask a Stablecoin Provider During Due Diligence?
The following questions are designed to surface license gaps that vendor sales teams do not volunteer. Each question targets a specific risk category from the matrix above.
- Can you provide your current MTL registry by state, with license numbers and expiration dates, as of today?
- Are you registered with FinCEN as a money services business? What is your legal entity registration number?
- Do you hold a New York BitLicense or NYDFS virtual currency business activity approval? If not, how do you handle New York users?
- Does your license coverage extend to the specific activities we are building: transmission, custody, on-ramp/off-ramp, or issuance?
- Are your licenses held directly by your entity, or are they held by a bank or trust partner? If the latter, what happens to our service if that partnership ends?
- How do you handle new state license requirements when we expand to a new geography?
- What clause in your standard agreement addresses service limitation or coverage gaps when a license lapses or is not yet obtained?
- For issuance: are you GENIUS Act compliant today? Who holds custody of your reserve assets, and what is your attestation schedule?
A vendor that answers all eight questions with specifics and documentation is a vendor operating at the maturity level required for enterprise platform use. A vendor that deflects, provides general statements, or routes you to legal review for basic license questions is signaling an internal compliance function that has not kept pace with the product.
Frequently Asked Questions
Does my platform need its own money transmitter license if our stablecoin vendor holds one?
It depends on how your platform is structured relative to the vendor’s activity. If the vendor is the direct transmitter of funds and your platform only initiates instructions, the vendor’s MTL typically covers the transmission. If your platform receives, holds, or controls user funds at any point before passing them to the vendor, that activity may itself require an MTL in the states where your users are located. Your legal counsel needs to analyze the transaction flow, not just the contract structure.
What is the GENIUS Act licensing requirement for a stablecoin infrastructure provider that does not issue stablecoins?
The GENIUS Act’s federal payment stablecoin issuer license applies specifically to entities that issue payment stablecoins, meaning they create and maintain the token and its reserves. A vendor that transmits or holds stablecoins issued by someone else, such as Circle’s USDC or Tether’s USDT, is not subject to the GENIUS Act issuer license. That vendor still needs state MTLs and FinCEN MSB registration for transmission activity, and potentially a state trust charter or qualified custodian status for custody.
Does a New York BitLicense cover the same activities as a money transmitter license?
No. The New York BitLicense, issued by NYDFS under the virtual currency business activity regulations, covers activities specific to virtual currency: buying, selling, exchanging, transmitting, controlling, administering, or issuing virtual currency involving New York residents. It functions as a separate authorization from the standard New York money transmitter license. Some activities require both. A vendor operating in New York for digital asset transmission needs to have specifically addressed NYDFS authorization, not just a general MTL that predates the BitLicense framework.
What happens to my platform if our stablecoin vendor’s license lapses in a state?
If the vendor’s license lapses, they must stop providing licensed activity in that state. Your platform’s users in that state lose access to the service. Beyond the service disruption, if your platform continued to route transactions through an unlicensed vendor in that state after the lapse, your platform could face state regulatory action for aiding unlicensed money transmission. This risk is why gap-ownership clauses and service limitation language in the vendor contract matter operationally, not just legally.
Is FinCEN MSB registration the same as being licensed?
No. FinCEN MSB registration is a federal anti-money laundering registration requirement under the Bank Secrecy Act. It is mandatory for any company qualifying as a money services business, but it is not a license and does not authorize activity in any state. State MTLs are separately required and operate under state law. A vendor can be FinCEN-registered and still be unlicensed in 40 states. Both the federal registration and the relevant state licenses must be in place for a vendor to operate legally across US geographies.
Does the GENIUS Act affect stablecoin vendors operating today before full implementation?
The GENIUS Act created transition provisions for stablecoin issuers operating before the law’s enactment. Issuers that were already operating had a defined window to file for a qualifying license or charter under the new framework. The exact compliance timeline under the Fed’s proposed rules, which were in proposal stage as of October 2026, determines when full compliance is required for existing issuers. For platforms evaluating issuance vendors, the practical question is whether the vendor has filed for GENIUS Act authorization or is operating under a qualifying state charter, not whether they completed the process before the law passed.
The Practical Conclusion for Vendor Shortlisting
License coverage is not a legal checkbox. It is a product constraint. A stablecoin vendor without New York and California coverage is a vendor that cannot serve two of the largest user markets in the US, regardless of how good the API is. A vendor whose coverage depends entirely on a bank partnership is a vendor with a concentration risk that does not appear in their product documentation. These facts should shape the shortlist before the technical evaluation begins, not after.
The compliance picture in stablecoin infrastructure is also genuinely changing in real time. The GENIUS Act’s federal framework is being implemented, the Fed’s reserve rules are in proposal, and state regulators are actively updating their guidance on digital asset transmission. A vendor’s license status today may not reflect their status in 12 months. That is an argument for requiring quarterly license confirmation as a contract term, not for accepting a one-time disclosure at signing.
The platform that gets this right runs the FintechSpecs Vendor License Stress Test before it runs a product demo. It treats the license map as the shortlist filter, not as the last page of the due diligence packet. In a market where regulatory gaps at the vendor level become platform risk by default, the infrastructure decision and the compliance decision are the same decision.
