Transforming the Bank: API-driven banking beyond Open APIs
summary
An open source platform that runs as both a API sandbox and production system and claims full compliance with JWT mTLS and OAuth2 PKCE, exposing every function as APIs. It lets teams create APIs via POST (dynamic CRUD entities), serves docs via a resource_docs endpoint that returns Swagger plus Scala function names, pipes events to Kafka support, ties API metrics into Invoice Ninja billing for metered/ratelimited consumers, and already powers a credit‑scoring app that ingests phone data (battery level, contacts) alongside transactions.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:27Open Banking vs API-driven Banking
- 6:49What are the benefits of becoming API-Driven?
- 8:47API driven Billing
- 19:04Functional Overview
related talks
28mOpen Banking, Yin and Yang in Hong Kong
27mDigital Transformation in Banking
21mAPI Design in FinTech: Challenges and Opportunities for next-gen APIs.
23mOpen Banking: The 3rd Channel
23mBanking-as-a-Service: The New API Stack for Banks
27mAPI Design in Fintech: Challenges and Opportunities for next gen APIs
26mOpen Banking and Open Insurance: The Role of APIs and Microservices
23mAdopting APIs & Microservices at a Major Bank (Part 2)
