Standards v1.2-final-errata1
Source Standard | |
---|---|
Document Title | Standards v1.2-final-errata1 |
Publication Date | Apr 18, 2025 |
Classification | PUBLIC |
The following errata is to be read and implemented in in conjunction with Standards v1.2-final .
The Description column describes the reason for the errata being created.
The Action column indicates what has been done to address the errata and the action required by implementers from TPPs and/or LFIs.
Section | Subsection | Description | Action | |
---|---|---|---|---|
1 | Confirmation of Payee | Currently the Confirmation of Payee API requires the TPP to specify Furthermore, the current matching algorithm only allows for a full match or no match. | In the Confirmation of Payee OpenAPI specifications the
| |
2 | Parties |
| LFIs have informed us that they are unable to support the current address format defined in the Parties endpoint of the standards. To address this, we are implementing a change to offer greater flexibility in how LFIs can provide address information within the Parties endpoint. This adjustment aims to ensure that the existing formatting requirements do not become a barrier to populating this data object. A deeper review of all the addresses within the standards will be made as part of: | This change impacts the following objects within the Parties endpoint
Within the above address objects we will:
A knowledge base article will be developed to provide guidance for LFIs on how to populate the |
The API Hub V6 documentation API Hub Documentation v6 and Ozone Connect API will be updated to support these change.
Attachments
Updated documents pursuant to the errata outlined above will provided below in due course.
Description | Page Link | Updated Document | |
---|---|---|---|
1 | Confirmation of Payee OpenAPI | tbc | tbc |
2 | Bank Data OpenAPI | tbc | tbc |
© CBUAE 2025