Money Makes Your App Go Round
summary
Payment gateways like Stripe, Braintree, PayPal handle the API but the hard parts are post-charge: one parsing bug occurs about one-in-200–300 transactions, saving failures lose records, and floating point rounding breaks money (use BigDecimal or the money gem). Recommendations: tokenize cards in the browser, store line-item prices and dates, run credit work in small background jobs, make operations idempotent, keep nightly validators and an audit trail (PaperTrail), and expect admin UI and refund logic to be half the product.
AI-written summary · about
chapters (9)
- 0:00Start
- 10:05Testing for Credit Card Failures
- 16:36Persistent Rounding Errors
- 17:30Money Gem
- 21:35Record of Failure
- 22:03Audit Tool
- 23:10Legal Obligations
- 24:32Refunding
- 25:13Take Reporting Seriously
related talks
15mKeynote: The Operating System of Payments, UX and Security in Modern Apps
28mOrchestrating payments for the millions
59mPayments
26mMastering API Platforms for Enhanced Payment Integration
42mThe recurring nightmare. Implementing cross platform in-app subscription purchases
21mCollision 2015 - John Collison of Stripe with Alexandra Suich of The Economist
34mWhen Making Money Becomes a Headache...
20mAgents with Wallets: Building for the Machine-to-Machine Economy