Following the sandbox implementation of the payments BB in February 2024, discrepancies below were noted in the spec and subsequently updated in this version.
Section 4: Key Digital Functionalities
4.10 Changes: Modification of the scheduling services in the payments BB; i.e., to enable internal functionalities like bulk processing of payments.
Section 5: Cross-cutting requirements
5.18 Change of eligibility verification from recommended to required
5.2.3 Inclusion of the recommended requirements for reporting services into cross-cutting requirements:
The data store will be write-only from the core service and should be read-only by external components (RECOMMENDED)
The data model on the reporting data store can be different from the internal operational data models that the switch uses (RECOMMENDED)
The component provided by the switch will translate internal events and internal data models to the external data store models. This component can be replaced (RECOMMENDED)
Section 6: Functional requirements:
6.10 Removal of the "Regular and repeat payments are scheduled (REQUIRED)" from Scheduling Services as this is done outside the payments BB.