You are viewing an old version of this page. View the current version .
Compare with Current
View Page History
Version 1
Next »
Document Title
Open Finance Standards v1.0-final-errata1
Publication Date
12 Aug 2024
Classification
PUBLIC
The following errata is to be read and implemented in in conjunction with https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1final/overview .
The Clarification column indicates the action required by implementers from TPPs and/or LFIs for each errata.
The Status column indicates whether each errata will require an UPDATE or NO UPDATE to the next published version of the Standards.
Section
Subsection
Description
Clarification
Status
1 Common Components
Pushed Authorization Request Endpoint OpenAPI
The PeriodSchedule shows all 3 schedule types - DefinedSchedule, FixedPeriodicchedule and VariablePeriodicSchedule as being as mandatory instead of “oneof”
Implementers should follow the specification as per uae-bank-initiation-openapi.yaml.
The specification in uae-pushed-authorization-endpoint-openapi.yaml will be updated in the next version.
UPDATE
2 Common Components
Pushed Authorization Request Endpoint OpenAPI
The optional Type string field within the VariablePeriodicSchedule object (MultiPayment) is no longer applicable and should have been removed.
Implementers should follow the specification as per uae-bank-initiation-openapi.yaml.
The specification in uae-pushed-authorization-endpoint-openapi.yaml will be updated in the next version.
UPDATE
3 Common Components
Pushed Authorization Request Endpoint OpenAPI
The MultiPayment object shows the Amount object as being as mandatory instead of optional.
Implementers should follow the specification as per uae-bank-initiation-openapi.yaml.
The specification in uae-pushed-authorization-endpoint-openapi.yaml will be updated in the next version.
UPDATE
4 Common Components
Pushed Authorization Request Endpoint OpenAPI
The MultiPayment object shows the MaximumIndividualPaymentAmount object as being as mandatory instead of optional.
Implementers should follow the specification as per uae-bank-initiation-openapi.yaml.
The specification in uae-pushed-authorization-endpoint-openapi.yaml will be updated in the next version.
UPDATE
5 Common Components
Pushed Authorization Request Endpoint OpenAPI
The Subscription object and the Webhook object are shown as being as mandatory instead of optional.
Implementers should follow the specification as per uae-bank-initiation-openapi.yaml.
The specification in uae-pushed-authorization-endpoint-openapi.yaml will be updated in the next version.
UPDATE
6 Common Components
Pushed Authorization Request Endpoint OpenAPI
The enumerations listed within the AccountSubType parameter reflect the legacy list of account sub types instead of CurrentAccount and Savings
Implementers should follow the specification as per uae-bank-initiation-openapi.yaml.
The specification in uae-pushed-authorization-endpoint-openapi.yaml will be updated in the next version.
UPDATE
7 Common Components
Pushed Authorization Request Endpoint OpenAPI
Within the FilePayment object, the RequestedExecutionDateTime parameter should have been renamed to RequestedExecutionDate
Implementers should follow the specification as per uae-bank-initiation-openapi.yaml.
The specification in uae-pushed-authorization-endpoint-openapi.yaml will be updated in the next version.
UPDATE
8 Banking
Common Rules and Guidelines
Within Section 15. Payment Status Update CRG-15.8 references the payment status model as GRC 15.12 instead of GRC-15.10
This is an errata reference issue only and has no functional impact. The reference will be updated in the next version.
UPDATE