Introduction to Account Information APIs (AIS)

This module adopts the common standards for collaboration between banks and other players within the banking eco-system of third parties such as developers, customers and partners like FinTechs, telecoms, retailers or other banks. The Account Information APIs is part of the much wider legislative push – CDR (Customer Data Rights).

This module contains Cuscal specific APIs which provide information on customer, account, beneficiary, scheduled payments, direct debits and transaction details. The solution in integrated with Cuscal and consent is managed by Cuscal.

The API version is the B2B-Reference-API-v1.0.11

The Temenos solution is capable of providing a connection to the outside world ADR (Accredited Data Recipient), by way of exposing web services in the form on APIs, utilising a third party API gateway (Cuscal).

A key technological component and part of the above architecture diagram is the Interaction Framework:

Temenos Interaction Framework provides an API platform to enable a flexible network of applications. It facilitates the creation of APIs to expose services available in multiple underlying business systems to any user interface provider. The Interaction Framework provides APIs for interacting with Temenos services based on the REST and JSON standards and rely on API specification (SWAGGER).

Provider APIs are building blocks that expose Temenos platforms as RESTful APIs defined in API specification, Swagger. Published APIs are pre-defined, publiclyexposed APIs that implement standard API definitions.

In Australia, the request from the ADR (Accredited Data Recipient) will first reach the API Gateway (Cuscal) that handles the consent management, meaning if a consent is set-up for an ADR, it is set-up in the Cuscal database.

Temenos Transact acts as the data holder and shares the list of accounts to Cuscal for the purpose of consent creation and its management for a customer.

When a customer invokes an API request through an ADR, it first reaches Cuscal / IB Manager wherein the customer is identified. This identification is not within the scope of Temenos Transact.

Before any consent is created in Cuscal, Cuscal will make a call to Temenos Transact to get the list of accounts that belong to the identified customer. The list will contain the sharable and the non-sharable accounts and a consent will only be created on the sharable accounts. Non-sharable accounts are only provided for information purpose. Accounts are marked as sharable or non-sharable in Temenos Transact. If the account is passed as non-sharable in the response by Temenos Transact, it is presumed that Cuscal will not share the details of that account with any ADR.

New APIs have been created to facilitate the interaction between the third-party intermediary CUSCAL and Temenos Transact. The requests from the ADR will reach the CUSCAL first and then will be forwarded to Temenos Transact.

This functionality allows banks to retrieve the details of accounts, account balances, customers, direct debits, payees, schedule payments and transactions records for the AUOBPZ module.

The following items have been released as part of this functionality:

• The AUOBPZ.API.ACCOUNT.BALANCES.1.0.0 enquiry has been created as part of this functionality to allow users to retrieve the details of a balance for a specific account.
• The AUOBPZ.API.ACCOUNT.DETAILS.1.0.0 enquiry has been created to allow users to retrieve the details of a specific account.
• The AUOBPZ.API.CUSTOMER.DETAIL.1.0.0 enquiry has been created to allow users to retrieve the basic information of a specific customer.
• The AUOBPZ.API.ACCOUNT.DIRECTDEBITS.1.0.0 enquiry has been created to allow users to retrieve a list of specific accounts that contains details of the direct debits.
• The AUOBPZ.API.PAYEE.DETAILS.1.0.0 enquiry has been created to allow users to retrieve detailed information for all payees of a particular customer.
• The AUOBPZ.API.SCH.PYMT.ACCOUNT.1.0.0 enquiry has been created to allow users to retrieve information from all the standing orders related to a specific account.
• The AUOBPZ.API.TRANSACTIONS.1.0.0 enquiry has been created to allow users to retrieve detailed information for a transaction related to a specific account.
• The AUOBPZ.API.CUSTOMER.ACCOUNT.1.0.0 has been created to allow users to retrieve the list of consented and non-consented accounts related to a specific customer.

• The accountOwnership field has been added to the NOFILE.AUOBPZ.API.ACCOUNT.BALANCES.1.0.0 and NOFILE.AUOBPZ.API.ACCOUNT.DETAILS.1.0.0 enquiries to allow a Data Recipient to know how many customers hold the account, for example, are classified as direct beneficiaries of the account.

Joint Holders

The Australian Competition and Consumer Commission (ACCC) is the regulator of the CDR. Now banks can choose to share their banking data with third parties accredited by the (ACCC), the accredited data recipients that must meet strict the requirements to receive data. The ACCC has mandated the banks to participate in bank data exchange.

This functionality allows banks to manage the joint account holders and secondary users, to provide their non-disclosure option or nominate secondary users, to give authorization for accounts to share data.

Also, banks are able to manage the details of the overall data sharing status of the open banking accounts and create, revoke the customers relationship based on the nomination status.

The following items have been introduced with this functionality:

• The AUOBPZ.DOMS,AUOBPZ.BEN.NON.DISCLOSURE.OPTIONS version has been created to edit the non-disclosure details.
• The NOFILE.AUOBPZ.API.BEN.DISCLOSE.DETAILS.1.0.0 enquiry has been created to retrieve the details of the non-disclosure option for a particular customer.
• The AUOBPZ.NOMINATIONS,AUOBPZ.CUST.NOMINATIONS version has been created to edit the nominations provided for or by, the secondary customers linked to the account.
• The NOFILE.API.CUST.NOMINATIONS.1.0.0 enquiry has been created to retrieve the details of the nominations provided for or by, the secondary customers.
• The AUOBPZ.CUST.NOMINATION.STATUS,AUOBPZ.NOM.STATUS version is used to manage the details of customer relationship based on the nominations status of the open banking accounts.
• The NOFILE.AUOBPZ.API.CUST.REL.PROFILES.1.0.0 enquiry has been created to retrieve the details of the secondary user's related profiles, for the accounts to which are linked.
• The AUOBPZ.ACCT.DATASHARE,AUOBPZ.API.ACCT.DATASHARE.STATUS.1.0.0 version is used to create or update the details of the overall data sharing status.

Click here to understand the terms and abbreviations used in this module.