Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
When Making Money Becomes a Headache. Dealing with Payments by Sebastian Sogamoso When things go right and our product starts making money everyone is happy, but sometimes this means the start of the nightmare for people working with payments. Let's not sugar coat it. In this talk you'll learn about some where thing went terribly wrong, some of them involved loosing money. Stories of stuff that can easily get overlooked, about the most common mistakes when working with payments and things you probably won't consider until shit hits the fan. All of this so that you don't run into the same problems and don't have to learn those lessons the hard way. Help us caption & translate this video! http://amara.org/v/Lew3/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the talk "When Making Money Becomes a Headache," delivered by Sebastian Sogamoso at Rails Pacific 2016, the speaker explores the various challenges and pitfalls associated with managing payments within applications. He emphasizes the importance of establishing and maintaining trust with users in order to ensure a positive user experience.\n\nKey points discussed include: \n- **Trust in Payments**: Trust is critical when dealing with payments, and any errors can severely diminish this trust. The talk highlights how bugs in payment processing can lead to users abandoning the application. \n- **Payment Gateway Pitfalls**: It’s a common misconception that the response status codes from payment gateways always correlate with successful transactions. Sogamoso illustrates that many payment operations take significant time to settle, and often the real outcome is communicated via webhooks after the initial status is returned. \n- **Idempotency Issues**: Ensuring idempotency in payment operations prevents users from being charged multiple times for the same transaction. Sogamoso showcases how to structure code to avoid such issues. \n- **Tracking Payment History**: Maintaining a comprehensive payment event history aids in accountability and allows for effective resolution of user queries about their transactions. This can be addressed through event sourcing or the use of libraries like PaperTrail. \n- **User Experience Enhancements**: The speaker outlines five strategies to improve user experience regarding payments: \n - Implement asynchronous transactions to avoid user waiting times. \n - Provide visibility of payment statuses to users to build trust. \n - Allow users to manage and delete their payment information securely. \n - Prepare for seamless deployment of significant changes. \n - Establish robust monitoring and alert systems for dealing with errors promptly. \n\nSogamoso concludes with the necessity of accepting errors as part of software development. He stresses the importance of having strategies in place for communication, proactive user engagement, and post-mortem analysis of bugs to foster continued user trust. Ultimately, the talk serves as a valuable resource for developers to navigate the complexities of payment systems effectively and improve user satisfaction in their applications.
Suggest modifications
Cancel
