I totally agree with you. Trust is key. We work hand-in-hand with our partners to build this and educate the market as we grow. In general, all of our products, widgets, sdks, etc. are delivered completely white-label so that we can leverage the trust already existing between end-user and the fintech he/she is interacting with. We're also working with the regulator and other stakeholders to build and drive the education towards open banking for the market as a whole. It's a very long-term process :)
We always try to do our dev work and connect to both the website and the app. In many (most) instances, though, in Latam going via web is the only way forward. That being said, we actively work with banks to partner up and establish direct connections too.
Partnering with banks you mean? Yeah, banks are slow to move but in Latam they're also pretty keen to partner up with fintechs if they see a win/win.
We work on the premise of end-users granting us permission to access and share the data they want for the means/apps they want. So there're an opt-in here. There's no general legal framework against this.
We're constantly improving the institutions page. I agree that adding the url to the bank / entity would be helpful.
The homepage for the developer portal you mean? We put it together using read.me as a first iteration but as we improve the product we'll also polish this up with a more customised UI.
Maybe this helps to understand our authentication flow --> https://developers.belvo.co/docs/connect-widget
I totally agree with you. Trust is key. We work hand-in-hand with our partners to build this and educate the market as we grow. In general, all of our products, widgets, sdks, etc. are delivered completely white-label so that we can leverage the trust already existing between end-user and the fintech he/she is interacting with. We're also working with the regulator and other stakeholders to build and drive the education towards open banking for the market as a whole. It's a very long-term process :)