Expand | ||||
---|---|---|---|---|
| ||||
|
Note |
---|
This is a draft of the UAE Open Finance Standards. It is intended for review only, not for implementation. |
1. What's new?
New functionality and specifications have been added in relation to the following:
Centralized Authentication and Authorization – UAE Pass. https://openfinanceuae.atlassian.net/wiki/x/KoSFBg
Operational Guidelines - Common Rules and Guidelines
2. What’s changed?
Updated Bank Service Initiation API - OpenAPI Documentation with:
Made
ConsentSchedule
optional inMultiPayment
consent - to facilitate Payments with Delegated AuthorizationRemoved
UAEOF.Passport
as an option forAERiskExternalAccountIdentificationCode
Added
IsBeneficiaryConfirmed
,AuthenticationChannel
andMerchantCategoryCode
as fields in theRisk
objectAdded
ConfirmationOfPayeeResponse
to PII data for Payments Rich Authorization Request as proofs that Confirmation of Payee has taken place
Updated Business Rules for COP in https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft5/pages/109413626/Single+Instant+Payment#3.4-Using-Confirmation-of-Payee-(COP) to align BRs with the new COP API Design
Updated the Common Rules and Guidelines page to include additional information in relation to the usage of the Risk Information Block in https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft5/pages/109415230/Common+Rules+and+Guidelines#9.-Risk-Information-Block.
Request to Pay. (NOTE: This page has been redacted from this draft as further work is required on this topic)
Proxy account identification. Specifying account identification using a proxy has been has been redacted from this draft.
3. What's to come?
The next publication on will be a release candidate. It will include feedback from engagement cycle 3 & 4 as well as all of the following functionality and specifications:
...