- A complete and generic banking API for many payment products and services.
## Tasks
[Polish Bank Association API](https://app.swaggerhub.com/apis/ZBP/polish-api/2_1_2#/)
- Official API for polish banks (used by quite a few banks, some with dev sandboxes)
- open-sourced CBS solutions
- scope of CBS/OBP responsibilities, OBP as initial CBS system
- deploy and test OBP functions
- open-source Wallet UI that could be used with OBP
## Goals
-**Current goal:** create EURO eWallet with SEPA payment capabilities and IBAN accounts
-**Future goal:** create multi-currency eWallet with FX and international transfers
## Notes
-*PCS Transfers* is the name of our company in Lithuania
- Later on we will also initiate another team for the client app (front-end + OBP Client)
- If we confirm that we want to use OBP as our API layer, the development of the client can proceed in parallel with the banking layer.
- Scope of CBS responsibilities depends on OBP capabilities and our design choices. It can be either simple connector for OBP to access DIS or a full-fledged Core Banking System. Requires further research.
- The new app should be separated from Exchange. Exchange won't communicate with Banking API at all in initial stages (there will be separate app for that)
- BoL does not look favorably on crypto right now
- We have EMI license ready. We are currently undergoing the certification to gain SEPA access through BoL. The next step is communication testing that will require a fully working DIS system.
- There is not deadline for certification per se, but BoL can revoke a license in there is not effort from FI in a long period of time (about a year after getting license).
- Current MVP for the Banking layer is - working SEPA transfers and account creation (IBAN generation).
## Questions
Question asked during meeting that may prove useful in the future.
**Q: Most apps with FX have a Specialized Bank license, does EMI allow us to run Currency Exchange service? There is agency in Lithuania called [ECOVIS](https://ecovis.lt/fintech/) that specializes in FinTech, maybe they could offer some advice.**
A: EMI license will allow us to do multi-currency transfers and hold multi-currency accounts. We are likely already using ECOVIS for consulting.
**Q: Are we going in the direction of Direct FX, P2P FX or multi-currency banking accounts (e-wallets)?**
A: Yes, we are creating eWallet app (initially only for Euro)
**Q: Do we know anything about the auditing capabilities required by the Bank or Supervisory Institutions?**
A: No, we know nothing about it at the moment.
**Q: Do we want to share the user base from Exchange or just the OAuth server**
A: We want to use the server but not the user-base from the Exchange
**Q: Are we required by law to comply with PSD2 from day one, and if so do we have procedures for KYC (how the process looks)?**
A: Yes, we are obliged to comply with PSD2, RTS etc.
**Q: What is our strategy for different currencies: SWIFT certification, 3rd party provider or something different.**
A: For now only EURO and passporting, later probably USD and ACH transfers.
**Q: From what I've heard there was quite a lot of trouble with ORY Hydra, if we want to separate OAuth service from OBP maybe FusionAuth is worth a shot?**
A: We can experiment with FusionAuth, but most problems with ORY Hydra is on front-end side. Ask Wojtek about it.
**Q: What type of account is our account in BoL, is it bound to a single currency?**
A:
**Q: What if we receive payment in different schema than SEPA (e.g. SWIFT) will it be rejected?**
A:
**Q: Are we a Supervised Financial Institution, is BoL a Financial Market Regulator?**
A:
**Q: Can FI be inderect SWIFT member/user via BoL?**
- Banking API docs, including customers, transfers, SEPA, transactions, etc.
**Q: Do we plan to create a domestic bank account and access domestic payment schema (e.g BACS in GB) for every supported currency or are we planning to outsource it?**
- An open-source banking system that's a bit convoluted.
[Open Bank Project API](https://bnpparibas-apiexplorer.openbankproject.com/?version=OBPv3.1.0&list-all-banks=false&core=&psd2=&obwg=&ignoredefcat=true&bank_id=bnpp.12.de.de&account_id=&view_id=#OBPv3_0_0-getPrivateAccountById)
- Quite extensive banking API.
## Resources
[Yapily "The Open Banking Gateway"](https://docs.yapily.com/)
- Simplified accounts/payment API.
All links and resources that could be usefull in the SEPA project implementation.
[SEPA - The definitive Guide](http://www.sepapolska.pl/dokumenty/EPC066-06-version_2.0_Making_Sepa_a_Reality_WebVersion.pdf)
[SEPA - EPC (guidelines and schemes)](https://www.europeanpaymentscouncil.eu/)
[SEPA - reason codes with new documents (effective 11.2019)](https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2019-05/EPC135-18%20v2.0%20Guidance%20on%20Reason%20Codes%20for%20SCT%20R-transactions.pdf)
[SEPA - usage Guide, contains some Customer-2-Bank messages, error codes and flowcharts](http://www.computerhok.nl/wiki/attach/SEPA/ISO20022_usage_guide_V3.pdf)
[The Berlin Group - one of the SEPA standarization efforts (NextGenPSD2)](https://www.berlin-group.org/nextgenpsd2-downloads)
[eIDAS and Qualified Trust Service Providers](https://www.openbankingeurope.eu/media/1177/preta-obe-mg-001-004-psd2-xs2a-understanding-internet-security-eidas-certificates-guide.pdf)
[RTS - implementation guidelines for CSA](https://eba.europa.eu/regulation-and-policy/payment-services-and-electronic-money/regulatory-technical-standards-on-strong-customer-authentication-and-secure-communication-under-psd2)
[European Third Party Providers Association (ETPPA)](https://www.etppa.org/tpp-news)
## Others
[ISO20022 XML Messages](https://www.iso20022.org/full_catalogue.page)
- Docs messanging format.
[ISO20022 to english](https://www.paiementor.com/payment-messages/)
- A convenient site with formats and full names for XML codes.
Resources useful for implementing eWallet and mWallet from scratch.
---
[Good 'technical' guide for creating mWallet app](https://www.devteam.space/blog/how-to-make-a-mobile-wallet-app/)
[Whitepaper on mobile wallet implementation](https://www.gsma.com/digitalcommerce/wp-content/uploads/2012/10/GSMA-Mobile-Wallet-White-Paper-Version-1-0.pdf)
[Types of payments and estimated costs of developing a mWallet](https://alty.co/blog/how-to-make-a-powerful-mobile-wallet-application/)
[Fintech Genome - Thread with useful banking APIs](https://genome.dailyfintech.com/t/lets-build-a-list-of-banking-apis/201)
[Small collection of interesting banking APIs](https://www.fintastico.com/collections/api-banking/)
[Polish Bank Association API](https://app.swaggerhub.com/apis/ZBP/polish-api/2_1_2#/)
[Saltedge - Good PSD2 compliant API for AISP](https://docs.saltedge.com/account_information/v4/#accounts)
[Fidor Germany Banking - Banking API docs](https://api-docs.fidor.de/v1/transactions/get-transactions)
[CONNECT 2 OCBC - Custom banking API with Accounts, Customers, Rates, Payments](https://api.ocbc.com/store/api_products)
[Stellar "Decentralized financial services for people" - More on a blockchain side of things. Accounts, operations, payments](https://www.stellar.org/developers/horizon/reference/endpoints/accounts-single.html)
[Apache Fintech "microfinance platform" - An open-source banking system that's a bit convoluted](https://demo.openmf.org/api-docs/apiLive.htm)
[Yapily "The Open Banking Gateway" - Simplified accounts/payment API](https://docs.yapily.com/)
[OpenBank ApiGee - Accounts and payments API.](https://openbank.apigee.io/api-catalogue)
[OpenBanking UK - API from official OpenBanking UK specs](https://openbanking.atlassian.net/wiki/spaces/DZ/pages/1000702294/Read+Write+Data+API+Specification+-+v3.1.1) with [Swagger JSON](https://raw.githubusercontent.com/OpenBankingUK/read-write-api-specs/v3.1.1/dist/account-info-swagger.json)
