When Making Money Becomes a Headache...
summary
Covers real failures: assuming HTTP status code ≠ success for async settlements, relying on unchecked webhooks, missing idempotent charges that double-bill, and failing to record payment events (uses paper_trail/event sourcing). Shows operational fixes: move charges to background jobs with Sidekiq retries, add monitoring/alerts, run a simulation gateway in production, and write post‑mortems and run RFCs. Demonstrates what was built, why it failed, and how each fix actually behaved.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:51The importance of trust
- 3:38Common payment pitfalls
- 7:23Idempotency in payments
- 8:57Tracking payment history
- 12:26Improving user experience
- 18:27Visibility and control
- 21:06Shipping changes seamlessly
- 26:25Bug handling and conclusion
related talks
31mCoding for Failure
41m(Re)Building a large scale payments system on Rails
29mMoney Makes Your App Go Round
30mSome Funny Things Happened on The Way to A Service Ecosystem
35mTales from the Crypt
35mSurviving Black Friday: Tales from an e-Commerce Engineer
43mAPI Optimization Tale: Monitor, Fix and Deploy (on Friday)
41mOff the Tracks - Challenging the Rails Mindset