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: Are there any foreseeable obstacles that I should know about? Is there a development mode where I can build without spending any actual money and just get dummy responses? 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 <http://kingori.co/>