The Moment Your Agent Holds the Money, You Are in a Different Industry
Money transmission licensing is state-by-state, expensive, slow, and triggered by control of funds rather than by intent, branding or company size. Agentic products walk into it sideways — through a budget balance, a marketplace payout, or a refund leg nobody reviewed.
The analysis is per-flow, not per-company. The most common failure here is a team that reaches a defensible conclusion about its main checkout path and then never re-runs the question for the four other places money moves — the prefunded budget, the seller payout, the refund, and the unspent balance. Each of those is its own receipt and its own transmission, and an exemption that covers one covers none of the others automatically.
The Four Gates
Run every flow through these in order. A flow that clears gates one through three is in scope unless gate four produces a documented exemption for that specific flow. Answer them about what the systems do, not about what the architecture diagram says.
Do you receive funds from one party?
Receiving means the money lands somewhere you direct — your bank account, an account in your name at a partner, a ledger balance you control. A card charge that settles directly to a merchant's own account does not clear this gate. A charge that settles to you and is later disbursed does.
Where it goes wrong: Teams answer no because a processor holds the funds. Ask instead whose name is on the account agreement and who can move the balance without the other party's instruction. That is the question a regulator asks.
Do you transmit them to a second party?
Transmission is the second leg. A one-legged flow — you collect your own fee for your own product — is not transmission. Two legs, where value arrives from a payer and leaves toward someone who is not you, is the classic shape whatever the interface looks like.
Where it goes wrong: An agent that buys a third-party good on the user's behalf has two legs by construction: the user funds the agent, the agent pays the merchant. The automation does not collapse the legs.
Is there a gap in time between the two?
Holding funds between receipt and disbursement is what most licensing regimes are actually protecting against, because the failure they were written for is an insolvent intermediary sitting on other people's money. Same-second pass-through is treated very differently from an overnight or an on-demand balance.
Where it goes wrong: Prefunded agent wallets, unspent credits and 'budget' balances are all a gap in time with a friendlier name. So is a hold placed while a model decides whether to approve a purchase.
Does an exemption actually cover the specific flow?
Exemptions exist and some are genuinely available — acting as the agent of a payee under a written agreement that discharges the payer's debt on receipt, operating as an authorised delegate of a licensee, or being a processor that never takes control. Each has conditions, and each is per-flow rather than per-company.
Where it goes wrong: A company can be exempt for its marketplace settlement flow and unlicensed for the refund, payout or credit-balance flow sitting beside it. Exemption analysis has to be run on every leg, not on the business.
Flow of Funds, Stage by Stage
Take one agentic purchase and follow the money through it. The licensing exposure is not spread evenly across these stages — it concentrates in three of them, and the stage that feels like the product carries none of it.
| Stage | Who holds the funds | Regime in play |
|---|---|---|
| User funds an agent budget | You, or a partner under your name | Stored value / prepaid — the strongest triggerA balance the user can spend later is value you hold for them. Escheat, disclosure and safeguarding duties can attach even where licensing does not. |
| Agent evaluates and selects a merchant | Nobody — no funds move | Outside money transmission entirelyThis is the part that feels like the product and carries none of the licensing risk. Keep it architecturally separate so the risky legs are small and visible. |
| Agent authorises a charge | Card network / issuer | Network rules, not state licensingWhose credential is used decides a great deal. A user's own card on file, charged directly to the merchant, keeps you out of the flow of funds. |
| Funds settle | Whoever the settlement account belongs to | The decisive fact in the whole analysisSettlement to a merchant's own account is a processor posture. Settlement to you, then onward, is receipt and transmission. |
| Unspent balance persists | You | Stored value plus unclaimed propertyDormancy clocks run on balances the user never returns for, and the AI product is often the thing that generated the balance in the first place. |
| Refund or payout leaves | You, briefly | Often the forgotten legSending money back to a user, or out to a seller, creator or worker, is transmission on its own terms even if the inbound leg was exempt. |
Six Agentic Product Shapes, Graded
No funds touch you at any point. This posture costs conversion and buys the entire licensing question away — which is a trade worth pricing explicitly rather than defaulting past.
Processor and gateway postures depend on never having control of the funds. Read the partner agreement for who owns the settlement account and who can direct the balance.
The user gave you money to spend later on their behalf. That is the paradigm case, and 'credits' or 'usage units' do not change it if the units are denominated in currency or refundable in currency.
The agent-of-the-payee route is real but demands a written agreement making your receipt discharge the buyer's obligation. Most marketplaces have the commercial arrangement and not the clause.
Outbound-only products get analysed less often and are squarely in scope. Automating the approval decision with a model adds a second problem: a wrong payout is now a wrong payout at machine speed.
Custody of convertible virtual currency is treated as transmission in most jurisdictions, and non-custodial architectures depend on the user actually holding the key rather than on a description that says so.
The Authorisation Record Is the Other Half
Licensing decides whether you may operate. Consumer payment rules decide what happens when a transaction goes wrong, and they turn on whether the user authorised it. For a checkout page that question is answered by the page. For an agent it is answered by whatever you retained about the instruction the user gave, how the agent interpreted it, and what limits were in force at the time.
A model that was told to stay under a ceiling is not a system that enforces a ceiling. The distinction is invisible until the first incident, at which point it is the whole case. Limits belong in the payment layer, where they fail closed, and the grant of authority belongs in durable storage with a scope, an amount, an expiry and a version of the terms the user saw.
What to write down before the first dollar moves
- Every flow, listed
- Inbound funding, purchase, refund, payout, balance expiry, chargeback recovery. Six lines minimum. A flow that is not on the list has not been analysed.
- The account map
- For each flow, the legal owner of every account the money rests in and who can initiate a movement from it without the other party's instruction.
- The exemption, per flow
- Named, with the contract clause that supports it and the states where you have checked that the exemption exists in that form. "Our processor handles it" is not an entry.
- The float
- Peak and average customer funds held overnight. This single number drives safeguarding expectations, bonding, and how urgent the whole question is.
Frequently Asked Questions
Does an AI shopping agent need a money transmitter licence?
It depends entirely on whether funds pass through your control, and the agent part is irrelevant to the analysis. State statutes generally cover receiving money or monetary value for transmission to another person or location. An agent that recommends and hands off to a merchant checkout never receives anything. An agent that charges a user, holds the money and then pays a merchant has received and transmitted, and a model choosing the merchant changes neither leg. The practical test is whose name is on the account the funds land in and who can move that balance unilaterally. Most teams get this wrong by assuming their processor's licences cover them — those licences cover the processor's conduct, and the exemption a processor relies on is conditioned on never taking control of the funds.
Are prepaid AI credits stored value?
Often, and it turns on what the credits can become rather than what they are called. Credits redeemable only for your own service, non-refundable, and denominated in usage units sit closest to a prepayment for goods, which is generally outside transmission. Credits that are refundable in currency, transferable between users, spendable with third parties, or denominated in dollars look like value you hold for the customer — the stored-value shape. An agent budget is the hardest version because it is dollar-denominated by design: the user funds fifty dollars so the agent can spend up to fifty dollars with merchants who are not you. Two duties can attach even without licensing: disclosure of expiry and fee terms, and unclaimed-property reporting on abandoned balances.
Does the agent-of-the-payee exemption cover a marketplace?
It can, but only where the paperwork matches the theory. The usual shape is that a person receiving payment as the agent of the payee, under a written agreement in which receipt by the agent discharges the payer's obligation, is not transmitting money. Two conditions do the work: a real written agency agreement with the seller, containing the discharge language, so that a buyer who pays you is legally done paying the seller at that moment even if you never remit. Many marketplaces have a seller agreement covering fees, disputes and payout timing and nothing about agency or discharge. The exemption also varies by state, with some limiting it to goods and services or excluding payee categories, so one template is not a national answer.
What is the federal piece and when does it start?
Federal money services business registration runs on a different clock from state licensing and catches teams still deciding the state question. A business qualifying as a money transmitter under the federal definition must register with the financial crimes regulator within a set period of starting to do business, maintain an anti-money-laundering programme with a designated compliance officer, independent review and training, and file the required reports. Registration is a filing rather than an approval, so there is no queue to hide behind. The AI-specific wrinkle is monitoring: agentic products generate high-frequency, small-value, machine-initiated transactions unlike the retail patterns most rulesets were tuned for, so off-the-shelf rules alert on everything or nothing.
Can we rely on our banking or processing partner's licences?
Only through a specific structure, and only if it is real. Two legitimate routes exist. Becoming an authorised delegate or agent of a licensed transmitter puts you under their licence for the appointed flows, but requires an executed appointment, their supervision, and usually their consent to your product design and marketing. Alternatively, a genuine processor posture keeps you outside the definition because you never take control of funds. What does not work is assuming that because a licensed partner is somewhere in the flow, your own receipt is covered — regulators analyse each party's own conduct. Ask the partner in writing which of your flows their licence covers, under what appointment, and what they require of you to keep that true.
How does autonomy change the risk beyond licensing?
It changes the error profile and the authorisation record, which is what every payments dispute turns on. An agent that transacts without per-transaction confirmation creates a category of unauthorised-transaction claim that consumer payment rules resolve in the user's favour, and your evidence is a prompt and a model decision rather than a signature or a checkout page. Three controls matter more than the legal opinion: capture the authority the user actually granted with scope, ceiling and duration in a form you can show months later; enforce per-transaction and cumulative limits in the payment layer rather than the prompt, because a limit a model is asked to respect is not a limit; and make reversal a first-class flow, since the fastest way to turn a model error into a regulatory problem is having no operational path to give the money back.
We only operate in one state. Does that simplify it?
Less than you would hope, because the relevant location in most statutes is the customer's, not yours. A transmitter is generally regulated where the person sending or receiving the money is located, which means a self-serve product with a signup form is potentially in scope in every state a user signs up from on day one. This is why the practical sequencing question is rarely 'which licence first' but 'can we restructure the flow so we do not take control at all', followed by 'if we cannot, can we operate as a delegate of someone who already holds the licences'. Geofencing to a small number of states is a real option and an unpopular one, but it is far cheaper than a multi-state licensing programme and far cheaper than unwinding an unlicensed one.
The Overnight Balance Test
Query your ledger for the total customer funds sitting in accounts you control at midnight, averaged over the last ninety days, and the single highest night.
If that number is not zero, you are holding other people's money overnight, and every question on this page applies to you today rather than at some later stage of the company. If nobody can produce the number, that is the finding.
Related Reading
- Unclaimed property and escheat on prepaid AI credits — what happens to the balance the user never comes back for.
- AI agents and contract liability — whether the agent could bind you to the purchase in the first place.
- AI transaction monitoring and model validation — the programme that follows once registration attaches.