Add open-banking.io (OBI) provider and vendor - #2425
Open
john-frandsen wants to merge 1 commit into
Open
Conversation
Adds open-banking.io to the provider and vendor databases. open-banking.io (OBI) is an open-source, certificate-free PSD2 open banking connector providing unified bank account information (AIS) access across 30+ EU/EEA markets. Rather than requiring integrators to hold their own eIDAS QWAC/QSeal certificates, OBI routes consented account-data requests through regulated Account Information Service Providers and aggregators, lowering the barrier to open banking adoption. Client SDKs are available for .NET, Node.js, Java, Go and Python. The entry follows the same structure as comparable open banking providers already in the database (e.g. yapily): - vendor 'open-banking-io' linked from the provider entry - payment_method 'bank_transfer' - category 'aggregating' - countries: EU 27 + EEA EFTA (IS, LI, NO) + GB
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
This PR adds open-banking.io (OBI) to the OpenFinTech provider and vendor databases, alongside comparable open banking providers already present such as
yapily.Why it belongs in the catalog
OBI is an open-source, certificate-free PSD2 open banking connector that provides unified bank account information (AIS) access across 30+ EU/EEA markets.
Most existing open banking entries in OpenFinTech (e.g. Yapily) describe regulated AISPs that an integrator connects to directly. OBI occupies a complementary and increasingly common niche: rather than requiring the integrator to hold their own eIDAS QWAC/QSeal certificates, it routes consented account-data requests through regulated Account Information Service Providers and aggregators. This substantially lowers the barrier to open banking adoption for fintechs, neobanks and treasury tools that lack a regulatory licence of their own, and is a meaningful category distinction worth representing in the database.
It also has a concrete, multi-language developer footprint, with maintained client SDKs on:
Changes
Two purely additive changes, no existing entries modified:
data/payment_providers.json— new provideropen-banking-io:vendor:open-banking-iopayment_method:bank_transfercategories:aggregatingcountries: EU 27 + EEA EFTA (IS,LI,NO) +GBnameand an Englishdescriptiondata/vendors.json— new vendoropen-banking-io:links.website:https://open-banking.io/countries,nameanddescriptionValidation
schemas/payment_providers_schema.jsonandschemas/vendors_schema.json(required fields,code/vendorregex,statusenum, translatablename, item regexes).provider.vendorcorrectly references the new vendor, andpayment_method(bank_transfer) exists indata/payment_methods.json.codeopen-banking-iois unique across both databases (no conflicts).Notes
resources/payment_providers/open-banking-io/andresources/vendors/open-banking-io/logo/icon directories are intentionally omitted for now. This is consistent with a number of existing providers that have data entries without image assets; the generated doc page will simply render without a logo until one is supplied. Happy to add a logo in a follow-up if you can point me at an asset you'd like used.codeslug (e.g.open_banking_io) or trim the country list if you'd prefer a different convention.