2025-12-19 Payments BB Meeting notes

Change Requests and GitBook Issues

@David Higgins

It was confirmed that:

• The issue encountered in the previous meeting was not related to workflows but to missing or unstable API documentation sections.

• GitBook intermittently failed to render content correctly, causing newly added sections (notably G2B APIs) to disappear or not load for some users.

• No new APIs were introduced; all workflows rely on existing Payments BB APIs.

G2B / B2G Scope and Release Decision

All

The group agreed that:

• G2B and B2G changes are still under discussion and should not be included in the immediate release.

• The next release should proceed with already-reviewed content (notably multi-currency related updates).

• G2B/B2G content will continue to evolve in parallel and be reviewed in a subsequent meeting.

Release Planning and Versioning

@Mauree, Venkatesen @Ali González

The upcoming Payments BB release will be version 2.0, as certain changes constitute breaking changes (e.g. requirement classification).

Release branches must only include finalized and agreed changes.

No merging should occur until outstanding release questions are resolved.

Documentation Structure and Formatting

@Ali González

Ali proposed converting requirements from table format to header + paragraph structure to:

• Improve requirement linkability (URI-based references).

• Ensure compatibility with the requirements parser.

Agreement was reached that:

• Section 5.3 remains the core technical requirements section.

• Mobile payments, voucher management, and bulk payments remain subsections under 5.3.x.

• Mobile money and voucher support are required features of the Payments BB, even if not all countries implement them operationally.

Terminology was aligned to use “Required” instead of “Mandatory”.

Version History Consolidation

@Kibuuka, Arnold @Ali González

Agreed approach:

• Version history will be consolidated.

• The next publication will clearly reflect v2.0.

• Minor inconsistencies will be resolved without blocking the release.

Review Process and Next Steps

ALL

1. All stakeholders must review the change requests before approval.

2. Links to all relevant change requests will be circulated by email.

3. Feedback will be requested ahead of the January meeting