2026-08-24 Meeting notes

2026-08-24 Meeting notes

 Date

Sep 10, 2026

 Participants

  • Kibuuka, Arnold

  • Mauree, Venkatesen

  • Ali González

  • David Higgins

  • Oscar Correia

 Goals

  • Review whether the revised Payments Building Block requirements are moving in the right direction. 

  • Validate proposed requirement text, classifications, and placement across key digital functionalities. 

  • Agree the approach and timeline for completing review comments and restructuring the specification. 

 Discussion topics

Topic

Presenter

Notes

Topic

Presenter

Notes

Progress since the previous meeting 

    • Kibuuka, Arnold recapped the work completed with Mauree, Venkatesen since the previous meeting. The team revised requirement wording, added or refined requirement levels, and populated mutability and observability classifications in the workbook. 

    • Duplicate or overlapping requirements previously identified by Oscar Correia and David Higgins were removed, combined, or rewritten where appropriate. 

    • The shared workbook was reposted in the meeting chat so participants could review the current working version. (Payments BB - Govstack 2.0 - Google Sheets)

Review assignments and open specialist inputs



  • Oscar Correia had substantially completed the mutability and observability review for Voucher Management. 

  • David Higgins confirmed that his assigned areas included Payment Request Initiation and Account Lookup Services. Payment Orchestration was also identified as an area requiring his review. 

  • Additional input was requested on the Information Mediator wording, the consolidation of event notifications and audit logging, and whether the revised requirements were positioned correctly. 

  • Because some participants had not yet completed their review, Mauree, Venkatesen proposed collecting comments by email and allowing approximately two weeks before reconvening. 

  • Ali González confirmed that the working group is moving in the right direction, particularly where cross-functional requirements have already been removed or crossed out. 

  • Oscar Correia asked whether reviewers could comment beyond their formally assigned sections. Mauree, Venkatesen confirmed that feedback across all components is welcome, while scoped assignments remain useful for distributing the workload. 

Requirement validation and workbook updates

 

  • Mauree, Venkatesen requested validation of revised text and entries marked as proposed in the attached requirements workbook, including the mutability and observability assessments. 

  • Reviewers should make corrections directly in the workbook.

  • The workbook shows active review areas across Payment Orchestration, Voucher Management, Account Lookup Services, Payment Request Initiation, Batch Processing, Bulk Payment Service, logging, reconciliation, security, and the API Management Gateway. 

  • Oscar Correia had previously been assigned Voucher Management, but may review all components and provide broader feedback. 

  • David Higgins confirmed that he had entered feedback against two tagged sections and would review the full document for alignment between sections. 

  • Mauree, Venkatesen specifically asked David to validate the Bulk Payment Service and Batch Processing descriptions against the implementation approach. 

API Gateway and Information Mediator

 

  • David Higgins clarified that the API Gateway and Information Mediator are separate functions. 

  • The Information Mediator supports interoperability, while the API Gateway is needed by the building block to interact with it and to validate incoming inputs. David stated that input validation is not performed by the Information Mediator. 

  • This clarification supports retaining API Gateway requirements in the Payments Building Block, including authentication, request validation, quotas or throttling, call logging, and standardized error responses reflected in the workbook. 

  • Ali González will propose a new format that reorganizes existing content by key digital functionality rather than distributing one functionality across separate chapters for functionalities, requirements, data structures, APIs, and workflows. 

  • Under the proposed model, each functionality would be presented in one place with its purpose, requirements, relevant workflows, service APIs, and supporting information. 

  • Ali will prepare an example using an existing functionality to demonstrate the proposed structure and clarify how current material would be consolidated. 

 Action items

Ali González Prepare and circulate a proposal and worked example for the new specification format organized by key digital functionality. 
David Higgins Review the full requirements workbook for alignment across sections, with priority on Bulk Payment Service, Batch Processing, and the relationship between API Gateway and Information Mediator. 
Oscar Correia Review Voucher Management and provide comments on any other components where feedback is relevant. 

 Decisions

  1. The next meeting was agreed for 9 September 2026 at 4:00 p.m. Geneva time after 8 September was ruled out because of a webinar conflict. 
  2. Review will proceed by key digital functionality, allowing each functionality and its associated requirements to be completed systematically. 
  3. Reviewers may comment across the complete workbook, notwithstanding previously assigned focus areas. 
  4. The API Gateway and Information Mediator will be treated as separate functions; the API Gateway remains responsible for input validation at the building-block boundary. 
  5. The specification will move toward a functionality-centered format that brings the functionality description, requirements, workflows, APIs, and related material together. 

 Related info