Open Banking. Open Source Solutions

Open banking allows for financial data to be shared between banks and third-party service providers through the use of application programming interfaces (APIs). Traditionally, banks have kept customer financial data within their own closed systems. Open banking allows customers to share their financial information securely and electronically with other banks or other authorized financial organizations such as payment providers, lenders and insurance companies.
Open banking enables third-party developers to create services and applications for financial institutions, expands the possibilities of financial transparency for account holders of banking institutions, allows for the exchange of data about the client with his consent and the creation of personal offers for him.
Provided here Open source tools, adapters and connectors for accessing to Open Banking APIs.

Connection to banks that implement the European PSD2 directive, or through one of the market initiatives: The Berlin Group NextGenPSD2 and The Open Banking UK.


Also see:
1) National Bank of Moldova invites for Consulting on payment services based on EU Directive PSD2.
2) National Bank of Moldova discussed the necessary regulations for transition to “Open Banking”.


Recommendations.
If any of the solutions interests you, or you think that it has a good perspective for development, or you can adapt the software to the needs of citizens, authorities, businesses or NGO-s in Moldova, then you can:


1. International Solutions

# Open Source Solution Web Licence
1 starlingbank / developer-resources
A list of useful links, integrations with our banking API and the community projects that have caught our eye.
developer.starlingbank.com/ different
Open Content
2 wso2 / docs-ob-toolkit-berlin
This repository contains the source code for WSO2 Open Banking Toolkit – Berlin documentation.
berlin.ob.docs.wso2.com/ Apache-2.0
3 GNU Taler Git Repositories
GNU Taler is a free software-based microtransaction and electronic decentralized payment system.  GNU Taler does not use a blockchain. A blind signature is used to protect the privacy of users as it prevents the exchange from knowing which coin it signed for which customer. Taler is short for the “Taxable Anonymous Libre Economic Reserves” and alludes to the Taler coins in Germany during the Early Modern period.
The program as “designed to be anonymous for the payer, but payees are always identified.” In a paper published in Security, Privacy, and Applied Cryptography Engineering, GNU Taler is described as meeting ethical considerations – the paying customer is anonymous while the merchant is identified and taxable.
taler.net/

taler-systems.com/

N/A
4 wso2 / docs-ob-toolkit-uk
This repository contains the source code for WSO2 Open Banking Toolkit – UK documentation.
no website Apache-2.0
5 enablebanking / OpenBankingPythonExamples
Sample Python code showing how to use Open banking APIs (PSD2 AISP & PISP) using enable:Banking Python library.
no website Apache-2.0
6 enablebanking / OpenBankingJSExamples
Sample JavaScript code showing how to use Open banking APIs (PSD2 AISP & PISP) using enable:Banking JS library.
no website Apache-2.0
7 OpenBankingUK / opendata-api-spec-compiled
Official Open Banking UK Open Data API specifications.
openbanking.org.uk/developers/ different
Open Content
8 saltedge / saltedge-examples
Examples of integrating Salt Edge API with different platforms and technologies.
www.saltedge.com different
Open Content
9 peterjskaltsis / up-banking-web-unofficial
An unofficial web app client for Up Banking, built with their new open banking API.
The project is built with Next.js and hosted with Vercel.
Up recently released the beta version of their API and I decided to build a web app to complement Up’s mobile app (I’ve found this also makes a great PWA iPad app for Up too).
up-banking-web-unofficial.vercel.app/ MIT