/
Standards v1.2-final-errata1

Standards v1.2-final-errata1

Source Standard

Standards v1.2-final

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

Section

Subsection

Description

Action

1

Confirmation of Payee

Confirmation of Payee OpenAPI

Currently the Confirmation of Payee API requires the TPP to specify GivenName and LastName for personal beneficiary accounts. However, due to the inconsistency of how names are stored across LFIs, it is not always possible to get a match without the FullName.

Furthermore, the current matching algorithm only allows for a full match or no match.

In the Confirmation of Payee OpenAPI specifications the POST /confirmation endpoint will be updated as follows:

For personal accounts, FullName will be added as a mandatory field and both GivenName and LastName will be made optional.

2

Parties

Bank Data OpenAPI


data[].verifiedClaims[].claims.residentialAddress

data[].verifiedClaims[].verification.evidence.documentDetails.issuer.address

data[].verifiedClaims[].verification.evidence.record.source.address

 

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:

Standards v2.0-final-errata1

This change impacts the following objects within the Parties endpoint

data[].verifiedClaims[].claims.residentialAddress

data[].verifiedClaims[].verification.evidence.documentDetails.issuer.address

data[].verifiedClaims[].verification.evidence.record.source.address

Within the above address objects we will:

  1. Repurpose the existing Formatted data field to represent the full address. Specifically Formatted will become a concatenated, human-readable string of the address, based on all the address elements available at the LFI.

  1. Update the field classifications so the only mandatory field will be the forementioned Formatted field all other fields in the address objects will be set to optional. These fields are StreetAddress, Locality, Region, PostalCode, CountryCode.

A knowledge base article will be developed to provide guidance for LFIs on how to populate the formatted fields based on the address elements they store. It will also offer guidance for TPPs on how to consume this updated address object.

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

Description

Page Link

Updated Document

1

Confirmation of Payee OpenAPI

tbc

tbc

2

Bank Data OpenAPI

tbc

tbc

© CBUAE 2025