From: Floyd N. <flo...@gm...> - 2024-03-01 10:06:42
|
Hi Ed , Thank you Alberto for your email regarding the mpesa integration. I appreciate the detailed explanation of the process involved in creating the code and using it as a translator between the mpesa message and fineract repayment instruction. I am looking forward to implementing this in a straightforward manner. In addition, I wanted to follow up on our previous conversation regarding the documentation for inbound and outbound transactions. Mr Ed Cable could you please share this documentation with us at your earliest convenience? Thank you for your cooperation and assistance in this matter. Best regards, Floyd Nick On Wed, Feb 28, 2024 at 5:42 PM José Alberto Hernández <al...@ar...lutions> wrote: > Hello! > > For the mpesa integration for instance, we need to create a small piece of > code to use this as translator between the mpesa message to fineract > repayment instruction > > In that logic is necessary to know the message reference in the mpesa > message and with that we need to identify the client and the account and > finally to apply the transaction > > That is a straight forward way to implement this > > Thanks and best regards > Alberto > > Sent from my iPhone > > On 28 Feb 2024, at 5:41 a.m., Floyd Nickson <flo...@gm...> > wrote: > > > As for the PHEE mobile money I noticed that the GSMA and Mpesa connectors > don't have ingresses enabled, the ingresses for the mpesa connector > especially the call back URLs serve the validation and confirmation of > transactions. > > The Interop APIs are as follows; > 1. GET /interoperation/accounts/{accountId} →Query Interoperation Account > details > 2. GET /interoperation/accounts/{accountId}/identifiers →Query > Interoperation secondary identifiers by Account Id > 3. GET /interoperation/accounts/{accountId}/kyc →Query KYC by Account Id > 4. GET /interoperation/accounts/{accountId}/transactions →Query > transactions by Account Id > 5. GET /interoperation/health →Query Interoperation Health Request > 6. DELETE /interoperation/parties/{idType}/{idValue} →Allow Interoperation > Identifier registration > 7. GET /interoperation/parties/{idType}/{idValue} →Query Interoperation > Account by secondary identifier > 8. POST /interoperation/parties/{idType}/{idValue} →Interoperation > Identifier registration > 9. DELETE /interoperation/parties/{idType}/{idValue}/{subIdOrType} →Allow > Interoperation Identifier registration > 10. GET /interoperation/parties/{idType}/{idValue}/{subIdOrType} →Query > Interoperation Account by secondary identifier > 11. POST /interoperation/parties/{idType}/{idValue}/{subIdOrType} > →Interoperation Identifier registration > 12. POST /interoperation/quotes →Calculate Interoperation Quote > 13. POST /interoperation/requests →Allow Interoperation Transaction > Request > 14. POST /interoperation/transactions/{accountId}/disburse →Disburse Loan > by Account Id > 15. GET /interoperation/transactions/{transactionCode}/quotes/{quoteCode} > →Query Interoperation Quote > 16. GET > /interoperation/transactions/{transactionCode}/requests/{requestCode} > →Query Interoperation Transaction Request > 17. GET > /interoperation/transactions/{transactionCode}/transfers/{transferCode} > →Query Interoperation Transfer > 18. POST /interoperation/transfers →Prepare Interoperation Transfer > > I would like to know how the above APIs are used i.e what headers should I > pass and which URL should I use. There is fineract-provider/api/v1 and > fineract-provider/api/v1/self, which of the two should I use alongside the > 18 APIs above. How does Fineract process an incoming transaction i.e > inbound deposit from mobile money. > > Kind Regards > > Floyd Nick. > > On Wed, Feb 28, 2024 at 10:50 AM Floyd Nickson <flo...@gm...> > wrote: > >> Thank you @Ed Cable for your support of Mifos. >> >> On Wed, Feb 28, 2024 at 10:27 AM José Alberto Hernández >> <al...@ar...lutions> wrote: >> >>> Hello! >>> >>> There are a couple of ways to implement this, depends on the business >>> needs and other requirements, but in resume yes you can easily integrate >>> Fineract with other applications and/or services >>> >>> Thanks and best regards >>> Alberto >>> >>> Sent from my iPhone >>> >>> On 28 Feb 2024, at 12:41 a.m., Ippez Robert <ipp...@gm...> >>> wrote: >>> >>> >>> Hello, >>> >>> This is a good topic, I have been also looking forward to seeing how >>> this can be implemented for production especially mobile money sending and >>> receiving. I believe the Fineract backend works with the payment hub which >>> actually seems complicated setting up for either testing or production for >>> some of us. >>> >>> Someone with good experience in deployment of the payment hub and >>> Fineract interoperability module can help some of us who wish to extend and >>> implement this for live production. >>> >>> Thanks and regards >>> Robert >>> >>> On Wed, Feb 28, 2024, 9:35 AM Floyd Nickson <flo...@gm...> >>> wrote: >>> >>>> Good Day >>>> Dear Mailing List Members, >>>> >>>> I am interested in exploring the interoperable APIs on Fineract and how >>>> they can be leveraged to send and receive money from mobile money channels. >>>> I believe that these APIs could greatly benefit my current project and I >>>> would like to understand how they work and how they can be integrated into >>>> my application. >>>> >>>> If anyone has experience working with Fineract's interop APIs or has >>>> any resources or information that could help me better understand and >>>> utilize them, I would greatly appreciate your input. >>>> >>>> Thank you in advance for any assistance you can provide. >>>> >>>> Best regards, >>>> Floyd Nick. >>>> >>> Mifos-developer mailing list >>> mif...@li... >>> Unsubscribe or change settings at: >>> https://lists.sourceforge.net/lists/listinfo/mifos-developer >>> >>> Mifos-developer mailing list >>> mif...@li... >>> Unsubscribe or change settings at: >>> https://lists.sourceforge.net/lists/listinfo/mifos-developer >> >> Mifos-developer mailing list > mif...@li... > Unsubscribe or change settings at: > https://lists.sourceforge.net/lists/listinfo/mifos-developer > > Mifos-developer mailing list > mif...@li... > Unsubscribe or change settings at: > https://lists.sourceforge.net/lists/listinfo/mifos-developer |