“Regulators do not ask whether a payment was made by a person or an autonomous agent. They ask whether the business accepted and transmitted funds on behalf of someone else — and control of the funds, not the technology moving them, is what triggers money-transmitter status.”
Whether your agentic-payments startup needs a money transmitter license turns on a single question: do you control customer funds? If your AI agent only instructs a user’s own bank or wallet to move money — a non-custodial software conduit — you may fall outside the money-transmitter definition. If your platform accepts, holds, pools, or controls customer funds in transit, you are likely a money transmitter under FinCEN’s rules and under most state licensing statutes — and the fact that an autonomous agent, rather than a person, presses “send” does not change the answer.
Agentic commerce — AI agents that hold payment credentials and transact autonomously — is arriving faster than the regulatory vocabulary built for it. But the threshold legal question is not new, and it is not AI-specific. Money-transmission law asks what a business does with the money, not what technology initiates the transfer. This guide walks the analysis a founder should run before launch: the federal control test, state licensing, the exemptions that might apply, what changes when the rails are stablecoins, and the unsettled consumer-authorization problem that agent-initiated payments create.
Key takeaways
- Control of funds is the trigger, not autonomy. A platform that accepts and transmits customer funds is a money transmitter; an autonomous agent that never gives the platform control of the funds generally is not.
- Two layers can both apply. Federal FinCEN registration as a money services business and separate state money transmitter licenses are independent requirements.
- The exemptions are real but narrow. The payment-processor and agent-of-payee exemptions can take a genuine software conduit out of scope — but pooling funds, holding float, or sitting between buyer and seller often defeats them.
- Stablecoin rails add a regime, they don’t remove one. The GENIUS Act governs payment stablecoins but does not erase state money-transmission licensing for the broader activity.
- Consumer-authorization law for agents is unsettled. How Reg E’s “authorized transfer” framework applies to autonomous agent payments is not yet resolved; build for auditable authorization now.
The agentic-payments licensing questions at a glance
The five questions that decide the analysis, the law behind each, and the usual answer:
| Question | What it turns on | Controlling authority | Typical answer |
|---|---|---|---|
| Do you control customer funds? | Custody or control of value in transit | 31 CFR 1010.100(ff)(5); FinCEN FIN-2019-G001 | Custodial platform = money transmitter; non-custodial conduit = generally not |
| Federal registration? | Money-services-business status | 31 U.S.C. § 5330; 31 CFR 1022.380 | Register with FinCEN within 180 days and run an AML program if you transmit |
| State licenses? | State money-transmission definitions | State money transmitter statutes | A license in each state where you transmit, unless an exemption applies |
| Does an exemption apply? | Payment-processor / agent-of-payee / technology-only | 31 CFR 1010.100(ff)(5)(ii); state exemptions | Maybe — narrow and fact-specific |
| Are the rails stablecoins? | Payment-stablecoin activity | GENIUS Act, Pub. L. No. 119-27 | A separate federal regime layered on the transmission analysis |
Start here: do you control the funds?
Every other question depends on this one. Federal law defines “money transmission services” as “the acceptance of currency, funds, or other value that substitutes for currency from one person and the transmission of currency, funds, or other value that substitutes for currency to another location or person by any means” (31 CFR 1010.100(ff)(5)). A business that does this is a “money transmitter” — a category of money services business — regardless of the technology it uses.
FinCEN applied that test squarely to software and wallet models in its 2019 guidance on convertible virtual currencies, which turns on control: a person who “accepts and transmits” value, or who has “total independent control” over a customer’s value, is a money transmitter, while a provider that supplies only “the delivery, communication, or network access services used by a money transmitter” to support money transmission services is not.1 The same logic governs an AI agent. If your platform takes custody of a user’s funds — holding them in an account, a pooled wallet, or a float balance — and then dispatches them, you are transmitting value on the user’s behalf. If the agent instead operates on the user’s own account or self-custodied wallet, and the funds never come under your control, you have a much stronger argument that you are a technology provider rather than a transmitter.
The distinction is sharp, and it is where most agentic-commerce models will live or die on licensing: custodial agents transmit; non-custodial agents instruct. Design the fund-flow architecture with that line in mind, because it determines everything below.
The federal layer: FinCEN registration and an AML program
If you are a money transmitter, you are a money services business, and federal law requires you to register with FinCEN. Registration is due within 180 days of the date the business is established, and it must be renewed periodically (31 U.S.C. § 5330; 31 CFR 1022.380).2 Registration is not the whole obligation — it triggers a Bank Secrecy Act compliance program: written anti-money-laundering policies, a designated compliance officer, customer identification and monitoring, suspicious-activity reporting, and recordkeeping.3
For an agentic-payments platform, the AML program raises genuinely new design questions — how to perform customer due diligence when an agent, not a human, initiates each transaction, and how to monitor for suspicious activity across autonomous, high-frequency agent behavior. Those are engineering-and-compliance problems to solve before launch, not after an examiner asks. Federal registration also does not displace state licensing; the two regimes run in parallel.
The state layer: money transmitter licenses (the expensive part)
State licensing is usually the larger burden. Most states require a money transmitter license to receive money for transmission, and most define “money” or “monetary value” broadly enough to include convertible virtual currency. Each state is a separate application, with its own net-worth minimums, surety bonds, background checks, and compliance requirements — which is why nationwide licensure is a multi-state, multi-quarter, and expensive undertaking.4 For the cost, timeline, and sequencing of a multi-state build, and for where crypto activity specifically triggers a license, see our companion guides on money transmitter licensing strategy and the state-by-state crypto licensing map.
The practical takeaway for an agentic-payments founder: if the fund-flow analysis makes you a transmitter, budget for the state layer early, and consider whether a partner-bank or licensed-provider model — operating under another entity’s licenses — is a faster path to market than direct nationwide licensure. That companion-bank question is covered in our money transmitter guidance for crypto companies.
The exemptions that might save you
Not every business that touches a payment is a money transmitter. Two exemption theories matter most for agentic commerce:
- The payment-processor exemption. FinCEN’s rules exclude a person who “acts as a payment processor to facilitate the purchase of, or payment of a bill for, a good or service through a clearance and settlement system by agreement with the creditor or seller,” provided the entity operates through bank-based clearance and settlement and meets the other conditions (31 CFR 1010.100(ff)(5)(ii)(B)).5 A genuine processor that runs transactions through the banking system by agreement with the merchant may qualify.
- The agent-of-the-payee exemption (state law). Many states exempt a person who receives funds as the authorized agent of the payee (the merchant), on the theory that payment to the agent is payment to the seller. The scope varies materially by state, and some states have narrowed it.
These exemptions are narrow and fact-specific. An agentic-commerce platform that pools user funds, holds float between authorization and settlement, or intermediates between both the buyer and multiple sellers frequently falls outside them. Do the exemption analysis deliberately, state by state, before relying on it — an incorrect assumption here is the most common and most expensive licensing mistake in payments.
When the rails are stablecoins or crypto
If your agent settles in payment stablecoins, a second federal regime attaches. The GENIUS Act (Pub. L. No. 119-27, signed July 18, 2025) created the first federal framework for payment stablecoins, with reserve, redemption, and disclosure requirements for permitted issuers.6 The Act governs stablecoin issuance; it does not by itself license the transmission of stablecoins by a payments platform, and it does not preempt state money-transmission licensing outside the stablecoin context. A platform moving stablecoins on users’ behalf should analyze both the GENIUS Act (if it issues) and money-transmission licensing (if it transmits). Where the value moved is convertible virtual currency, FinCEN’s 2019 guidance — and its control test — applies directly.1
The unsettled question: Reg E and agent authorization
The frontier issue for consumer-facing agentic payments is not licensing at all — it is authorization. The Electronic Fund Transfer Act and Regulation E protect consumers against “unauthorized” electronic fund transfers and impose error-resolution duties on the institutions involved (15 U.S.C. § 1693 et seq.; 12 CFR Part 1005).7 Those rules were written for a world in which a person authorizes each transfer. It is not yet settled how a consumer’s standing grant of authority to an autonomous agent — “book my travel under $2,000” — maps onto Reg E’s transaction-level authorization and liability framework, or who bears the loss when an agent transacts in a way the consumer did not specifically intend.
The deeper question beneath authorization is who eats the shortfall, and how Regulation E allocates the loss when a prompt-injected agent moves consumer money is the sharpest open problem a builder should track.
No rule resolves this yet, and any statement to the contrary is premature. What a builder can do now is design for the record a regulator will later want to see: clear, auditable, revocable consumer authorization; per-transaction limits and logs; and a defined error-and-dispute path. Companies that can show how an agent was authorized, and how a consumer can stop and dispute it, will be far better positioned than those treating autonomy as a reason the consumer-protection rules do not apply. They do apply; the only open question is how.
What to do first
In order: (1) map your fund flows and answer the control question honestly — custodial or non-custodial — because it drives everything; (2) if you control funds, plan for FinCEN registration and an AML program built for agent-initiated activity; (3) run the state licensing and exemption analysis before launch, and weigh a partner-bank model against direct licensure; (4) layer in the GENIUS Act analysis if you touch payment stablecoins; and (5) design auditable consumer authorization now, ahead of the rules. Each of these is a question to resolve with counsel before you build the payment flow, not after.
This article provides general information only and is not legal advice. Money-transmission, Bank Secrecy Act, state-licensing, and consumer-protection requirements are complex, fact-specific, and — as applied to autonomous AI agents — genuinely unsettled and evolving. Several positions described here should be confirmed against the controlling statute, regulation, or regulator guidance before you rely on them. Whether and how any requirement applies to a particular business is a determination to make with qualified counsel. No attorney-client relationship is formed by this article. Attorney Advertising.
Work with Astraea Counsel
Astraea Counsel advises fintech, crypto, and AI companies on money-transmission and licensing strategy, Bank Secrecy Act compliance, and the regulatory questions raised by autonomous AI agents. Explore our Regulatory Compliance services or contact us to discuss your payment model.
Related resources
- Do Crypto Companies Need a Money Transmitter License? — the federal and state framework for crypto money transmission
- Money Transmitter Licensing State Strategy — sequencing, cost, and the partner-bank alternative
- State-by-State Crypto Licensing Map — where crypto activity requires a state license
Notes
For a determination on your own agent, see our AI agent licensing lawyer page.
Footnotes
-
Financial Crimes Enforcement Network, “Application of FinCEN’s Regulations to Certain Business Models Involving Convertible Virtual Currencies,” FIN-2019-G001 (May 9, 2019), available at https://www.fincen.gov/resources/statutes-regulations/guidance/application-fincens-regulations-certain-business-models. ↩ ↩2
-
31 U.S.C. § 5330 (registration of money transmitting businesses); 31 CFR 1022.380 (registration of money services businesses; initial registration due within 180 days). ↩
-
31 CFR 1022.210 (anti-money-laundering program requirements for money services businesses); 31 CFR 1022.320 (suspicious activity reporting). ↩
-
See Astraea Counsel, “Money Transmitter Licensing State Strategy” and “State-by-State Crypto Licensing Map” for the state-by-state requirements, net-worth minimums, surety bonds, and cost estimates. State money-transmission definitions and exemptions vary and change; confirm current status per state. ↩
-
31 CFR 1010.100(ff)(5)(ii) (exemptions from the money-transmitter definition, including the payment-processor exemption for transactions through a clearance-and-settlement system by agreement with the seller or creditor). ↩
-
Guiding and Establishing National Innovation for U.S. Stablecoins Act (GENIUS Act), Pub. L. No. 119-27 (signed July 18, 2025) (federal framework for permitted payment stablecoins; reserve, redemption, and disclosure requirements). ↩
-
Electronic Fund Transfer Act, 15 U.S.C. § 1693 et seq.; Regulation E, 12 CFR Part 1005 (consumer protections for electronic fund transfers, including liability for unauthorized transfers and error-resolution procedures). ↩
