...
The following errata is to be read and implemented in in conjunction with https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1final.
The Clarification Action 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
or | Status |
|---|
| colour | Green |
|---|
| title | No Update |
|---|
|
to the next published version of the Standards. | Section | Subsection | Description | Clarification | StatusAction |
|---|
| 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.| Status |
|---|
|
| colour | Red |
|---|
title | 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.| Status |
|---|
| colour | Red
|---|
| title | 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. | |
| 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.status |
|
| 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.| Status |
|---|
|
| colour | Red |
|---|
titleUpdate | | 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.| Status |
|---|
|
| colour | Red |
|---|
title | 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.| Status |
|---|
|
| colour | Red |
|---|
title | 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.| Status |
|---|
|
| colour | Red |
|---|
title | Update