Re: Mobile Money Gateway Next Steps

[Ed Cable]

We had a very productive call last week during our 11/22 check-in.
Recordings of that session have been added to the wiki along with a
recording from today's session at
https://cwiki.apache.org/confluence/pages/editpage.action?pageId=74687855
and
https://cwiki.apache.org/confluence/display/FINERACT/2017-11-29+Weekly+Check-In+Meeting


Avik will be sharing some additional feedback based on the results of his
end to end test of some of the code.

Ed

On Tue, Nov 21, 2017 at 10:30 PM, Ed Cable  wrote:

> Hi all,
>
> Our next meeting is Wednesday at 1100GMT via GoToTraining
>
> Based on our last meeting of the mobile money integration group, we had a
> few of the following action items:
>
> *Finalize Architecture:*
> Primarily we need to finalize the architecture and design so that the
> developers working on the gateway can proceed forward. We needed to
> incorporate the following:
>
> - Avik's feedback and oustanding questions from previous meetings
> including
> 1)adding in support for transaction limits at disbursal based on tiered
> KYC, 2) including a separate table for API aggregators, 3) handling of
> failed transactions (both inbound and outbound) and clearly documenting the
> integration with Fineract for how those failed transactions are handled and
> when they're re-attempted, 4) extension of apache fineract to handle
> clients who have mulitple phone numbers and multiple mobile money accounts.
> - Nazeer's continued feedback based on viewing the recent demo from Antony
> (see https://cwiki.apache.org/confluence/display/FINERACT/
> 2017-11-03+Weekly+Check-In+Meeting)  of the code he worked on at
> https://github.com/apache/fineract/compare/develop...
> OmexIT:payment-gateway-integration
>
> - James feedback regarding discovery of the receiver being separate
> following a design similar to Simple Payment Setup Protocol
>
> Whether the payment gateway should be a stand-alone module or directly
> part of Apache Fineract.
>
> Antony saw benefits of having it be part of Fineract so that each tenant
> could have its own transactions.
>
> *Review and incorporate Antony's code into main repo for gateway*
> Code is located at https://github.com/apache/fineract/compare/develop...
> OmexIT:payment-gateway-integration
>
> *Create Tickets for Additional Work on Apache Fineract*
> - Capturing additional mobile numbers per client and tagging or
> categorizing with code that they're for different mobile money providers.
>
>
>
>


-- 
*Ed Cable*
President/CEO, Mifos Initiative
edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
  

Mobile Money Gateway Next Steps

[Ed Cable]

Hi all,

Our next meeting is Wednesday at 1100GMT via GoToTraining

Based on our last meeting of the mobile money integration group, we had a
few of the following action items:

*Finalize Architecture:*
Primarily we need to finalize the architecture and design so that the
developers working on the gateway can proceed forward. We needed to
incorporate the following:

- Avik's feedback and oustanding questions from previous meetings
including
1)adding in support for transaction limits at disbursal based on tiered
KYC, 2) including a separate table for API aggregators, 3) handling of
failed transactions (both inbound and outbound) and clearly documenting the
integration with Fineract for how those failed transactions are handled and
when they're re-attempted, 4) extension of apache fineract to handle
clients who have mulitple phone numbers and multiple mobile money accounts.
- Nazeer's continued feedback based on viewing the recent demo from Antony
(see
https://cwiki.apache.org/confluence/display/FINERACT/2017-11-03+Weekly+Check-In+Meeting)
 of
the code he worked on at
https://github.com/apache/fineract/compare/develop...OmexIT:payment-gateway-integration

- James feedback regarding discovery of the receiver being separate
following a design similar to Simple Payment Setup Protocol

Whether the payment gateway should be a stand-alone module or directly part
of Apache Fineract.

Antony saw benefits of having it be part of Fineract so that each tenant
could have its own transactions.

*Review and incorporate Antony's code into main repo for gateway*
Code is located at
https://github.com/apache/fineract/compare/develop...OmexIT:payment-gateway-integration

*Create Tickets for Additional Work on Apache Fineract*
- Capturing additional mobile numbers per client and tagging or
categorizing with code that they're for different mobile money providers.