[prev in list] [next in list] [prev in thread] [next in thread]
List: mifos-developer
Subject: Re: [Mifos-developer] Channel (Wallet / Self Service) Integration for PH EE
From: Devansh Aggarwal <f20180131 () goa ! bits-pilani ! ac ! in>
Date: 2020-08-31 8:54:48
Message-ID: CAPLk_tBX1xQRpAtp+gAzQvaD9YekL=HJFgTf_1LvzYW5tbgXyQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi Avik,
Thank you for appreciating my work. I have already contacted Naman and
Shivansh in this regard but I still ask them to give more priority to the
Payment-Hub integration pull request and to the Hover SDK implementation
pull request.
Thank You
Best Regards
Devansh Aggarwal
On Mon, Aug 31, 2020 at 1:14 PM Avik Ganguly <avik@fynarfin.io> wrote:
> Hi Devansh,
>
> The gist looks great and the documentation for each PR looks to be of
> good quality. I can imagine that the work you've done will benefit lots of
> folks once they get merged.
>
> Can you request Naman & Shivansh to review the PR for Payment Hub
> integration <https://github.com/openMF/mobile-wallet/pull/1009> and Hover
> SDK integration <https://github.com/openMF/mobile-wallet/pull/1021>? I
> have subscribed to notifications on activities on these 2 PRs.
>
> Looping in @Ippez Robert <ippezrobert@gmail.com> since he might like to
> test the Hover functionality.
>
> With best regards,
> Avik.
>
> On Sat, Aug 22, 2020 at 11:27 AM Devansh Aggarwal <
> f20180131@goa.bits-pilani.ac.in> wrote:
>
> > Hi Ed and Avik,
> >
> > Sorry for the late reply, here's my Report on work done so far during
> > GSoC 2020 - link
> > <https://gist.github.com/devansh-299/e2041c07d9ab55a747391951e9090df4>.|
> >
> > As for the Payment Hub integration, last year Shivansh, as described by
> > Ed, integrated old Payment Hub flows where all the process was taking place
> > through users created in the Payment Hub environment and were not linked to
> > self service users in any way. This year I worked upon integrating the new
> > Payment Hub APIs via *registered* self service users. For registering a
> > self-service user I used the APIs mentioned here
> > <https://mifos.gitbook.io/docs/payment-hub-ee/overview/payment-hub-apis>
> >
> > Also, currently I am working on preparing a detailed documentation of how
> > I integrated FineractCN along with Fineract 1.x in Mobile Wallet as I
> > believe this will be helpful for other contributors. If you suggest, I can
> > also create something similar for Payment Hub integration.
> >
> > Thank You
> > Best Regards
> > Devansh Aggarwal
> >
> >
> > On Sat, Aug 22, 2020 at 9:57 AM Ed Cable <edcable@mifos.org> wrote:
> >
> > > @Garvit Agarwal <garvitagarwal984@gmail.com> you have gone the furthest
> > > in integrating your channel app with Payment Hub EE/Mojaloop - can you
> > > share on the mailing list thread what you have done thus far to help inform
> > > Avik and Subham. We might have you help with some of the integrations with
> > > GSMA mobile money API that Subham has worked on.
> > >
> > > Likewise, @Devansh Aggarwal <f20180131@goa.bits-pilani.ac.in> you too
> > > have had a lot of interaction with Payment Hub EE so far and it would be
> > > great to try to integrate your work on the wallet with Subham's.
> > >
> > > Shivangi - your app given it's on the current Fineract codebase might be
> > > the most important to try to integrate with Payment Hub EE and the GSMA
> > > mobile money connector at the moment - so please update Avik as well on
> > > your progress.
> > >
> > > Avik, please see my responses in-line:
> > >
> > > ---------- Forwarded message ---------
> > > From: Avik Ganguly <avik@fynarfin.io>
> > > Date: Thu, Aug 20, 2020 at 10:47 AM
> > > Subject: [Mifos-developer] Channel (Wallet / Self Service) Integration
> > > for PH EE
> > > To: Mifos software development <mifos-developer@lists.sourceforge.net>,
> > > Subham Pramanik <subhampramanik@gmail.com>
> > >
> > >
> > > Hi Devs,
> > >
> > > Subham is wrapping up work on GSMA mobile money connector scope. Most
> > > of his PRs are merged. That brings us to the question of whether we can
> > > leverage some of the Mifos channels to demonstrate payment flows such as
> > > those implemented for Mojaloop and GSMA.
> > >
> > > I am aware that Devansh, Shivangi, Garvit and others from the community
> > > have been working on wallet & self service applications. I am not sure on
> > > where everyone is standing regarding completion of their goals but it will
> > > be great if you can share answers / documents to the following :-
> > >
> > > - Did Mojaloop flows ever get integrated at the channel level?
> > >
> > > For all of this, this is still just via the self-service APIs (if they
> > > exist). Unfortunately we've still not made progress with the open banking
> > > layer.
> > >
> > > Devansh has re-implemented the mojaloop flows for merchant qr code and
> > > peer to peer transfer to use an authenticated self service user (was
> > > previously just hard-coded credentials). I believe the merchant request to
> > > pay use case (payee-initiated payment) is still not implemented because we
> > > don't have Fineract notification FCM messaging working yet.
> > >
> > > Garvit has also implemented Payment Hub/Mojaloop flows through Mifos
> > > Mobile CN
> > >
> > >
> > > - Did any old Payment Hub flows get integrated?
> > >
> > > Previously Shivansh had integrated the old Payment Hub flows.
> > >
> > > - Draft documentation or draft gist of your work so far.
> > >
> > > Interns - could you please share this?
> > >
> > > - Any work in progress or changes to the channel side with respect
> > > to auth-n via WSO2?
> > >
> > > Garvit has only started on this but any guidance you can provide to help
> > > unblock them would be appreciated. A blocker for Garvit is there is no
> > > self-service API in which to create a user in Fineract CN. There are no
> > > self-service APIs in fact because the intent was to transform back-office
> > > APIs via the open bank adapter to the Open Banking aPI format.
> > >
> > > - I remember some discussions on integrating notifications. Did
> > > anyone explore the effort to modify FINCN notification service to be part
> > > of PH EE space? Did anyone explore relying on AMS notifications from
> > > Fineract or FINCN?
> > >
> > > Garvit has created a ticket for what needs to be implemented for FINCN
> > > at.
> > >
> > > Ebenezer shared his input on what should be implemented at
> > > https://discourse.mifos.org/t/fcm-notifications-support-for-fineract-cn-https-issues-apache-org-jira-browse-fincn-231/9667 \
> > > it would extend off of
> > > https://cwiki.apache.org/confluence/display/FINERACT/Fineract+CN+Notification
> > >
> > > For Fineract, there was some confusion around what had been implemented.
> > > We had thought support for FCM had been enabled but it was just for SMS
> > > campaigns. There's still an outstanding ticket at
> > > https://issues.apache.org/jira/browse/FINERACT-691 This thread has more
> > > details on the current notifiations support - the effort to for that ticket
> > > might not be too substantial so maybe we could get that implemented. All
> > > the channel apps are ready to consume FCM messaging once the back-end
> > > properly generates it.
> > >
> > > I pasted the discussion around that below.
> > >
> > >
> > >
> > >
> > >
> > > - Would anyone be willing to volunteer to incorporate a reference
> > > GSMA MM flow such as international remittance into one of the channels?
> > >
> > > Let's discuss here or on Slack as some of the interns are awaiting tasks
> > > and with proper direction could work on this.
> > >
> > > Ed
> > >
> > > With best regards,
> > > Avik.
> > >
> > > Discussion on Fineract FCM notifications
> > > ------------------------------------------------------
> > >
> > > Pranjal, Courage, Nazeer and others
> > >
> > > I'm responding on top of this thread as both Devansh and Shashank are
> > > blocked in trying to move forward with the portions of their projects
> > > related to consuming FCM notifications. From our previous meeting, we
> > > had somehow concluded that the PR at
> > > https://github.com/apache/fineract/pull/421 was for FCM notifications support
> > > but in talking with Nazeer it was only for SMS campaigns.
> > >
> > > Nazeer - are you able to clarify on that PR. If it doesn' have the
> > > support for FCM notifications, can we outline the work involved in
> > > providing server-side support to generate the FCM notifications.
> > >
> > > Thanks all. Once we come to more clarity i'll take this to the list. If
> > > a call is quickest way to tackle this, let's get one scheduled.
> > >
> > > Thanks,
> > >
> > > Ed
> > >
> > > On Fri, Jun 5, 2020 at 4:22 PM Ed Cable <edcable@mifos.org> wrote:
> > >
> > > > Hi all,
> > > >
> > > > Just to follow up on the second leg of the meeting we had to discuss
> > > > the notifications sub-system being used for the Request to Pay API for
> > > > the mobile wallet as well as a general update about the mobile wallet use
> > > > case in the near term to have it work in the new lab environment.
> > > >
> > > >
> > > > https://us02web.zoom.us/rec/share/5-oyIZrd1mZLYNLutAL8avU5H9zPX6a8gClL-fEPyh5OYllEDFBX8_ENod_Zeup_?startTime=1591200315000
> > > >
> > > > From the discussion, it appears the current manner in which
> > > > notifications are generated and stored in Fineract 1.x will work for
> > > > the request to pay API. However we must ensure that the self-service users
> > > > (which should be in the same users table but just denoted as
> > > > "self-service") are subscribed to this topic to receive the
> > > > notification.
> > > >
> > > > All students working on the customer-facing apps for Fineract 1.x,
> > > > should familiarize themselves with the notifications system (see
> > > > previous design and how it works) as the client-side integration should
> > > > also be complete for mifos mobile and mobile wallet. If you have any
> > > > questions, please share them publicly on the mifos and fineract dev list
> > > > and discourse forum as it's a valuable discussion for community.
> > > >
> > > > @Ebenezer Graham <ebenezergraham69@gmail.com> can we grab some time to
> > > > discuss integration with the Fineract CN notifications microservices.
> > > >
> > > > We identified some small action items to take to make the current
> > > > mobile wallet work for the prior 2 Mojaloop use cases and soon the 3rd
> > > > Mojaloop use case in our lab environment.
> > > > We need to:
> > > >
> > > > 1) Provide Shivansh and Devansh with both the updated environment
> > > > details of the Fineract, Payment Hub instances in the new lab environment
> > > > as well as the updated API endpoints.
> > > > 2) Confirm where the MSISDN is being stored as an additional attribute
> > > > for Fineract.
> > > > 3) Ensure that the Interop users/customers that are created in the
> > > > Fineract instances have an associated self-service user account and to add
> > > > these credentials to the lab environment Google sheet.
> > > >
> > > >
> > > > https://docs.google.com/spreadsheets/d/1b8BRajrpNacFNEH6gGENDVWIGusLc0pGRd6MnKbqTKM/edit?usp=sharing
> > > >
> > > > Once the above is in place, we should be able to have the initial 2
> > > > mojaloop use cases of peer to peer transfer and payment via QR code work
> > > > with actual authenticated self-service users (not just hard-coded JSON user
> > > > data).
> > > >
> > > >
> > > >
> > > > On Tue, Jun 2, 2020 at 9:19 AM Ed Cable <edcable@mifos.org> wrote:
> > > >
> > > > > Hi everyone,
> > > > > Thank you for those who were able to join, especially to Pranjal for
> > > > > joining short notice. We made some good progress in the discussion but will
> > > > > continue this conversation once Istvan can join during part of our call
> > > > > tomorrow that was scheduled for Open Banking fintech app requirements.
> > > > >
> > > > > Here's a summary of what we concluded and outstanding questions/next
> > > > > steps:
> > > > > *Fineract 1.x*
> > > > >
> > > > > - Creation and Storage of Notifications on Back-End
> > > > > - Per the design of Pranjal and implementation by Courage and
> > > > > Adhiyan, the notifications subsystem for creating and storing
> > > > > notifications through the publisher/subscriber/topic model is
> > > > > complete and more recently has been updated by Nazeer to work with
> > > > > FCM messaging
> > > > > - Slides on Design of Notification Subsystem:
> > > > > https://docs.google.com/presentation/d/1jzqEQxxRYa1ZvN_SXLRwDgXBux1cb3_IMBWbdS7rRV0/edit?usp=sharing
> > > > >
> > > > > - Link to PR updating notifications for Fineract -
> > > > > https://github.com/apache/fineract/pull/421
> > > > > - Receiving notifications through channel apps
> > > > > - Working for Community App
> > > > > - Works for Mifos Mobile and for Mobile Wallet
> > > > > - PR for MIfos MObile for FCM Messaging -
> > > > > https://github.com/openMF/mifos-mobile/pull/1180
> > > > > - Questions/Concerns
> > > > > - Based on Pranjal's current understanding of Request to Pay
> > > > > use case, he believes for notifications like payment requests
> > > > > that are high priority, time-critical, and actionable, we should enhance
> > > > > notifications to generate and store them in a different manner
> > > > > than the current generic system for information updates
> > > > > - Istvan, within Zeebe, how many times will we re-try
> > > > > sending out the payment request notification if the payer
> > > > > doesn't take action?
> > > > > - Would the flow be Mojaloop API to Connector in Payment Hub
> > > > > to Fineract and then to Channel?
> > > > >
> > > > >
> > > > > *Fineract CN*
> > > > >
> > > > > - Creation and Storage of Notifications on Back-End
> > > > > - Separate notifications framework created by @Ebenezer Graham
> > > > > <ebenezergraham69@gmail.com> who i'm looping into this
> > > > > discussion.
> > > > >
> > > > >
> > > > > *Other Questions*
> > > > >
> > > > > - *Mobile Wallet Authentication via Self-Service Users*
> > > > > - Shivansh shared that for the integration that he and Naman
> > > > > did last year to support the peer to peer and merchant proximity use cases
> > > > > that they had to this all with just hard-coded JSON users based on the 4
> > > > > demo user accounts and that they weren't aware of how they would be able to
> > > > > actually authenticate via self-service users to initiate these \
> > > > > transactions.
> > > > > - So we both need to for the interim, ensure we can support
> > > > > doing these transactions in the mobile wallet via self-service APIs but
> > > > > then once we've fully mapped the entire app to use Open Banking APIs, do
> > > > > the transacstions via that manner.
> > > > > - @Istvan Molnar <istvan.molnar@dpc.hu> for our demo web app
> > > > > which allowed a customer to scan a QR code and make payment to a merchant,
> > > > > I thought we were using self-service API, I guess that was only for a staff
> > > > > person that was acting like a customer.
> > > > > - We need to have this transaction actually be supported from
> > > > > our self-service API (in interim) and then open banking API.
> > > > > - I'm glad this call flagged this as it's an important
> > > > > distinction that I didn't realize we weren't yet supporting because for our
> > > > > lab environment, the P2P and proximity payment are supposed to be
> > > > > customer-initiated scenarios, not staff ones.
> > > > > - *This all speaks to the importance and criticality of having
> > > > > our lab environment use the community-developed channel apps and not just
> > > > > reference demo apps as we need to try to closely model real-world
> > > > > scenarios.*
> > > > >
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Ed
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Jun 1, 2020 at 11:44 AM Ed Cable <edcable@mifos.org> wrote:
> > > > >
> > > > > > Hi Mobile Wallet and Mobile Banking teams,
> > > > > >
> > > > > > As part of the ongoing work with supporting the Mojaloop request to
> > > > > > pay API, we will finally get the opportunity to work more closely with \
> > > > > > the DPC team to incorporate our community-developed channel apps into the \
> > > > > > lab environment. Primarily, we need to be able to demonstrate the end to \
> > > > > > end scenario where notification generated by the payer needs is received
> > > > > > by the payee so they can take action to initiate payment based on the
> > > > > > request.
> > > > > >
> > > > > > I'm setting up a call with our mentors and interns for the mobile
> > > > > > banking and mobile wallet apps to discuss a few of the following points
> > > > > > with Istvan, Kristofz, and Zoltan:
> > > > > >
> > > > > >
> > > > > > - What are the endpoints for the communications?
> > > > > > - How are notifications being generated? In Fineract or in the
> > > > > > app?
> > > > > > - What form factor can notifications be received via? In app
> > > > > > through FCM, via SMS?
> > > > > > - How are channel apps invoking the credentials?
> > > > > >
> > > > > > I'm going to send out an invite for 1500GMT on Tuesday.
> > > > > >
> > > > > > Cheers,
> > > > > >
> > > > > > Ed
> > > > > >
> > > > > ᐧ
> > >
> > > Disclaimer:
> > >
> > > Privileged & confidential information is contained in this message
> > > (including all attachments). If you are not an intended recipient of this
> > > message, please destroy this message immediately and kindly notify
> > > the sender by reply e-mail. Any unauthorised use or dissemination of
> > > this message in any manner whatsoever, in whole or in part, is strictly
> > > prohibited. This e-mail, including all attachments hereto, (i) is for
> > > discussion purposes only and shall not be deemed or construed to be a
> > > professional opinion unless expressly stated otherwise, and (ii) is not
> > > intended, written or sent to be used, and cannot and shall not be used, for
> > > any unlawful purpose. This communication, including any attachments, may
> > > not be free of viruses, interceptions or interference, and may not be
> > > compatible with your systems. You should carry out your own virus checks
> > > before opening any attachment to this e-mail. The sender of this e-mail and
> > > *Fynarfin Tech Private Limited* shall not be liable for any damage that
> > > you may sustain as a result of viruses, incompleteness of this message, a
> > > delay in receipt of this message or computer problems experienced.
> > > Mifos-developer mailing list
> > > mifos-developer@lists.sourceforge.net
> > > Unsubscribe or change settings at:
> > > https://lists.sourceforge.net/lists/listinfo/mifos-developer
> > >
> > >
> > > --
> > > *Ed Cable*
> > > President/CEO, Mifos Initiative
> > > edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
> > >
> > > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> > > <http://facebook.com/mifos> <http://www.twitter.com/mifos>
> > >
> > > Mifos-developer mailing list
> > mifos-developer@lists.sourceforge.net
> > Unsubscribe or change settings at:
> > https://lists.sourceforge.net/lists/listinfo/mifos-developer
>
>
> Disclaimer:
>
> Privileged & confidential information is contained in this message
> (including all attachments). If you are not an intended recipient of this
> message, please destroy this message immediately and kindly notify
> the sender by reply e-mail. Any unauthorised use or dissemination of this
> message in any manner whatsoever, in whole or in part, is strictly
> prohibited. This e-mail, including all attachments hereto, (i) is for
> discussion purposes only and shall not be deemed or construed to be a
> professional opinion unless expressly stated otherwise, and (ii) is not
> intended, written or sent to be used, and cannot and shall not be used, for
> any unlawful purpose. This communication, including any attachments, may
> not be free of viruses, interceptions or interference, and may not be
> compatible with your systems. You should carry out your own virus checks
> before opening any attachment to this e-mail. The sender of this e-mail and
> *Fynarfin Tech Private Limited* shall not be liable for any damage that
> you may sustain as a result of viruses, incompleteness of this message, a
> delay in receipt of this message or computer problems experienced.
>
[Attachment #5 (text/html)]
<div dir="ltr"><div><div><div>Hi Avik,<br><br></div>Thank you for appreciating my \
work. I have already contacted Naman and Shivansh in this regard but I still ask them \
to give more priority to the Payment-Hub integration pull request and to the Hover \
SDK implementation pull request. <br><br></div>Thank You<br></div><div>Best \
Regards</div><div>Devansh Aggarwal<br></div></div><br><div class="gmail_quote"><div \
dir="ltr" class="gmail_attr">On Mon, Aug 31, 2020 at 1:14 PM Avik Ganguly <<a \
href="mailto:avik@fynarfin.io">avik@fynarfin.io</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Devansh,<div><br></div><div>The \
gist looks great and the documentation for each PR looks to be of good quality. I \
can imagine that the work you've done will benefit lots of folks once they get \
merged.</div><div><br></div><div>Can you request Naman & Shivansh to review the \
PR for Payment Hub <a href="https://github.com/openMF/mobile-wallet/pull/1009" \
target="_blank">integration</a> and Hover SDK <a \
href="https://github.com/openMF/mobile-wallet/pull/1021" \
target="_blank">integration</a>? I have subscribed to notifications on activities on \
these 2 PRs.</div><div><br></div><div>Looping in <a class="gmail_plusreply" \
id="gmail-m_-7923670338564531952plusReplyChip-0" href="mailto:ippezrobert@gmail.com" \
target="_blank">@Ippez Robert</a> since he might like to test the Hover \
functionality.</div><div><br></div><div>With best \
regards,</div><div>Avik.</div></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Sat, Aug 22, 2020 at 11:27 AM Devansh Aggarwal <<a \
href="mailto:f20180131@goa.bits-pilani.ac.in" \
target="_blank">f20180131@goa.bits-pilani.ac.in</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi Ed and \
Avik,</div><div><br></div><div>Sorry for the late reply, here's my Report on work \
done so far during GSoC 2020 - <a \
href="https://gist.github.com/devansh-299/e2041c07d9ab55a747391951e9090df4" \
target="_blank">link</a>.|<br><br></div><div>As for the Payment Hub integration, last \
year Shivansh, as described by Ed, integrated old Payment Hub flows where all the \
process was taking place through users created in the Payment Hub environment and \
were not linked to self service users in any way. This year I worked upon integrating \
the new Payment Hub APIs via <i>registered</i> self service users. For registering a \
self-service user I used the APIs mentioned <a \
href="https://mifos.gitbook.io/docs/payment-hub-ee/overview/payment-hub-apis" \
target="_blank">here<br></a></div><div><br></div><div>Also, currently I am working on \
preparing a detailed documentation of how I integrated FineractCN along with Fineract \
1.x in Mobile Wallet as I believe this will be helpful for other contributors. If you \
suggest, I can also create something similar for Payment Hub \
integration.<br></div><div><br></div><div>Thank You</div><div>Best \
Regards<br></div><div>Devansh Aggarwal<br></div><div><br></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Aug 22, 2020 at 9:57 AM \
Ed Cable <<a href="mailto:edcable@mifos.org" \
target="_blank">edcable@mifos.org</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><a class="gmail_plusreply" \
id="gmail-m_-7923670338564531952gmail-m_2017978450864157723gmail-m_2458968173780165543m_-6485895589734250856plusReplyChip-1" \
href="mailto:garvitagarwal984@gmail.com" target="_blank">@Garvit Agarwal</a> you \
have gone the furthest in integrating your channel app with Payment Hub EE/Mojaloop - \
can you share on the mailing list thread what you have done thus far to help inform \
Avik and Subham. We might have you help with some of the integrations with GSMA \
mobile money API that Subham has worked on.<div><br></div><div>Likewise, <a \
class="gmail_plusreply" \
id="gmail-m_-7923670338564531952gmail-m_2017978450864157723gmail-m_2458968173780165543m_-6485895589734250856plusReplyChip-2" \
href="mailto:f20180131@goa.bits-pilani.ac.in" target="_blank">@Devansh Aggarwal</a> \
you too have had a lot of interaction with Payment Hub EE so far and it would be \
great to try to integrate your work on the wallet with \
Subham's.</div><div><br></div><div>Shivangi - your app given it's on the \
current Fineract codebase might be the most important to try to integrate with \
Payment Hub EE and the GSMA mobile money connector at the moment - so please update \
Avik as well on your progress.</div><div><br></div><div>Avik, please see my responses \
in-line: </div><div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">---------- Forwarded message ---------<br>From: <strong \
class="gmail_sendername" dir="auto">Avik Ganguly</strong> <span dir="auto"><<a \
href="mailto:avik@fynarfin.io" \
target="_blank">avik@fynarfin.io</a>></span><br>Date: Thu, Aug 20, 2020 at 10:47 \
AM<br>Subject: [Mifos-developer] Channel (Wallet / Self Service) Integration for PH \
EE<br>To: Mifos software development <<a \
href="mailto:mifos-developer@lists.sourceforge.net" \
target="_blank">mifos-developer@lists.sourceforge.net</a>>, Subham Pramanik <<a \
href="mailto:subhampramanik@gmail.com" \
target="_blank">subhampramanik@gmail.com</a>><br></div><br><br><div dir="ltr">Hi \
Devs,<div><br></div><div>Subham is wrapping up work on GSMA mobile money connector \
scope. Most of his PRs are merged. That brings us to the question of whether we can \
leverage some of the Mifos channels to demonstrate payment flows such as those \
implemented for Mojaloop and GSMA.</div><div><br></div><div>I am aware that Devansh, \
Shivangi, Garvit and others from the community have been working on wallet & self \
service applications. I am not sure on where everyone is standing regarding \
completion of their goals but it will be great if you can share answers / documents \
to the following :-</div><div><ul><li>Did Mojaloop flows ever get integrated at the \
channel level?</li></ul><div>For all of this, this is still just via the self-service \
APIs (if they exist). Unfortunately we've still not made progress with the open \
banking layer. </div><div><br></div><div>Devansh has re-implemented the mojaloop \
flows for merchant qr code and peer to peer transfer to use an authenticated self \
service user (was previously just hard-coded credentials). I believe the merchant \
request to pay use case (payee-initiated payment) is still not implemented because we \
don't have Fineract notification FCM messaging working \
yet.</div><div><br></div><div>Garvit has also implemented Payment Hub/Mojaloop flows \
through Mifos Mobile CN</div><div><br></div><ul><li>Did any old Payment Hub flows get \
integrated?</li></ul><div>Previously Shivansh had integrated the old Payment Hub \
flows. </div><ul><li>Draft documentation or draft gist of your work so \
far.</li></ul><div>Interns - could you please share this? </div><ul><li>Any work in \
progress or changes to the channel side with respect to auth-n via \
WSO2?</li></ul><div>Garvit has only started on this but any guidance you can provide \
to help unblock them would be appreciated. A blocker for Garvit is there is no \
self-service API in which to create a user in Fineract CN. There are no self-service \
APIs in fact because the intent was to transform back-office APIs via the open bank \
adapter to the Open Banking aPI format. </div><ul><li>I remember some discussions on \
integrating notifications. Did anyone explore the effort to modify FINCN notification \
service to be part of PH EE space? Did anyone explore relying on AMS notifications \
from Fineract or FINCN?</li></ul><div>Garvit has created a ticket for what needs to \
be implemented for FINCN at.</div><div><br></div><div>Ebenezer shared his input on \
what should be implemented at <a \
href="https://discourse.mifos.org/t/fcm-notifications-support-for-fineract-cn-https-issues-apache-org-jira-browse-fincn-231/9667" \
target="_blank">https://discourse.mifos.org/t/fcm-notifications-support-for-fineract-cn-https-issues-apache-org-jira-browse-fincn-231/9667</a> \
it would extend off of <a \
href="https://cwiki.apache.org/confluence/display/FINERACT/Fineract+CN+Notification" \
rel="nofollow" style="color:rgb(0,0,153);font-family:Arial,Helvetica,"Luxi \
Sans",sans-serif;font-size:14.4px;white-space:pre-wrap" \
target="_blank">https://cwiki.apache.org/confluence/display/FINERACT/Fineract+CN+Notification</a></div><div><br></div><div>For \
Fineract, there was some confusion around what had been implemented. We had thought \
support for FCM had been enabled but it was just for SMS campaigns. There's still \
an outstanding ticket at <a \
href="https://issues.apache.org/jira/browse/FINERACT-691" \
target="_blank">https://issues.apache.org/jira/browse/FINERACT-691</a> This thread \
has more details on the current notifiations support - the effort to for that ticket \
might not be too substantial so maybe we could get that implemented. All the channel \
apps are ready to consume FCM messaging once the back-end properly generates it. \
</div><div><br></div><div>I pasted the discussion around that \
below.</div><div><br></div><div><br></div><div><br></div><div><br></div><ul><li>Would \
anyone be willing to volunteer to incorporate a reference GSMA MM flow such as \
international remittance into one of the channels? </li></ul><div>Let's \
discuss here or on Slack as some of the interns are awaiting tasks and with proper \
direction could work on \
this.</div><div><br></div><div>Ed</div><div><br></div></div><div>With best \
regards,</div><div>Avik.</div><div><br></div><div>Discussion on Fineract FCM \
notifications</div><div>------------------------------------------------------</div><div><br></div><div><div>Pranjal, \
Courage, Nazeer and others</div><div><br></div><div>I'm responding on top of this \
thread as both Devansh and Shashank are blocked in trying to move forward with the \
portions of their projects related to consuming <span>FCM</span> \
<span>notifications</span>. From our previous meeting, we had somehow concluded that \
the PR at <a href="https://github.com/apache/fineract/pull/421" \
target="_blank">https://github.com/apache/fineract/pull/421</a> was for \
<span>FCM</span> <span>notifications</span> support but in talking with Nazeer it \
was only for SMS campaigns.</div><div><br></div><div>Nazeer - are you able to clarify \
on that PR. If it doesn' have the support for <span>FCM</span> \
<span>notifications</span>, can we outline the work involved in providing server-side \
support to generate the <span>FCM</span> \
<span>notifications</span>.</div><div><br></div><div>Thanks all. Once we come to more \
clarity i'll take this to the list. If a call is quickest way to tackle this, \
let's get one scheduled.</div><div><br></div><div>Thanks,</div><div><br></div><div>Ed</div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 5, 2020 at 4:22 PM \
Ed Cable <<a href="mailto:edcable@mifos.org" \
target="_blank">edcable@mifos.org</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi all,<div><br></div><div>Just to \
follow up on the second leg of the meeting we had to discuss the \
<span>notifications</span> sub-system being used for the Request to Pay API for the \
mobile wallet as well as a general update about the mobile wallet use case in the \
near term to have it work in the new lab environment.</div><div><br></div><div><a \
href="https://us02web.zoom.us/rec/share/5-oyIZrd1mZLYNLutAL8avU5H9zPX6a8gClL-fEPyh5OYllEDFBX8_ENod_Zeup_?startTime=1591200315000" \
target="_blank">https://us02web.zoom.us/rec/share/5-oyIZrd1mZLYNLutAL8avU5H9zPX6a8gClL \
-fEPyh5OYllEDFBX8_ENod_Zeup_?startTime=1591200315000</a><br></div><div><br></div><div>From \
the discussion, it appears the current manner in which <span>notifications</span> \
are generated and stored in Fineract 1.x will work for the request to pay API. \
However we must ensure that the self-service users (which should be in the same users \
table but just denoted as "self-service") are subscribed to this topic to \
receive the <span>notification</span>. </div><div><br></div><div>All students \
working on the customer-facing apps for Fineract 1.x, should familiarize themselves \
with the <span>notifications</span> system (see previous design and how it works) \
as the client-side integration should also be complete for mifos mobile and mobile \
wallet. If you have any questions, please share them publicly on the mifos and \
fineract dev list and discourse forum as it's a valuable discussion for \
community. </div><div><br></div><div><a class="gmail_plusreply" \
id="gmail-m_-7923670338564531952gmail-m_2017978450864157723gmail-m_2458968173780165543gmail-m_-1275443967747783329gmail-m_6892949580793566069plusReplyChip-5" \
href="mailto:ebenezergraham69@gmail.com" target="_blank">@Ebenezer Graham</a> can we \
grab some time to discuss integration with the Fineract CN \
<span>notifications</span> microservices.<br></div><div><br></div><div>We identified \
some small action items to take to make the current mobile wallet work for the prior \
2 Mojaloop use cases and soon the 3rd Mojaloop use case in our lab \
environment.</div><div>We need to:</div><div><br></div><div>1) Provide Shivansh and \
Devansh with both the updated environment details of the Fineract, Payment Hub \
instances in the new lab environment as well as the updated API \
endpoints.</div><div>2) Confirm where the MSISDN is being stored as an additional \
attribute for Fineract. </div><div>3) Ensure that the Interop users/customers that \
are created in the Fineract instances have an associated self-service user account \
and to add these credentials to the lab environment Google \
sheet.</div><div><br></div><div><a \
href="https://docs.google.com/spreadsheets/d/1b8BRajrpNacFNEH6gGENDVWIGusLc0pGRd6MnKbqTKM/edit?usp=sharing" \
target="_blank">https://docs.google.com/spreadsheets/d/1b8BRajrpNacFNEH6gGENDVWIGusLc0pGRd6MnKbqTKM/edit?usp=sharing</a><br></div><div><br></div><div>Once \
the above is in place, we should be able to have the initial 2 mojaloop use cases of \
peer to peer transfer and payment via QR code work with actual authenticated \
self-service users (not just hard-coded JSON user \
data).</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div \
dir="ltr" class="gmail_attr">On Tue, Jun 2, 2020 at 9:19 AM Ed Cable <<a \
href="mailto:edcable@mifos.org" target="_blank">edcable@mifos.org</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi \
everyone,<div>Thank you for those who were able to join, especially to Pranjal for \
joining short notice. We made some good progress in the discussion but will continue \
this conversation once Istvan can join during part of our call tomorrow that was \
scheduled for Open Banking fintech app \
requirements.</div><div><br></div><div>Here's a summary of what we concluded and \
outstanding questions/next steps:</div><div><b>Fineract \
1.x</b></div><div></div><div><ul><li style="margin-left:15px">Creation and Storage of \
<span>Notifications</span> on Back-End</li><ul><li style="margin-left:15px">Per the \
design of Pranjal and implementation by Courage and Adhiyan, the \
<span>notifications</span> subsystem for creating and storing \
<span>notifications</span> through the publisher/subscriber/topic model is complete \
and more recently has been updated by Nazeer to work with <span>FCM</span> \
messaging</li><ul><li style="margin-left:15px">Slides on Design of \
<br>
<div style="font-size:small;background-color:rgb(255,255,255);color:rgb(136,136,136)">Disclaimer:</div><div \
style="font-size:small;background-color:rgb(255,255,255);color:rgb(136,136,136)"><br></div><div \
style="font-size:small;background-color:rgb(255,255,255);color:rgb(136,136,136)">Privileged \
& confidential information is contained in this message (including all \
attachments). If you are not an intended recipient of this message, please destroy \
this message immediately and kindly notify</div><div \
style="font-size:small;background-color:rgb(255,255,255);color:rgb(136,136,136)">the \
sender by reply e-mail. Any unauthorised use or dissemination of this message in any \
manner whatsoever, in whole or in part, is strictly prohibited. This e-mail, \
including all attachments hereto, (i) is for discussion purposes only and shall not \
be deemed or construed to be a professional opinion unless expressly stated \
otherwise, and (ii) is not intended, written or sent to be used, and cannot and shall \
not be used, for any unlawful purpose. This communication, including any attachments, \
may not be free of viruses, interceptions or interference, and may not be compatible \
with your systems. You should carry out your own virus checks before opening any \
attachment to this e-mail. The sender of this e-mail and </div><div \
style="font-size:small;background-color:rgb(255,255,255);color:rgb(136,136,136)"><b>Fynarfin \
Tech Private Limited</b> shall not be liable for any damage that you may sustain as a \
result of viruses, incompleteness of this message, a delay in receipt of this message \
or computer problems experienced. </div>Mifos-developer mailing list<br> <a \
href="mailto:mifos-developer@lists.sourceforge.net" \
target="_blank">mifos-developer@lists.sourceforge.net</a><br> Unsubscribe or change \
settings at:<br> <a href="https://lists.sourceforge.net/lists/listinfo/mifos-developer" \
rel="noreferrer" target="_blank">https://lists.sourceforge.net/lists/listinfo/mifos-developer</a></div><br \
clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div \
dir="ltr"><div><div dir="ltr"><b><font face="tahoma, sans-serif">Ed \
Cable</font></b><div><font size="1" face="tahoma, sans-serif">President/CEO, Mifos \
Initiative</font></div><div><font size="1" face="tahoma, sans-serif"><a \
href="mailto:edcable@mifos.org" target="_blank">edcable@mifos.org</a> | Skype: \
edcable | Mobile: +1.484.477.8649<br></font><div><font size="1" face="tahoma, \
sans-serif"><br></font></div><div><font size="1" face="tahoma, sans-serif"><font \
color="#339999"><b>Collectively Creating a World of 3 Billion Maries | </b><a \
href="http://mifos.org" target="_blank">http://mifos.org</a></font> <a \
href="http://facebook.com/mifos" style="font-style:italic" target="_blank"><img \
src="https://secure.plimus.com/developers/817570/Template/icon-tiny-facebook.png" \
alt=""></a><i> </i><a href="http://www.twitter.com/mifos" style="font-style:italic" \
target="_blank"><img \
src="http://organizationsandmarkets.files.wordpress.com/2010/04/icon-tiny-twitter.png" \
></a></font></div></div><div><br></div></div></div></div></div></div></div></div></div>
>
</blockquote></div>
Mifos-developer mailing list<br>
<a href="mailto:mifos-developer@lists.sourceforge.net" \
target="_blank">mifos-developer@lists.sourceforge.net</a><br> Unsubscribe or change \
settings at:<br> <a href="https://lists.sourceforge.net/lists/listinfo/mifos-developer" \
rel="noreferrer" target="_blank">https://lists.sourceforge.net/lists/listinfo/mifos-developer</a></blockquote></div>
<br>
<div style="font-size:small;background-color:rgb(255,255,255);color:rgb(136,136,136)">Disclaimer:</div><div \
style="font-size:small;background-color:rgb(255,255,255);color:rgb(136,136,136)"><br></div><div \
style="font-size:small;background-color:rgb(255,255,255);color:rgb(136,136,136)">Privileged \
& confidential information is contained in this message (including all \
attachments). If you are not an intended recipient of this message, please destroy \
this message immediately and kindly notify</div><div \
style="font-size:small;background-color:rgb(255,255,255);color:rgb(136,136,136)">the \
sender by reply e-mail. Any unauthorised use or dissemination of this message in any \
manner whatsoever, in whole or in part, is strictly prohibited. This e-mail, \
including all attachments hereto, (i) is for discussion purposes only and shall not \
be deemed or construed to be a professional opinion unless expressly stated \
otherwise, and (ii) is not intended, written or sent to be used, and cannot and shall \
not be used, for any unlawful purpose. This communication, including any attachments, \
may not be free of viruses, interceptions or interference, and may not be compatible \
with your systems. You should carry out your own virus checks before opening any \
attachment to this e-mail. The sender of this e-mail and </div><div \
style="font-size:small;background-color:rgb(255,255,255);color:rgb(136,136,136)"><b>Fynarfin \
Tech Private Limited</b> shall not be liable for any damage that you may sustain as a \
result of viruses, incompleteness of this message, a delay in receipt of this message \
or computer problems experienced. </div></blockquote></div>
Mifos-developer mailing list
mifos-developer@lists.sourceforge.net
Unsubscribe or change settings at:
https://lists.sourceforge.net/lists/listinfo/mifos-developer
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic