Mojaloop Foundation Organizational  Structure


The Mojaloop Foundation’s appointed Board of Directors, Officers, and Technical Governing Board provides the strategic vision, funding, and technical guidance to ensure the long-term health and growth of the Mojaloop open source software and development community.

While the Board of Directors oversees corporate affairs, the Technical Governing Board will oversee the organization’s work program, including participation in software decisions and authorization of code maintainers, consistent with the Mojaloop Foundation’s charitable and educational purpose.


  • Focused on the statutory functions of corporate governance and adherence to the core mission
  • Comprised of one representative appointed by each Sponsor member of the organization
  • Duty of ensuring that the activities of the organization continuously align with and fulfill the stated mission
  • Monitor the regulatory landscape relative to the work of Mojaloop
  • Oversee efforts that elevate education and awareness in support of the organization’s mission
  • Meet via conference call once per month, face-to-face sessions 1-2 times per year
  • Supported by staff for meeting scheduling, agendas, materials, minutes, and other operational activities

Board Chair:  Konstantin Peric, Chair, Mojaloop Foundation Deputy Director, Financial Services for the Poor, Bill and Melinda Gates Foundation

Technical Governing Board:

  • Comprised of a broader set of member representatives than the Board of Directors, the Technical Governing Board  will plan and oversee all of the technical work conducted within the organization
  • Ensure diversity of perspectives and approaches regarding the technical work at hand
  • Empowered to make all decisions regarding technical direction, and approve technical program activities that fall within the scope of the mission, such as code release decisions, standards document approvals, and authorization of code maintainers
  • Meet via conference call once per month, face-to-face sessions at convenings four times per year
  • Supported by staff for meeting scheduling, agendas, materials, minutes, and other operational activities

TGB Chair: Miller Abel, Deputy Director, Principal Technologist, Bill and Melinda Gates Foundation

Executive Director:

  • Directs the day-to-day activity of the Foundation
  • Facilitates the Board of Directors and Technical Governing Board
  • Drives the recruitment of sponsors and members
  • Evangelizes the organization and its work
  • Manages the performance of staff and resources

Paula Hunter, Executive Director, Mojaloop Foundation

Community Manager:

  • Grow and support the community (maintainers)
  • Implementation of support
  • Promote the technology
  • Connect with developers throughout the ecosystem
  • Support Technical Advisory Board work

Community Manager Chair: Simeon Oriko, Director of Community, Mojaloop Foundation

Release Management and DevOps:

  • Manage the agile development process
  • Drive release schedules for all deliverables
  • Contribute to the overall technical strategy
  • Support Technical Advisory Board Work

Release Management and DevOps Chair: Kim Walters, Managing Director, Crosslake Technologies

Design Authority:

  • Ensure a uniform Architecture
  • Create a channel for bringing ideas to Design and Verification
  • Define Technical Strategies
  • Verify Architectural Standards
  • Drive Design Methodologies

Design Authority Chair: James Bush, Principal Architect, ModusBox Inc.

Marketing Steering Group:

  • Ensure clear and strong alignment between the overall Mojaloop
  • Foundation goals and strategy and marketing/communications deliverables and plans
  • Enable Member companies to provide input on the direction of the strategic marketing communications of the Foundation
  • Tap into the technical, business and market knowledge of the Community to provide direction and content opportunities to staff
  • Engage and leverage the collective wisdom of the Community

Marketing Steering Group Chair: Mary Kingsley, Marketing Director, Mojaloop Foundation

Community Council:

  • Foster a strong and diverse Mojaloop community by aiming to engage the global payments community and grow membership.
  • Acts as the voice of the Community; its responsibilities encompass the development and implementation of strategic targets for the Community, and the resolution of potential conflicts.
  • Ensure strong governance and operating procedures in the council as well as the Community more broadly.
  • Track and communicate community metrics

Community Manager Chairs: Simeon Oriko, Director of Community, Mojaloop Foundation & Innocent Kawooya, CEO, HiPipo

Product Council:

  • Promote transparent updates & alignment across workstream activity through a product lens
  • Ensure Workstream Goals align with Product needs & all workstreams are supported by Product People
  • Identify and plan the right work to grow Mojaloop adoption, aligning on a product roadmap
  • Create a mechanism for business requirements & new concepts/ideas to come from real-world adopters
  • Shape the work in a way that priority contributions are simple to ask for
  • Support Marketing Teams with good Product Knowledge to ensure Product Marketing is effective

Product Council Chair: Lesley-Ann Vaughan, Director of Product Strategy, Mojaloop Foundation 

Change Control Board:

  • Drive wider adoption of the Mojaloop Specification
  • Improve clarity and help promote uniformity of implementations
  • Carefully balance considerations of existing implementations and new business needs for changes to keep the burden on existing implementations to a minimum while supporting changes needed to meet new business needs
  • Support changes needed to meet the business needs of adopters by keeping the standard relevant to defend against forking
  • Drive the costs lower for implementation and maintenance

Apart from these, the CCB also takes the responsibility to safeguard the Mojaloop Family of API specifications so that it upholds the Level One Principles. As part of maintenance, the CCB considers, debates critical feature requests and change requests generic enough to be part of the Specification itself and after deliberation decides whether to accept them or not. If agreed upon by the group, these changes are implemented and deployed as well, as per

Change Control Board Chair: Samuel Kummary, Program Lead, ModusBox