Open Banking Compliance
Comply with major Open Banking standards in use worldwide.
Launch an API Sandbox tailored to your needs.
Access new fintech products and talent by launching a hackathon event.
Plan and implement a successful API strategy.
Offer the next generation of financial services.
From the team that inspired the first Open Banking regulation in the world.
Monitor disruptive fintech innovations to ensure compliance with local rules.
Get started with the OBP API.
Get your team API-ready with our personalised training courses.
Dual licensed model
The AGPL is the original open source license updated for the web. You can distribute modified versions if you keep track of the changes and the date you made them. As per usual with GNU licenses, it is a viral licence and you must license derivatives under AGPL. Additionally, the source code must be distributed along with web publication. You can read the full text of the licence here.
Describes the ability to use the software for commercial purposes.
Describes the ability to modify the software and create derivatives.
Describes the ability to distribute original or modified (derivative) works.
Describes the ability to place warranty on the software licensed.
Describes the ability for you to grant/extend a license to the software.
Describes the warranty and if the software/license owner can be charged for damages.
Describes whether the original copyright must be retained.
If use of our drivers under the AGPL does not satisfy your organization, commercial licenses are available with open Bank Project. Feel free to contact us for more details.
Describes the allowance of using contributors’ names, trademarks or logos.
Describes the amount of money paid to TESOBE for the right of using the software
If the library has a “NOTICE” file with attribution notes, you must include that NOTICE when you distribute. You may append to this NOTICE file.
Stating significant changes made to software.