2. Open Banking
1995!
Why do we need a Web
site?!
2000! 2010! 2020!
Of course we have a
Web site!
Of course we have an
API!
Why do we need an
API?!
In the future, every bank will have an API
• Banks gain faster time-to-market and save money!
• Developers have easy data access!
• Customers enjoy improved experience!
• Open APIs for every bank.!
• Open Standards!
• Open Source!
• Open Data!
• Open Innovation!
3. Why important?
Banks can leverage the OBP API to create better customer relationships!
Source: faberNovel, 6 reasons why API are reshaping our business
An API reduces the time, complexity and cost of deploying banking apps!
4. Why now?
Current “workarounds” do not work anymore!
Non-Banking
Competitors!
¾ millennials would be more excited about an offering
from new entrants than from their own bank!
Changing!
Customer Behavior!
71% of millennials would rather go to the dentists than
listen to what banks are saying!
Ageing IT systems!
IT systems are perceived as!
the #1 barrier to innovation!
Upcoming Regulation!
UK Treasury Open Banking Call for evidence, EU’s
PSD-II, Poland’s KNF anti-screen-scrapping decision.!
Source: The Millennial Disruption Index, Scratch 2014 / Innovation in Retail Banking 2013, Efma-Infosys!
5. The Open Bank Project
1/ Open
Standard!
2/ Open Source
Technology!
3/ Developer
Community
Banks can leverage the OBP API to create better customer relationshipsBanks can leverage the OBP API to create better customer relationships
The Open Bank Project is an open
source API and App Store for banks
and a developer community around.!
6. Overview
We offer a white-labeled API solution for banks and complementary services!
OBP Connectors!
OBP API!
Core Banking Systems!
Bank’s
Customers
Trusted!
developers
The Bank
Mobile and web applications
South side!
Adapters!
Public Facing
APIs!
9. RESTful
• HTTP(s)
• An approach to API design
• Resources to GET / POST / PUT / PATCH /
DELETE
• Not quite CRUD
• Supported by many clients, servers (the internet)
• If consistent, developers can make assumptions
about endpoints
• Test in browser
• Versioning in URL
• Sort params in URL
• Test in REST client
• Direct Auth options
10. JSON
Strings, numbers, true, false, null, objects and arrays:
{
"id": 1,
"name": "REST in Practice: Hypermedia and Systems Architecture",
"price": {
"currency": "USD",
"amount": 12.50
},
"good_book": true,
"publisher": "O'Reilly",
"authors": ["Ian Robinson", "Jim Webber", "Savas Parastatidis"],
"available_since": "2010-09-15T17:14:55Z",
"comment": null
}
http://jsonlint.com/ to validate
22. Example Login
Login as an example customer:
“user_name”:“Robert.Cuscal.01”
“password”:“X!5c20e368”
More logins here:
https://github.com/OpenBankProject/OBP-API/wiki/APC-OBP-
API-Sandbox#customer-logins
32. Python script Direct Login
Clone the Repository
https://github.com/OpenBankProject/Hello-OBP-DirectLogin-Python
Follow the README to install
Run python hello_obp.py
Run python hello_payments_v2.1.py
33. Python script with OAuth
Clone the Repository
https://github.com/OpenBankProject/Hello-OBP-OAuth1.0a-Python
Follow the README to install
Run python hello_obp.py
Run python hello_payments_v2.1.py
34. REST client
Open your REST client
Make a GET request to:
https://apc.openbankproject.com/obp/v2.1.0/banks
35. REST client Direct Login
Direct Login
https://github.com/OpenBankProject/OBP-API/wiki/Direct-Login