2023-02-27 Meeting notes - Payments Working group

Rework section 10 - Workflows

@Mauree, Venkatesen

@Oscar Correia

• If a workflow has different options, shouldn't they each be considered a separate workflow?

• Does the level of detail for these workflows contain too much internal payment BB descriptions? Other BBs shouldn't need to know about the internals of how payment systems work

• There is a ton of content here but I'm not sure that this is the right place for it (or if this content really needs to be so detailed)

Comments were not accepted to be reviewed with the poster, it was peoposed that these elements alos listed in the workflow are importnt beaces the payments BB is not the nal repositry for the money as it interacts with other componets like the FSPs.

Pay 86 - Rework section 9 - Service APIs

@Mauree, Venkatesen

@James Dailey

• There should be API definitions for each component - payment switch, account mapping, core banking functionality, etc.

@James Dailey prroposed that there could be a need to have an API that can be used to trigger the payments the API, he also proposed and API for the accounts that the government agencies use.

@Mauree, Venkatesen Added that the triggering and funding of the accounts is dne through the TSA and payemnt scrolls are sent via the bulk API.

@James Dailey it is importat for the payment scrolls and the amounts that are to be disbursed to be on the ame rails to avoid any issues that may arise during reconcilation of the amounts.

@Mauree, Venkatesen added the need to update the diagram in 10.1.1 to remove the internal elements of the payments building block.

@Oscar pointed out that on this issuee the settlemets are out of scopee of the payments building block.

@James Dailey proposed updating the the text in section 2.5 bullet 8 better to address some of the concerns mentioned above better.

@Mauree, Venkatesen to add some text to section 10 option 2 and 3.

@Achim Blume to check with Farouk on section 10 can be revisited especially on how the FMIS interacts with other blocks.

• The APIs are very incomplete – we should have clear APIs defined for core use cases. Mojaloop has well-documented flows that can be used to extract what APIs would be needed. Or can reference the Mifos PaymentHub as well

• 9.1, 9.2, 9.6 - Where are the API endpoints defined?

• 9.3, 9.5 - Use embeded swagger APIs

• 9.4 - We should not reference other unversioned specifications. What happens if mojaloop changes their spec?

• 9.6.6.1 - We don't need to document the status codes unless they deviate from the HTTP standard (which they shouldn't)

@James Dailey that there is need make the sequence diagrams to be more concise and clear before we can have the articulated APIs.

Payments Infrastructure Deploement Scenarrios

• @Mauree, Venkatesen @Oscar Correia @James Dailey proposed that this could be added to the descriptions with the assumptions

• It was agreed to move bullets (1 &2) 4.3 to the crosscuting requirements.

Section 5 - Pay -85

@Oscar Correia to review the functional requirements relating to voucher