Instructions for self-hosting are now available on github.
If you have any questions or remarks, feel free to contact me under chris (at) openiban.com
.
The openiban API will cease operation on the 24th of May, 10 p.m. GMT.
On May 25th the GDPR will come into force. Consequently, over the course of the last few weeks, some mails from companies that use openiban have reached me, asking me to sign a data processing agreement. They are legally required to do this with all of their third party data processing contractors.
For me as an operator of a free webservice that processes personal data, the new legislation poses unforseeable risks that I am not willing to expose myself to.
I've been running openiban as an individual, on my own time and money, free for anyone to use in any way they want. Openiban made and held the promise, that no data was ever to be logged or reused for analytical purposes.
Thank you for trusting and using the openiban API.
I really enjoyed hosting this webservice and seeing it's usage increase over the course of the last five years. Merely handling a handful of requests per day, the openiban API is now used by various companies and individuals to process close to 400.000 requests per week. This growth happened organically without ever investing a single thought or penny into SEO or advertisement, making me wonder if this could have been a use case for bootstrapping a company.
The API will be shutdown on 24th of May, 10 p.m. GMT. At the same time, the IBAN validation form will be removed.
After the API shutdown, the website will remain active for an indefinite time but it's contents will change. What I will try to do over the next week is:
If you have any questions or remarks, feel free to contact me under chris (at) openiban.com
.
Update (2018/01/24) : Updated BIC data for DE, LU, NL, BE, CH. (Thanks @jaltek!)
Update (2017/12/07) : Updated BIC data for Germany.
Update (2017/08/13) : Added BIC data for Austria and Liechtenstein.
Update (2017/07/24) : Updated BIC data for Germany.
Update (2017/02/23) : Updated BIC data for Belgium.
Update (2017/02/03) : Added BIC data for Switzerland. Improve IBAN generation for countries where the bank code and IBAN lengths are known.
Update (2017/01/10) : Updated BIC data for Luxembourg and Germany.
Update (2016/07/08) : Added BIC data for Luxembourg.
Update (2016/06/19) : Updated BIC data for Belgium, Germany and Netherlands.
Update (2016/03/20) : IBAN Codes (sample) are automatically validated after calculating.
Update (2016/01/07) : Calculate IBAN Codes Beta (sample)
This is Beta functionality, so please make sure that you validate the result manually or by using the validation service.
Update (2016/01/05) : Updated BIC data for Belgium, Germany and Netherlands.
You can use the HTTPS version of this service.
No personal data is stored. No request logs are written. Everything works in memory.
You can use goiban-service for a self hosted service. Or get the source and and installation of go and wrap it with your own web-service implementation. If you have any requests or problems with the service, please file an issue at github or drop an e-mail at support(at)openiban.com .
Check out all gathered metrics in JSON format. The goiban-service implementation supports KeenIO metrics (deprecated). See the README for more information.
Validation currently works by checking validity of the IBAN checksum and the length restriction for country specific IBAN numbers. A list of country specific BIC checks can be found here. If the validation result is valid, the IBAN is technically OK for the specific country.
Warning: Even technically valid IBANs might still contain a crafted bank code or account number.
We currently validate Bank codes for the following countries:
Validation of IBANs also returns a BIC / bank name for the following countries:
Library | Language |
---|---|
openiban.js ⭐ | JavaScript/TypeScript |
OpenIBAN | Python |
OpenIban Connector | PHP (Plugin for Shopware) |