Versions Compared

Version Old Version 1 New Version Current
Changes made by

Chris Michael

Chris Wood

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

What's new?

New functionality has and specifications have been added in relation to the following:

  • Business rules and API specifications for International Payments. Please be aware that the current API specification does not allow for a TPP to access an FX rate prior to the user authentication. Although this functionality is included in the business rules for now, its implementation is under consideration and subject to further industry engagement.

  • Business rules and data model for retail motor insurance use cases.

  • Centralized (Federated) Authentication and Authorization.

What’s changed ?

Since the previous draft, the following elements functionality and specifications have been updated:

...

Business rule changes to support Variable Beneficiaries for Multi-Payments.

...

Consent States - How consent moves between these states in its lifecycle.

...

  • Bank Data Sharing API description includes the /parties endpoint to provide details of the User as held by the LFI.

  • Bank Service Initiation API description includes the Refunds endpoint and consent flag that allows debtor account details to be retrieved.

  • Bank Service Initiation API description includes the Bulk/Batch payments operations that allows TPPs to submit a file of payment instructions to an LFI via the OFP.

  • Bank Service Initiation API description references Aani codes rather than ISO 20022 for the property PaymentPurposeCode.

  • Bank Data Sharing and Bank Service Initiation API descriptions have been amended to include a standardised prefix of “AE” for Schema Object names.

  • API description pages have been renamed from “Swagger Documentation” to “OpenAPI Documentation” to provide the correct name of the API description language used.

  • Future Dated Payment has been updated to reflect that FDPs are warehoused and scheculed by LFIs

  • Purpose code has been added to all payment types.

  • https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft3/pages/70092119/Multi-Payments#1.8-Using-Variable-defined-Consent-for-Single-Future-Dated-Payment-(FDP)clarification added in the Multipayments

  • Bank Data Sharing description has been updated to clarify that an LFI may act as a TPP and ingest LFI data, subject to the same rules and guidelines as a TPP.

  • Motor Insurance description has been updated to specify that an LFI is required to return a quote to a TPP regardless of whether there is a commercial agreement in place.

  • Motor Insurance https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft3/pages/70093001/Motor+Insurance+Quotes#7.-Data-Categories have been updated in line with responses from industry participants as to which data fields are available.

What's to come?

Future drafts will include some/all of the following functionality and specifications:

...

  • Fast-track Single Immediate Payments

  • Request to Pay

  • Enhanced Product data

  • Balance Checks

  • Delegated Authentication

  • Bulk/Batch Payments.

  • Confirmation of Payee API design.