viguerapablo
Joined 10 years ago
Karma
30
Submissions
20
Member since
Feb 3
Recent submissions
Comment · 6 years ago
At the moment only in English. We've seen that most developers we work with are generally OK using English-based documentation to code. We might look to broaden that to Spanish and Portuguese down the line but it's not an immediate priority.
Comment · 6 years ago
Amazing. Sure, feel free to email me / us at pablo[at] or hello[at] and happy to discuss further.
Comment · 6 years ago
Cool - thanks. Happy to chat further. Is your product mostly UK/Europe based or you also have an active client base in Latam?
Comment · 6 years ago
We are starting with the banks with most coverage - so think Davivienda, Bancolombia, Banco de Bogotá, etc. We'll be looking to have quite a few go live soon. Good point on 2FA/MFA. We have built our API so it can fully account for those in the connection flow. More info here --> https://developers.belvo.co/docs/handling-2-factor-authentic...
Comment · 6 years ago
Did you have an issue when typing in your url? Do you recall what the error message was? We do have a url validation in that form that requires https:// Typing in www. will give you an error.
Comment · 6 years ago
Thanks for the feedback!
Comment · 6 years ago
Our product / tech team is mostly based in Barcelona (early team at least) but we'll actively grow our tech team in Latam as well - mostly Mexico City. Happy to get connected to folks you might think would be a good fit. :)
Comment · 6 years ago
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.
Comment · 6 years ago
Yeah, we know the guys at Plaid pretty well and we're big fans of the infrastructure they have created for fintechs and new financial services.
Comment · 6 years ago
Thanks! We don't yet support NuBank, but it's on the list for sure - both for Mexico (where it launched a month ago) and for Brazil (where we'll look to expand soon). We do plan on adding neobanks and other financial data sources to our API though. Although we typically work in a "data source agnostic" way, we also spend time building up relationships and looking to get directly connected via partnerships.
Comment · 6 years ago
Thanks!
Comment · 6 years ago
Similar to TrueLayer yes, more tailored to the local market in terms of bancarisation % and status of open banking regulation (not existent).
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 :)
Comment · 6 years ago
We did post this originally 24h ago but took it down a few minutes later to refine it and post again today. This should be the good post. Cheers!
Comment · 6 years ago
It's similar in a way, yes. We have clients that are just like Mint for the Latam market.
Comment · 6 years ago
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.