Release Notes

Release Notes

What’s changed?

v2.0-draft4

Business rules updates

Technical specification updates

Section

Subsection

Description

Section

Subsection

Description

1

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961416

Claims schema

Added FullName to the personal Claims object

This is to align with Ozone Connect

2

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961416

Claims schema

Added definition for personal Claims schema to clarify that “An LFI MUST provide both GivenName and Surname for a Retail customer“

3

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361960882

ExtendedPurpose schema

Updated definition of ExtendedPurpose which is used for non-domestic payments - to clarify that the ExtendedPurpose "Specifies the purpose of an international payment."

4

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961528

x-fapi-customer-ip-address header

Added the x-fapi-customer-ip-address as a mandatory header field in the following API operations:

  • GET /products

  • POST /leads

As a means to identify whether the User is present when the TPP makes an API call to the LFI.

5

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961528

Links

In addition to the ApplicationUri - have added these fields for LFIs to represent application processes other than an application link:

  • ApplicationPhoneNumber

  • ApplicationEmail

  • ApplicationDescription

6

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961528

ResidentialAddress

Updated to reflect revised properties for address.

7

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961528

POST /leads

Made the EmiratesId mandatory in the creation of a lead

8

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961528

POST /leads

Added a MarketingOptOut flag as a mandatory field for the creation of a lead

9

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961065

post /accounts

Changed request payload to incorporate JWS properties.

Added Webhook support.

10

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961004

patch /fx-quotes/{QuoteId}

Added QuoteReference, Commission, and Trade properties to request payload.

Changed request payload to incorporate JWS properties.

Added Webhook support.

11

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961004

post /fx-quotes

Updated Links section to include links required by user experience.

12

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361962348

All

Updates to reflect mandatory, optional, and supported properties across quotes and data sharing.

Changed patch request payload for quotes to incorporate JWS properties.

Added Webhook support for accepted quotes.

13

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361957218

post /par

Updated insurance consent to reflect revised permissions structure and values.

14

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961037

All

Created to support comprehension of https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961065

15

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361960976

All

Created to support comprehension of https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961004.

16

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361962312

All

Updates API Guide to reflect revisions to API operations.

v2.0-draft3

Business rules updates

Technical specification updates

Section

Subsection

Description

Section

Subsection

Description

1

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961416

Error Response

Standardised Error Codes across the specifications:

  • Appropriate Code enumerations matched to HTTP Status

  • Error body only for 400, 403 and 500

  • Error Code values are extendable based on a namespaced pattern where “the namespace is the system or organisation that has responded with the error, and the code is the code specific to the system or organisation."

2

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961416

AEExternalAccountSubTypeCode

Added AccountSubType Code values for Credit Card, Mortgage and Personal Loan

Updated to include:

- CreditCard - Mortgage - PersonalLoan
3

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961416

AEExternalAccountIdentificationCode

New enumerations for identifying Credit Cards, Mortgages and Personal Loans:

- MaskedPAN - MortgageReference - PersonalLoanReference
4

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961416

AEProduct

Extended Product API endpoint to include a flag for IsSecured

5

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961416

AETransaction

Extended Transaction API endpoint to include flag for IsPrimaryInstrument to flag if the transaction was created using the primary instrument.

6

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961416

AEPartyIdentityAssurance2

Extended /accounts/{AccountID}/parties endpoint to accommodate Business accounts:

  • New PartyCategory to flag Retail, SME or Corporate

  • New CorporateClaims object

  • Claims can either be a personal claim or a CorporateClaims

7

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961416

AEPartyIdentityAssurance4

Extended /parties endpoint to accommodate Business accounts:

  • New PartyCategory to flag Retail, SME or Corporate

  •  

8

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961561

Error Response

Standardised Error Codes across the specifications:

  • Appropriate Code enumerations matched to HTTP Status

  • Error body only for 400, 403 and 500

  • Error Code values are extendable based on a namespaced pattern where “the namespace is the system or organisation that has responded with the error, and the code is the code specific to the system or organisation."

9

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961561

Services

Services may now be extended with a namespaced enumeration for LFI specific services

10

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961561

LocationCategory

LocationCategory extended to include DriveThru

11

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961561

Links

Links object for extending fees links

12

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361960882

Error Response

Standardised Error Codes across the specifications:

  • Appropriate Code enumerations matched to HTTP Status

  • Error body only for 400, 403, 409 and 500

  • Error Code values are extendable based on a namespaced pattern where “the

13

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361960882

RejectReasonCode

New RejectReasonCode to relay errors from systems rejecting the payment.

Code: description: | Rejected Reason Code is a namespaced rejection reason code. The first part of the code is the namespace, which is the name of the organisation or system (e.g., AANI) that is rejecting the payment, and the second part is the specific rejection reason code for the originating organisation or system. Payments that are rejected by AANI will have the AANI prefix, followed by the specific ANNI reason code. The Payment resouce is updated with the rejection reason code if a Rejected payment is initially created in a Pending state. If the Payment resource is rejected, and no Payment resource is created - a 4xx HTTP status code is returned to the TPP with the appropriate Error Response. type: string pattern: ^[A-Za-z]+\.[A-Za-z]+$ Message: $ref: "#/components/schemas/AEMessage"
14

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361959594

Error Response

Standardised Error Codes across the specifications:

  • Appropriate Code enumerations matched to HTTP Status

  • Error body only for 400, 403, 409 and 500

  • Error Code values are extendable based on a namespaced pattern where “the

15

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961528

Error Response

Standardised Error Codes across the specifications:

  • Appropriate Code enumerations matched to HTTP Status

  • Error body only for 400, 403, 409 and 500

  • Error Code values are extendable based on a namespaced pattern where “the

16

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961528

MortgageDetails.Limits

Extending to allow a Percentage

17

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361957181

Error Response

Standardised Error Codes across the specifications:

  • Appropriate Code enumerations matched to HTTP Status

  • Error body only for 400, 403, 409 and 500

  • Error Code values are extendable based on a namespaced pattern where “the

18

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2draft3/pages/321228735/Error+Messages+for+Payment+Initiation?force_transition=468764fd-58aa-49bb-9ae3-6992006c7d4a

Error Messages

Agreed guidance on Errors

19

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361962348

All

Updated quote and data sharing bodies to reflect industry session.

Standardised error codes as above.

20

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961065

All

Updated party data based on changes to Account Information API.

Updated status codes.

Standardised error codes as above.

21

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv2dot0final/pages/361961004

All

Updated party data based on changes to Account Information API.

Updated status codes.

Standardised error codes as above.

v2.0-draft2

Technical specification updates

  • Added the ATM Data OpenAPI specification

v2.0-draft1

 

v1.2

These are the changes that have been introduced in v1.2 from v1.1

Business rules updates

Technical specification updates

  • New Open Finance Product API specification for

    • Leads - for TPPs to send information about leads to LFIs

    • Products - for TPPs to retrieve product information from LFIs

  • Updated Standing Orders fields from mandatory to optional - FinalPaymentDateTime, NumberOfPayments, FinalPaymentAmount - as these are not available in all cases

  • Updated references in the OpenAPI specification from “IPP” to “Aani Core”

  • Clarified in OpenAPI specification that the AEExchangeRateInformation object is returned by the LFI

v1.1

These are the changes that have been introduced in v1.1 from v1.0

Business rules updates

Errata version

Section

Subsection

Impacts

Description

Action

Errata version

Section

Subsection

Impacts

Description

Action

1

2

Bank Service Initiation

Single Instant Payments

LFIs

TPPs

The Open Finance Standards do not offer a prototype of a Single Instant Payment flow.

A prototype illustrating an example of a Single Instant Payment flow has been created.

TPPs and LFIs should use this prototype in conjunction with the prescribed customer experience screens.

2

2

Common Components

https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1final/pages/151847164#UserExperiencePrinciples-11.-Other-Rules-for-User-Journeys

LFIs

TPPs

All Customer Experience sections currently provide branded screens without stipulation of whether these are illustrative or prescriptive.