Bank Data Integration: Progress and Secure Solutions
Week 7October 20, 2024
This week has been a slower one for Reboard. As I mentioned in last week’s post, I spent some time in Sydney. Sydney was great, and the Blue Mountains have some truly beautiful hikes. It’s amazing that building Reboard allows me to work even when I travel. However, progress naturally slows down a bit while I’m on the road.
Product/Tech: Securing the Bank Data Integration
The main focus this past week was on improving the security of the bank data integration. After receiving feedback from GoCardless, I discovered that my initial setup wasn’t as secure as it needed to be. In the previous implementation, a client could potentially access one of the two access tokens used to authorize transactions with GoCardless, which posed a security risk.
Now, I’ve updated the integration so that all requests are routed through a small backend within the application. This setup ensures the token remains hidden, making the integration far more secure. It was a necessary change and one that brings me closer to launching the feature.
Progress and Design Updates
Adding this new functionality to Reboard also means the UI needs to evolve. Currently, I’m working on redesigning the dashboard to display bank data directly from the integration. This will be the focus of the coming week, along with testing the updated UI using real data.
Looking Ahead: Next Week’s Goals
With the bank sync feature becoming more robust and secure, the next step is to finish the UI updates and test everything thoroughly. I’m eager to see how this will enhance Reboard’s user experience and get us ready for the next phase—onboarding our first customers.
Exciting times ahead!