Open Banking, Open Source, and Open Standards
summary
Argues open banking is evolutionary not revolutionary, with government-led regimes aligning policy to open source practices and industry-led efforts often becoming proprietary. Cites PSD2/UK mandates, Canada limiting scope to read-only aggregation (no payments), and Australia publishing consumer data standards on GitHub. Uses Lam & Liu’s model showing demand expansion effect can entrench incumbents despite portability. Notes Canadian credit unions: 5.9M members, ~273B CAD AUM and largest 100 hold ~90% of assets.
AI-written summary · about
chapters (19)
- 0:00Intro
- 2:28Large Credit Union Coalition
- 2:44Canadian Credit Union System
- 3:49What do credit unions do
- 5:22What is open banking
- 6:31Governmentregulated vs open banking
- 8:07Open Finance
- 8:53Business Models
- 12:28Data Portability
- 15:02Demand Expansion Effect
- 17:11Open Banking
- 17:55Open Banking Policy
- 18:42Consumer Data Standards
- 20:14Open Source vs Open Standards
- 20:39Why Cant We Have One Open Banking API Standard
- 22:23Open Standards vs Proprietary Standards
- 23:34Why should we have one open banking standard
- 24:42Examples of open banking tools
- 25:24Strategic considerations
related talks
47mThe State of Open Banking
40mFrom Open Banking to Open Finance. What's to come?
31mOpen Banking – The Brand , the Challenges and the Future
14mKeynote: Open Finance: An Open Source View- Declan O'Gorman
34mDesign for Open Banking - Challenges facing UX Designers
17mOpenBanking : The Day After PSD2
19mWill Open Banking trigger the API of Me?
17mKeynote: Closing Remarks