Who's Afraid of the Big Bad Third Party Integration?
summary
Has integrated with five to six payment gateways and a messy GDS that only sometimes offers REST/JSON, so the concrete takeaways are: read docs, open a sandbox early, build a simple POC that completes auth and a charge to reveal docs gaps and support slowness, track developer and tester hours, expect major breaking changes (Stripe payment intents required a rebuild costing about as much as the original), allow 20% contingency, and consider use Zapier or Power Automate as middleware instead of direct APIs.
AI-written summary · about
chapters (10)
- 0:00Welcome
- 2:13What is third-party integration
- 8:00Why integrate with third parties
- 10:07Understanding client needs
- 15:02Quoting and cost estimation
- 22:03Documentation challenges
- 28:45Overcoming learning curve
- 34:01Setting up for success
- 41:31Overlooked integration considerations
- 48:29Q&A
related talks
26mMastering API Platforms for Enhanced Payment Integration
43m200 Integrations with 5 Developers
23mScale up your business with API integration
20mBest practices for API Integration
16mAPI Integration with JS: Scalable, and Future-Ready Systems
20mPotential of API integrations, common traps and advices
29mOpportunities and Risk in API Management
23mWhat Makes an Agile API?