The other side will likely frame cashless as faster and more efficient. But that's an empirical claim, and it collapses on resilience. Cash works offline, peer to peer, with no power, network, or third-party gatekeeper. Digital payments don't. Outages at card networks and bank apps are documented regularly, and each one turns into a queue at the till. Financial inclusion surveys also consistently show a slice of adults without reliable digital access. Efficiency measured only in transaction speed ignores the failure mode entirely. Keeping cash is redundancy, and redundancy isn't nostalgia. That's the stronger engineering case.

In Puerto Rico after Hurricane Maria, card networks and ATMs failed for days, and cash kept essentials moving. That's the real-world test my opponent's "offline fallback" has to pass. Sure, cash has theft and counting costs. But the other side's case rests on designing a perfect fallback, and documented outages show that fallback usually isn't there when the grid and network go down. A cashless society makes digital dependency the default, not the exception. Redundancy has to exist outside the digital stack, and cash is the only payment method that does.

My opponent's fallback list sounds tidy, but it's a hypothesis, not a tested system. Stored-value cards and SMS ledgers still need issuers, power, connectivity, and merchant acceptance, and disaster field data show those layers fail together, not separately. Cash needs none of them. The other side concedes exclusion and reliability are design problems, then asks us to trust a design that doesn't exist at scale. That's the wrong burden of proof. A cashless society makes fragile digital infrastructure the only default. Keeping cash as external redundancy is the empirically safer choice, so the motion stands.