Hi Saransh. Thanks for your input. Vinayak
On Fri, Apr 17, 2020 at 1:23 AM Saransh Sharma <sara...@muellners.com> wrote: > > > On Fri, Apr 17, 2020 at 5:43 AM Javier Borkenztain <jav...@fiter.io> > wrote: > >> Hi Vinayak, >> >> Yes, it seems a feasible project to be executed within Fineract 1.x. >> >> You can use Fineract APIs to send and receive the data. You can export >> reports in various formats to reconcile data. >> >> We have implemented an extension on the API manager tools of Fineract >> using WSO2 tool <https://wso2.com/>. This allows improving Fineract's >> APIs capabilities. >> >> Do you want to do just accounting on the different loans? What else do >> you need to do with the data? >> >> Let us know how can we help! >> Best, >> Javier >> APACHECON 2020 <https://www.apachecon.com/acna2020/>> Call for >> presentations is open! Apply here >> <https://www.apachecon.com/acna2020/cfp.html> for Fineract track now!! >> >> >> On Thu, Apr 16, 2020 at 8:02 PM Vinayak Javaly <vina...@urgent.vc> wrote: >> >>> Hello all. I hope this email finds you all well. >>> >>> I'm looking for general advice. >>> >>> I'm building a new system that will aggregate loan information from >>> several different Loan Management Systems. Some of these systems may be >>> from other LMS vendors (e.g. Mambu, LendFoundry). I'm planning to use >>> Fineract as the core LMS in my new system. Here's my planned workflow: >>> >> So most of the fintechs face this issue, infact banks do also come across > such paths. The simple approach taken by partners is to build own solutions > on top fineract API. > This allows fast navigation. > >> >>> 1. Each LMS will periodically send loan product, loan, repayment, >>> etc. info in a standardized format >>> 2. Our system will receive each LMS' data and input it into Fineract >>> 3. We're planning on performing the loan accounting for these loans >>> in Fineract, AND have a periodic reconciliation process with the source >>> LMS' >>> >>> Our approach towards this solution is simple. > We would build webhooks (reverse hooks) where one can send data to, > direclty to fineract using the Oauth scoping, (lacking currently in > fineract). > This extends and eases the pain but in the long term you will be saving a > lot of time for other integrators which will come back to you. > > Integration is an issue as of now , currently fineract has Oauth but it is > limited to authentication. Building such things internally solves key > challenges like scalability and performance also such as fineract-CN. > > All we need is an API manager where we could simply extend existing > without changing the code base is also a better way look at this url > > > https://discourse.mifos.org/t/action-items-from-open-banking-call-on-monday-april-6-2020/9457 > > > >> My questions: >>> >>> 1. Is this a good idea? Does this seem feasible? >>> >>> If it solves your problem for now. > >> >>> 1. Do you see any major or minor issues with this plan? >>> >>> Pros: > Fast, > Soft modelling can be done , like your own data structure and auth layers > , your own integration. > > Cons: > You will end up managing the meta-data with less emphasis on process. > Cumbersome is long run. > Lack of context. > Service over Service approach always leads to failure. > >> Thank you in advance. >>> >>> Stay safe. >>> >>> Vinayak >>> >> >> >> -- >> [image: Logo] <https://www.fiter.io/> >> *Javier Borkenztain* *| CEO* >> *e:* jav...@fiter.io >> *w:* fiter.io <http://www.fiter.io/> >> *m:* +598-94621188 >> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube >> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image: >> linkedin icon] <https://www.linkedin.com/company/fiter-io> >> > > > -- > > Saransh Sharma > *Research Partner* > *Muellner Internet Pvt Ltd * > > > ---------------------------------------------------------------------------------------------- > > The idea of separation of me and you is amazing. > > ---------------------------------------------------------------------------------------------- > *Company Website <https://www.muellners.com/> **Company Linkedin > <https://www.linkedin.com/company/muellners> *Company Facebook > <https://www.facebook.com/muellners> > > This mail is governed by Muellner® Internet Private Limited's IT policy. > The information contained in this e-mail and any accompanying documents > may contain information that is confidential or otherwise protected from > disclosure. If you are not the intended recipient of this message, or if > this message has been addressed to you in error, please immediately alert > the sender by reply e-mail and then delete this message, including any > attachments. Any dissemination, distribution or other use of the contents > of this message by anyone other than the intended recipient is strictly > prohibited. All messages sent to and from this e-mail address may be > monitored as permitted by applicable law and regulations to ensure > compliance with our internal policies and to protect our business. E-mails > are not secure and cannot be guaranteed to be error free as they can be > intercepted, amended, lost or destroyed, or contain viruses. You are deemed > to have accepted these risks if you communicate with us by e-mail. >
