A Florida proposal would force Bitcoin ATM operators to look up a customer's same-day activity at other companies' kiosks before completing a transaction — a cross-operator monitoring requirement that goes further than nearly any state crypto-kiosk law on the books. The measure pairs that obligation with a registration regime for virtual currency kiosks and additional compliance and consumer-protection duties.
For operators, this is the line that matters: Florida is not just asking each company to watch its own machines. It is asking them to see across the entire kiosk network, in close to real time, to catch the layering pattern scammers use when they spread a victim's deposits across multiple ATMs in a single day. If Florida enacts it and the mechanism works, expect other states to copy the language. If it can't be implemented, expect the litigation and lobbying fights already underway in Tennessee and North Carolina to intensify.
That distinction matters. Most state laws to date — including the recent North Carolina and Maine measures — cap daily transaction amounts per operator, require fraud warnings, and mandate refunds for scam victims. None of them ask Operator A to know what Operator B's machine did with the same person an hour earlier. Florida's proposal does.
What the Proposal Actually Requires
The core obligations in the source proposal break down into three parts:
Core Requirements in the Florida Proposal:
- Registration: Virtual currency kiosk operators must register under a state regime before operating in Florida.
- Cross-kiosk monitoring: Before processing a new transfer, operators must collect information on a customer's same-day transactions at other kiosks.
- Consumer protection: Additional compliance and consumer-protection obligations attach to registered operators.
The cross-kiosk provision is the genuinely novel piece. Most state crypto-ATM laws to date — including the North Carolina bill that recently passed the House and the Maine Virtual Currency Kiosk Act — focus on per-operator transaction limits, mandatory fraud warnings, refund windows, and licensing. Those rules treat each operator as an island. Florida's proposal treats the kiosk network as a system to be monitored collectively.
The logic tracks the way Bitcoin ATM scams actually work. Victims directed by a "government agent" or "tech support" scammer are frequently told to split a single large theft across multiple machines and multiple operators in one day to stay under per-operator daily limits. A per-operator cap does nothing to stop a victim who simply drives to a competitor's kiosk down the street. Cross-kiosk monitoring is the regulatory answer to that gap.
The Open Question: How Do Operators Actually Check?
The source proposal establishes the obligation but leaves the mechanics unresolved — and the mechanics are where this either becomes a national template or collapses under its own weight. The proposal as presented does not specify:
Unanswered implementation questions:
- Data-exchange mechanism: How is an operator supposed to "collect" information on transactions that happened at a competitor's kiosk?
- System architecture: Whether the state will run a centralized database, mandate peer-to-peer verification between operators, or require a third-party intermediary — each carrying very different cost and privacy profiles.
- Penalties and enforcement: What happens to an operator who fails to check, or who processes a flagged transaction anyway, is not established.
- Exemptions: Whether small operators below a certain kiosk count are exempt, or the mandate applies universally.
- Liability shield: Whether an operator that checks the system and proceeds is shielded from civil liability — or exposed by the very record they created.
That last point is the one operators should watch most closely. Regulators have already begun holding operators liable for fraud losses. A cross-kiosk check that does not come with a clear liability safe harbor creates a worst-case scenario: operators bear the cost and technical burden of monitoring, then still face civil exposure when a scam slips through. Conversely, a mandated check that does shield compliant operators could become something the industry actually wants — a defined standard of care.
The gaps are not nitpicks. A cross-kiosk monitoring mandate without a defined data-exchange mechanism is an instruction without a tool. The proposal's real-world effect depends entirely on infrastructure the source text does not yet describe.
Why This Lands Now
The timing is not coincidental. The proposal arrives in a quarter defined by escalating fraud numbers and a contracting industry.
The state-regulation timeline:
- June 13, 2026: North Carolina House advances a crypto ATM bill with licensing, fraud warnings, and transaction limits.
- June 16, 2026: Bitcoin Depot bankruptcy underscores a shrinking sector.
- June 20, 2026: Minnesota bans crypto ATMs outright following a scam surge.
- June 26, 2026: FBI confirms $333M+ in 2025 kiosk scam losses; Florida's cross-kiosk monitoring proposal surfaces.
The federal government is also moving. H.R. 9268, a bipartisan bill requiring Bitcoin ATM registration, has advanced in Congress following the $333 million fraud figure. Florida's proposal would go further than the federal legislation by mandating active fraud detection rather than passive registration.
Florida sits at a fork the rest of the country is also approaching: ban kiosks entirely, as Minnesota did, or build infrastructure to keep them operating under tighter surveillance. Florida's proposal is firmly in the second camp — and that makes it a more interesting template, because a workable monitoring regime gives other states a middle path between prohibition and the status quo. If it survives the legislative process and proves implementable, it offers something the per-operator caps do not: fraud detection that follows the customer instead of the machine.
What This Means for Consumers
If you use a Bitcoin ATM in Florida and this becomes law, expect more friction and more questions before a transaction completes — by design.
What to expect and what to do:
- You may be flagged or delayed if you've already used another company's kiosk the same day. That is intentional and aimed at scam patterns.
- If anyone — a "government official," "tech support," a "lawyer," or an online "investment manager" — is directing you to deposit cash at multiple Bitcoin ATMs, stop. Splitting a payment across machines to "stay under a limit" is a classic scammer instruction, and exactly the behavior this proposal is designed to flag.
- Crypto sent to a scammer's wallet is generally irreversible. The registration regime may add consumer-protection obligations, but the surest protection is not sending the funds.
- Review your rights and reporting options through our consumer protection resources before using any kiosk.
What This Means for Operators
This is a compliance and infrastructure problem before it is a legal one. The cross-kiosk requirement is the most operationally significant element of the proposal, and it lands during a period when operators are already absorbing licensing costs in multiple states and watching regulators begin to hold them liable for fraud losses. Operators should treat it as a signal of where multi-state regulation is heading, regardless of whether Florida's specific bill passes.
What operators should do now:
- Engage on the mechanism. The proposal does not yet specify centralized database, peer-to-peer, or third-party intermediary. That decision drives your build cost. Get input to the legislature now, before the architecture is locked.
- Map the small-operator question. If there is no kiosk-count exemption, a universal mandate could be existential for operators running a handful of machines who cannot afford a data-exchange integration.
- Demand a liability safe harbor. A check obligation without civil-liability protection for compliant operators is the worst structure for the industry. Push for clarity on whether checking and proceeding shields you.
- Assume contagion. A workable Florida template will be copied. Build cross-kiosk data capability as a strategic asset, not a one-state compliance cost.
The competitive dynamic here is unusual: cross-kiosk monitoring requires rivals to share customer data with one another, which cuts against every instinct in a fragmented industry. The operators best positioned to comply are the largest networks with the most internal data — and the consolidation already underway, from Coin Cloud's 2023 collapse to Bitcoin Depot's 2026 bankruptcy, means there are fewer counterparties to coordinate with than there were two years ago.
What to Watch
The decisive question is the one the source proposal leaves open: will Florida build or mandate the actual data-exchange system, or pass an obligation with no infrastructure to fulfill it? An unfunded monitoring mandate becomes a compliance trap that operators cannot satisfy and regulators cannot enforce evenly. A well-specified one — centralized, with a liability safe harbor and a defined small-operator pathway — could be the model that finally gives the industry a national standard of care.
Watch for amendments that name a centralized database, a third-party clearinghouse, or a peer-to-peer standard. Whichever the legislature chooses will determine not just whether Florida's law works, but whether it becomes the model the next dozen states copy.