Products · Broad category
Payment processors
Raised as a usability problem by 13 people on Hacker News over 17 years (2010–2026), in 13 threads.
This is a broad category rather than one product, so its issues aren't ranked on the home page.
People raised many different problems with Payment processors, but no single problem has yet been raised by 3 people in 3 different months and threads.
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 13 complaints
- Docs, API and web portal are messy; onboarding requires many calls and emails instead of forms2026-08-17
- Third-party payment providers make it hard to cancel subscriptions, leaving users upset and charged again2021-09-10
- Many payment providers' test systems differ from production and are unusable2019-11-05
- Documentation is confusing and contradictory, and testing payments is tricky2019-01-14
- Support email rejected unless sent from the exact address on file; password reset blocked2018-04-08
- Dashboard uses nonstandard terms for industry-standard concepts, and developer docs are hard to use2017-04-13
- Updating to newer API versions requires near-full rewrites with little migration guidance2017-02-22
- Dashboard is confusing without accountancy vocabulary; terminology is obscure2013-08-19
- Impossible to work out true costs; fee structures and application require info the business lacks2011-08-23
- Website is hard to navigate and emphasizes only simple payments2010-12-14
- Hard to tell what's included versus extra add-on services2010-06-14
- Dialog has no exit, cancel, or Esc option to return to main screen2010-04-28
- Existing subscriptions can't be moved to a new payment system without users re-doing something2010-04-19