Hi Kingori, Do you mean something like this developed by Eugene http://kn9ts.github.io/project-mulla/ Project Mulla as a solution to your SOAP problems. Project Mulla is a MPESA API RESTful mediator. It lets you make familiar HTTP REST requests, transforming your requests to the fiddling dreaded SOAP/XML requests that the Safaricom MPESA G2 API only understands. It then communicates with the MPESA API gateway, transforming all SOAP responses from the SAG to RESTful JSON responses that you then consume effortlessly Regards, James I'm On Saturday, 9 July 2016, King'ori Maina via skunkworks < skunkworks@lists.my.co.ke> wrote:
Hey Skunks,
I’m considering working on a wrapper for the M-PESA 2nd generation platform <http://www.safaricom.co.ke/business/corporate/m-pesa-payments-services/m-pesa-api> (in my primary programming language) to have closer integration with Safaricom MPesa and also to possibly make it easier for others to integrate (read … abstract all the SOAP stuff). I’m willing to have it open sourced from the word go (even through development). Some people might find it useful.
I’ve never dealt with Safaricom technically etc. … and just want to have a light consultation about what exactly I’m getting myself into.
I’m not in Kenya but I have my Safaricom line roaming so can access MPesa (not sure that bit is really important but ...). Keeping that in mind, I have some questions:
1. Are there any foreseeable obstacles that I should know about? 2. Is there a development mode where I can build without spending any actual money and just get dummy responses? 3. Is a low level explanation of the transaction process somewhere (not the API spec)?
Ps: I’ve simply skimmed through the docs, pardon my naivety (if any).
— King kingori.co