Ad Hoc Development vs. API Strategy in Open Banking
summary
Ad hoc project teams produce isolated separate bubbles — standalone APIs, duplicated auth and onboarding, and mismatched contracts — that are hard to reuse or support, so pilots rarely turn into scalable products. A clear strategy defines the regulatory and value playground (PSD2 obligations), standardizes developer portal and API design, plans contracts and support channels, and builds a reusable foundation before scaling. Example: a bank launches a PSD2 premium API and moves toward corporate payments while formalizing onboarding and support.
AI-written summary · about
chapters (17)
- 0:00Intro
- 3:00Why people dont work well together
- 4:10Corporate culture
- 5:22Ad Hoc
- 5:37The End Result
- 5:54New Traits
- 6:14New Team
- 8:02Proof of Concept
- 8:39Different Bubbles
- 11:32Culture
- 13:27Strategy
- 13:39API
- 15:47Business Playground
- 18:14Legal Design
- 20:51Documentation
- 22:27Communication
- 23:58Conclusion
related talks
29mStrategies versus plans for financial services APIs
27mAPI Design in Fintech: Challenges and Opportunities for next gen APIs
23mOpen Banking: The 3rd Channel
26mMastering API Strategies for Digital Transformation
37mIntroduction to essential elements of Open Banking Framework
26mHow API Technology is Revolutionizing Financial Services
21mAPI Design in FinTech: Challenges and Opportunities for next-gen APIs.
27m5 Steps to thrive in the Open Economy