Written by Helena Markou
San Diego is considering a narrowly targeted response to cryptocurrency scams: make the warning visible at the machine where a customer is preparing to convert cash into a digital asset. The City Council’s September 15 public notice lists an ordinance establishing a cryptocurrency-ATM warning-sign requirement for consideration by the Rules Committee on September 16. The item requests that owners and operators post a city-created warning sign about cryptocurrency scams. It would also make businesses hosting a crypto ATM responsible for ensuring the sign is posted, with a link to scam-stopping information and reporting resources. At this stage, it is a proposed ordinance and agenda item, not an enacted city rule.
The policy starts from an accurate operational observation. Crypto ATMs can accept or dispense cash in exchange for a digital financial asset, and the city notes that they are commonly found in grocery stores, gas stations and corner stores. That physical setting matters. A person under pressure from a scammer may be less likely to pause for abstract online safety guidance than for a short, prominent warning immediately before an irreversible transfer. A well-designed intervention can add friction at the point where urgency, cash access and technical complexity meet. It does not need to solve every crypto scam to make a meaningful difference for some users.
The design of the warning will determine much of its utility. A generic notice that says “beware of scams” may be easy to ignore, especially when an operator on the phone has already supplied a persuasive story. A stronger sign should name recognizable red flags: someone claiming to be a government agency, utility, bank, law-enforcement official, employer or romantic contact; an instruction to move cash quickly; a demand to scan a wallet address or QR code; or a request to keep the transaction secret. It should state plainly that legitimate agencies do not demand payment through a cryptocurrency ATM and provide a clear next action: stop, do not send, and contact a trusted person or reporting channel.
The proposal’s allocation of responsibility is notable. Owners and operators would be responsible for posting the city-created warning, but host businesses would also be responsible for ensuring a sign is present. That dual approach recognizes the practical reality that the ATM operator may be remote while the host location is where a customer sees the device. It can reduce the risk of a gap between contractual responsibility and storefront execution. It also raises implementation questions: how often will signs be inspected, who replaces a damaged notice, what happens when a machine is moved, and what penalties or remediation apply if a warning is missing?
A warning sign is a communication tool, not a transaction-monitoring system. It cannot identify a compromised device, determine whether a caller is coercing a user, recover assets after a transfer, or distinguish every legitimate purchase from a fraudulent one. Nor does a city notice change the technical finality of many blockchain transfers. The proposal should therefore be assessed against a realistic benchmark: whether it creates a timely pause, supplies clear reporting pathways and makes a scammer’s instruction harder to follow. It should not be advertised as a guarantee that cryptocurrency-ATM fraud will disappear.
Accessibility is equally important. Messages should be available in commonly used local languages, readable at the point of transaction, understandable for people unfamiliar with digital assets and usable by customers with visual or cognitive limitations. A QR code or web link alone is insufficient when a user lacks a smartphone, connectivity or time. The sign needs a short human-readable message first, with optional links and telephone reporting information second. The city should also consider whether the notice remains visible through every relevant step of a transaction rather than appearing only before a customer reaches the cash-in screen.
San Diego’s proposal is therefore best understood as a local safeguard at the edge of the crypto ecosystem. It does not regulate a blockchain protocol or decide whether a particular digital asset is legitimate. It attempts to create a clearer informed-consent moment before cash is transformed into a potentially hard-to-recover transfer. If adopted, its success will rest on practical details: prominent messaging, shared accountability, accessible reporting options and honest communication about what a warning can and cannot do. The core insight is sound: where social engineering relies on speed, a well-placed pause can be a meaningful form of protection.
