Openbanking APIs

5 APIs81 Endpoints2 Categories

API Catalog

Account and Transaction API Specification

The UK Open Banking Account and Transaction API (AISP) is the standard interface that account-information service providers use to read PSU bank data from regulated UK banks. It defines 29 endpoints covering account access consents, account lists, balances, transactions, beneficiaries, direct debits, standing orders, statements, products, and parties. The flow uses two OAuth 2.0 schemes: TPP client credentials for consent setup and PSU authorization-code SCA for resource access. Every ASPSP that complies with the standard exposes the same operations under their own /open-banking/v4.0/aisp base path.

29 endpoints

Confirmation of Funds API Specification

The UK Open Banking Confirmation of Funds (CBPII) API lets a card-based payment instrument issuer ask a bank whether sufficient funds are available on a PSU's account for a specific amount. The 4-endpoint surface covers creating, retrieving, and revoking funds-confirmation-consents plus the actual /funds-confirmations check. The PSU first authorises the consent under PSUOAuth2Security, then the CBPII calls /funds-confirmations under TPPOAuth2Security with the consent ID. The response is a yes/no flag, not the actual balance.

4 endpoints

Event Notification API Specification - TPP Endpoints

The UK Open Banking Event Notification API (TPP endpoints) defines how a TPP receives push notifications from a UK ASPSP about consent and resource events. The single endpoint, POST /event-notifications, accepts a Security Event Token (SET) per RFC 8417 from the bank and is secured with TPPOAuth2Security using client_credentials. Events typically cover consent revocations, resource changes, and other lifecycle signals so the TPP no longer needs to poll consent state.

1 endpoints

Open Data API

The UK Open Banking Open Data API publishes machine-readable directory information about UK bank branches, ATMs, personal current accounts, business current accounts, commercial credit cards, and unsecured SME loans across the nine CMA9 banks. The data covers product features, fees, eligibility criteria, and physical access points such as branch addresses and ATM locations. It is a public, unauthenticated dataset designed to power product comparison sites, branch finders, and accessibility tools without exposing customer data. Coverage spans HSBC, Barclays, Lloyds, NatWest, Santander, RBS, Bank of Ireland, Danske, and Nationwide.

6 endpoints

Payment Initiation API

The UK Open Banking Payment Initiation API (PISP) lets authorised Third Party Providers create and manage account-to-account payments directly from a customer's bank account under PSD2. It covers domestic, domestic scheduled, domestic standing order, international, international scheduled, international standing order, and file payments, each with its own consent, payment, and status resources. Strong Customer Authentication is enforced via redirect or decoupled flows, and TPPs authenticate to the bank with mTLS plus OAuth 2.0 client credentials. This is the spec implemented by every CMA9 bank in the UK.

41 endpoints

Connect Your Agent

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.