Requesting Account Information (AIS)

OBIE defines the "Account Information Service" as an online service to provide consolidated information (balance, transaction history) on one or more payment accounts held by a PSUClosedPayment Services User – an individual person or legal business entity making use of an Open Banking service as a payee, payer or both. with one or more payment service providers.

As it relates to an AISPClosedAccount Information Service Provider – a TPP authorised to access consumer or business account data from the account holder's financial institutions with the account holder's explicit consent., this essentially means that, under open banking protocols, banks allow access to a customer's account data by TPPs only if the customer (PSU) explicitly gives consent (grants permission) to let the bank allow such access.

The scope of analysis and service the bank supports includes comparing a PSU's accounts and transaction history to a range of financial service options, aggregating data across participating financial institutions and customers to create marketing profiles, and making new transactions and account changes on the PSU's behalf.

API support for accessing a PSU's account information institutes a communications flow that ensures all regulations for PSU consent and authorisation are met.

Pictured above (hover to enlarge) is the general flow. Guidance on making the appropriate POST and GET calls, as well as handling the bank's responses to these requests is covered next.

Base URLs

See Base URLs.

Headers

See Common Request Headers.

Typically, the bank requires a user ID as the first step of the credentials exchange necessary to identify the user. Additional details may be required, as well.