IdeaWell

Project ideas from Hacker News discussions.

Banks and Credit Unions to Team Up Against Apple Pay Fees

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. Contactless payments reduce friction and are gaining merchant acceptance
Users note that even reluctant merchants (e.g., Walmart, Kroger, Home Depot) now support Apple Pay/tap‑to‑pay, and that the speed gain outweighs the fees banks charge.

“I get why the banks are not happy, but I can tell them that I am not going to use Chase Wallet… just pay the fee and be thankful for the reduced payment friction, which they invariably make money from.” – havaloc
“Every big merchant has now relented (Kroger, Home Depot, Walmart).” – havaloc

2. Privacy and data‑collection concerns around tech‑giant wallets
Commenters debate whether Apple Pay shields transaction data from Apple and merchants, contrasting it with the extensive tracking that occurs when users share phone numbers or use proprietary wallets.

“Apple doesn't see individual transactions when Apple Pay is used… the secret card payment token is sent from the phone to the credit‑card's issuing bank and bypasses Apple servers.” – jasode
“Another alternative… is tapping a piece of plastic instead of your phone and not inviting any of the tech giants into your transactions at all.” – add‑sub‑mul‑div

3. Desire for low‑cost, non‑proprietary payment infrastructure (e.g., Brazil’s Pix or a government‑run system)
Several participants advocate for payment networks that avoid private‑sector rent‑seeking, citing Pix as a successful state‑driven model and arguing that payment facilitation should be a public utility.

“create a payment network that don't rely on private institutions rent seeking behavior, like Pix in Brazil.” – braiamp
“The government's problem… payment facilitation should be a service provided by the government.” – radialstub
“Pix is doing exactly the right thing… ECB/SEPA is as well.” – KellyCriterion

🚀 Project Ideas

Generating project ideas…

OpenTap: Open-Source NFC Tap-to-Pay SDK for Merchants

Summary

  • Provides a royalty-free SDK enabling any POS hardware (including Android-based terminals on GrapheneOS) to accept contactless payments via tokenized card data directly to issuing banks, eliminating merchant fees.
  • Core value proposition: Zero-fee, privacy-preserving tap-to-pay that works across devices and reduces checkout friction.

Details

Key Value
Target Audience Small to medium retailers, pop-up shops, and developers building custom POS systems
Core Feature NFC reader library that performs EMV tokenization locally and settles via ISO 20022 APIs to banks
Tech Stack Rust for core NFC, WASM for portability, gRPC for bank communication, optional SQLite for token cache
Difficulty Medium
Monetization Hobby
#### Notes
- HN users lament Walmart’s lack of tap-to-pay and desire for fee‑free alternatives (e.g., “I would use my non‑profit credit union Wallet if it meant less fees”). OpenTap directly addresses that pain.
- Enables discussion on open payment standards and could spur adoption in privacy‑focused OS communities like GrapheneOS.

FedPay: Real‑Time Low‑Cost Payment Network Inspired by Pix

Summary

  • A federated instant‑payment network connecting participating banks and credit unions via ISO 20022, offering sub‑second transfers with fees capped at a few cents.
  • Core value proposition: Provides a Pix‑like alternative for the US/EU, reducing reliance on card networks and their 1‑3% fees while preserving user privacy.

Details

Key Value
Target Audience Banks, credit unions, fintech apps, and consumers seeking cheap P2P and merchant payments
Core Feature Hub‑spoke clearing house that routes payment messages using XML ISO 20022, settles in central bank reserves, with optional pseudonymization
Tech Stack Java/Spring Boot for hub, Apache Kafka for messaging, PostgreSQL for ledger, SDKs in Kotlin/Swift
Difficulty High
Monetization Revenue-ready: transaction fee of $0.005 per transfer (volume‑based)
#### Notes
- Commenters praised Pix in Brazil and wished for similar infrastructure (“create a payment network that don't rely on private institutions rent seeking behavior, like Pix in Brazil”). FedPay answers that call.
- Could ignite HN debate on public‑utility payment rails and interoperability with existing card schemes.

UnifiedPay Terminal: Single‑Screen POS Interface for All Contactless Methods

Summary

  • A POS software layer that presents a unified “tap or scan” UI, automatically detecting Apple Pay, Google Wallet, bank NFC cards, and QR‑based payments, guiding the cashier and reducing confusion.
  • Core value proposition: Eliminates merchant‑side friction and customer frustration when terminals don’t support a particular contactless method, speeding up checkout.

Details

Key Value
Target Audience Retail chains (e.g., Walmart, Kroger), independent merchants, and POS vendors
Core Feature Adaptive UI that abstracts multiple payment protocols into a single contactless button, with fallback instructions and analytics on transaction time
Tech Stack Electron (or Tauri) for cross‑platform desktop, Node.js backend, libnfc for NFC, ZBar for QR, WebSocket for cloud analytics
Difficulty Low
Monetization Hobby
#### Notes
- HN thread notes Walmart cashiers having to explain “No tap” and customers waving cards uselessly; UnifiedPay would remove that scenario (see comment: “Cashier must explain: No tap…”).
- Practical utility: reduces training costs, improves NPS, and provides data for optimizing checkout flow.

Read Later