The problem Swikrati solves

With great powers, comes great responsibility. While building Swikrati, we tried to keep this in mind. The AA framework holds a lot of potential and we see it as the dawn of a major revolution. Thus, we decided to build Swikrati, a platform that gives the end-user granular access over fetching data. From specifying what kind of data you want to fetch to specify the frequency at which this data can be fetched, Swikrati grants all access to the end-user. Moreover, each bit of data is stored on the client-side. Thus, fetching data only at the time a user requires it, for the financial institutes and types of data the user has given access to, as frequently as the end-user wants it to, entire access is granted to the end-user.

Different applications at the marketplace fetch data when an end-user signs up on their platform. But since the launch of the AA framework, we decided to give the end-user granular access over the entire application. Moreover, each bit of data is stored at the client end in a secure fashion. We maintain a database storing information sent over by the Setu sandbox required for auditing purposes. The end-user can also get an analysis of the transactions he has performed.

Challenges we ran into

The overall architecture we thought included socket communications too, for a more secure transfer of data but due to the constraint of time, we were unable to include that in our final architecture.