Integration with KopoKopo M-PESA integration interface

Verified on 15.06.2012
Mifos Kopo Kopo integration URL works properly in REST api client and also by using "curl" program.

_{Build Date: Tue Jun 12 02:13:03 PDT 2012
Build Number: hudson-head-i-release-archive-3}

Mifos integration URL is "/basic/k2/processTransaction.json" and it use basic http authentication, so You must provide login credentials.
Example of full URL:
http://mifos:testmifos@localhost:8080/mifos/basic/k2/processTransaction.json
(standard credentials works for both basic and form authentication)

For now, only important parameters are: k2_transaction_id, ac_no, currency, amount, mm_system_id, transaction_date.
Based on guides provided by KopoKopo (HTTP POST Notification ticket attachment) I've decided to match operations by "ac_no" parameter. Ac_no is matched as global account number, so if ac_no contains global account number of loan account then mifos process loan payment transaction, if savings account then savings deposit transaction.
Other parameters:

• mm_system_id (mobile money system id) stands for payment type name, for example "M-PESA"

• transaction_date pattern is DD/M/YY.

• k2_transaction_id is used as receiptId for mifos transaction processing

• amount is just the transaction amount

• currency should be valid account currency 3 letter Alphabetical code (example 'INR' or 'USD')

Mifos KopoKopo integration URL can be easily tested with "curl" program (example in ticket attachments from KopoKopo) or with browser with any REST plugin installed.

I've configured basic authentication to use with K2 HTTP(S) POST Notification API. But I think it would be good idea to choose generic pattern for stateless restful URLs using basic http authentication. For example /restful/*/.json or /service/*/.json. Current URL looks like /account/k2/processTransaction.json. Any suggestions?

Since there is no functional specification available, we will not work on this ticket within Release H.

Comments from Jakub on mailing list:

I think that KopoKopo integration is a great idea. I have assigned this
ticket to Release H.

As far as I understand we should only provide a simple REST method,
right? The POST request from the KopoKopo will contain the following fields:

• k2_account_id

• k2_transaction_id

• mm_system_id

• mp_transaction_id

• biller_number

• transaction_date

• transaction_time

• transaction_type

• ac_no

• sender

• first_name

• last_name

• middle_name

• amount

• currency

Rebecca, Ed, do you have any vision/specification how to map these
requests to the Mifos operations? What types of operation do you like to
have available for the KopoKopo? How to match these operations with
active accounts in Mifos? Using sender's mobile phone number (field:
sender), or maybe the account number directly (field: ac_no). If you
provide such functional specification, then the implementation shouldn't
be a big problem.