Explore Problems

After a customer flagged an unrecognized transaction, Wells Fargo restricted their account and issued a new card — then processed the disputed charge anyway. The fraud prevention process caused double harm: account disruption plus no actual protection. Customers are left worse off for engaging with the bank's fraud reporting system.

Developers must use separate, incompatible SDKs for each cloud storage provider (S3, GCS, Azure Blob, R2), creating vendor lock-in and requiring rewrites when switching or supporting multiple backends. A unified abstraction layer is missing in the JavaScript ecosystem. 229 HN upvotes validates strong developer demand.

Fraudsters impersonating bank fraud departments instruct consumers to make Zelle transfers to recover allegedly stolen funds, causing the actual theft. Banks refuse to reverse these payments despite clear evidence of social engineering. The combination of real-time payment finality and inadequate bank fraud detection creates an unaddressed consumer protection gap.

Fraudsters impersonating law enforcement pressure consumers into transferring funds to protect them from fabricated investigations. Banks refuse to reverse these transfers despite clear evidence of impersonation fraud and social engineering. The combination of urgency tactics and legitimate-looking impersonation defeats existing bank fraud detection systems.

Thieves who steal unlocked phones can immediately execute thousands of dollars in Zelle and Venmo transfers before the owner can react. Payment apps treat physical phone possession as sufficient authorization, creating a structural gap where theft of a device equals theft of funds. Banks and payment platforms systematically deny fraud refunds for these transactions because the device was used directly.