OBP-API | open source RESTful API platform for banks that supports | REST library

by OpenBankProject Scala Version: v3.0.0 License: No License

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | OBP-API Summary

OBP-API is a Scala library typically used in Web Services, REST applications. OBP-API has no bugs, it has no vulnerabilities and it has medium support. You can download it from GitHub.

The Open Bank Project is an open source API for banks that enables account holders to interact with their bank using a wider range of applications and services. The OBP API supports transparency options (enabling account holders to share configurable views of their transaction data with trusted individuals and even the public), data blurring (to preserve sensitive information) and data enrichment (enabling users to add tags, comments and images to transactions). Thus, the OBP API abstracts away the peculiarities of each core banking system so that a wide range of apps can interact with multiple banks on behalf of the account holder. We want to raise the bar of financial transparency and enable a rich ecosystem of innovative financial applications and services. Our tag line is: Bank as a Platform. Transparency as an Asset. The API supports OAuth 1.0a, OAuth 2, OpenID Connect and other authentication methods. See here for more information.

Support

Quality

Security

License

Reuse

Support

OBP-API has a medium active ecosystem.

It has 1438 star(s) with 404 fork(s). There are 125 watchers for this library.

It had no major release in the last 6 months.

There are 194 open issues and 378 have been closed. On average issues are closed in 924 days. There are 6 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of OBP-API is v3.0.0

Quality

OBP-API has no bugs reported.

Security

OBP-API has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

OBP-API does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

OBP-API releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of OBP-API

Get all kandi verified functions for this library.

OBP-API Key Features

No Key Features are available at this moment for OBP-API.

OBP-API Examples and Code Snippets

No Code Snippets are available at this moment for OBP-API.

Community Discussions

Trending Discussions on OBP-API

Where to find the PSD2 technical specification?

OpenBankProject: DirectLogin missing parameters

QUESTION

Where to find the PSD2 technical specification?

Asked 2019-Jun-25 at 11:09

PSD2, The Payment Services Directive of the EU.

Financial institutions in the EU need to be PSD2 compliant, and there's a bunch of vendors claiming PSD2 compliancy. PSD2 is supposed to be a uniform EU-wide standard, and there's a million whitepapers, video blogs, impact estimates, high level overviews, but no technical specification.

Nothing saying really what message needs to be sent where and then happens what. The closest thing I found is this but even there there's no reference, nothing to imply what exact technical spec they followed.

Does anybody know where to get the official PSD2 technical requirements?

EDIT: I tried my luck with the developers of openbanking project

PS I understand that this question is technically a "questions asking us to recommend or find a book, tool, software library, tutorial or other off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam"

This question must have a unique and precise answer from a single regulator - the EC, this is not an opinionated answers area.

...

ANSWER

Answered 2017-Sep-28 at 12:52

I got an answer from the "owner" of the OBP project, I'm posting it verbatim:

Regarding the current status, Open Bank Project API develop branch currently supports OBP API specs 1.2.1 through 3.0.0

We also have an ISO20022 connector (PAIN) for initiating payments.

You can read the OBP specs here:

https://apiexplorersandbox.openbankproject.com/

or use the Swagger:

https://apisandbox.openbankproject.com/obp/v1.4.0/resource-docs/v3.0.0/swagger

or Resource Docs (our own format):

https://apisandbox.openbankproject.com/obp/v1.4.0/resource-docs/v3.0.0/obp

(the Swagger / Resource Doc links can also be found at the bottom of the API Explorer)

Regarding PSD2, PSD2 doesn't explain exactly how countries should comply (e.g. it doesn't define URLs etc.). However, it does say in Article 28 point 3: "Account servicing payment service providers shall also ensure that the dedicated interface uses ISO 20022 elements, components or approved message definitions, for financial messaging".

This is why STET (the recent French standard) uses field names like "PmtTpInf", "InstrPrty", "SvcLvl" and "Cd" etc.

In addtion to the OBP standards mentioned above, we aim to support:

An ISO 20022 version of OBP. This will most likely be requested using a different Mime type on the current OBP URLs and will be implemented as an automatic translation of OBP terms to ISO20022 equivelents (where they exist). We'll probably support ISO20022 short field names and also longer type names (which are verbose but are more self describing).

UK Open Banking standard
STET (French)
Other Country standards.

Thus OBP API will be able to surface multiple standards using one OBP instance and backend connector. It will provide easy to use REST APIs (OBP) and less easy to read ISO20022 interfaces for compliance.

Hope that helps.

p.s. here is STET: https://www.stet.eu/assets/files/PSD2/API-DSP2-STET_V1.2.2.pdf

Source https://stackoverflow.com/questions/46341494

QUESTION

OpenBankProject: DirectLogin missing parameters

Asked 2017-Dec-12 at 14:25

We are trying to implement the OpenBankProject in an application. Possible auth options are oAuth or DirectLogin (the DirectLogin docs), since we allready are using the second, we chose the fast lane ^^

But now this API keeps returning These DirectLogin parameters are missing: username, password, consumer_key while these are set by curl_setopt.

Current script:

...

ANSWER

Answered 2017-Dec-12 at 14:25

You need to use double quotation for header parameters, like this:

Source https://stackoverflow.com/questions/47773956

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install OBP-API

The project uses Maven 3 as its build tool.

Support

The API documentation is best viewed using the OBP API Explorer or a third party tool that has imported the OBP Swagger definitions. Please refer to the wiki for links.

Find more information at: