This API, provides the ability for approved/authorised account information service providers (AISPs) to access a customer’s (payment service user, PSU) account and transaction information for business current accounts (BCAs) and Personal Current Accounts (PCAs), Credit Cards, Savings Payment Accounts and Multi-Currency Payment Accounts only when the PSU grants consent. This API is developed according to the Open Banking Read/Write API Specifications and fulfils PSD2 regulation. see https://www.openbanking.org.uk

Key Features:

• List of Transactions: Debits, Credits, Value, Description, TransactionID, Status, BookingDateTime
• Account details: Account Type and Account Subtype, Overdraft information
• Balances
• Saved payees
• Recurring payments: Direct Debits, Standing Orders
• Product Details
• Offers
• Statements
• Account Holder Name

New in this version:

• We are introducing a new /transactions endpoint field called “mutability” which allows you to distinguish between transactions whose description and other details might be subject to change (“mutable”) against those that are not subject to change (“immutable”).
• We have added the field RepresentativeAPR field in PCA/BCA Product endpoints.

Custom Data Types

For model class "OBExternalAccountIdentification4Code" Santander has introduced a custom data type for Account/SchemeName to identify some Savings Accounts which do not have a numeric sort code account number format named "UK.Santander.SavingsRollNumber"

eg:

• "SAVINGR12345678".

• "SAVING123456789".

What can you do?

Register an intent to retrieve account information by creating an "account request". This registers the data "permissions", expiration and transaction history timeframe the PSU has consented to provide to the AISP.

This subsequently allows the AISP to retrieve account and transaction data for that PSU.

Authorisations to AISPs will be available to review or stop by the PSU through online banking.

Who can have access to the API?

Access to the Account Information API is limited to approved/authorised AISPs, using eIDAS certificates. Approval and authorisation is managed by the Financial Conduct Authority in the UK (FCA, see https://www.fca.org.uk/ and other relevant competent authorities across the EU. Approved/Authorised organisations should then be enrolled to use the Open Banking Directory. By successfully accomplishing these prerequisites, an AISP will obtain the necessary digital identities and certificates which enable organisations to securely connect and communicate via the Open Banking Security Profile (OIDC) in a standard manner and to best protect all parties within the Open Banking ecosystem.