Openbanking Confirmation of Funds API Specification

Name: Confirmation of Funds API Specification API
Brand: Confirmation of Funds API Specification
Availability: InStock

Browse all Openbanking APIs

✓ Official Vendor SpecFinanceBankingoauth24 Endpoints

Install Jentic One Beta

Connect the Confirmation of Funds API Specification to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Confirmation of Funds API Specification, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

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.

Capabilities

What an agent can do with Confirmation of Funds API Specification API.

Create a funds-confirmation-consent that the PSU then authorises for a specific account

Retrieve the state of a funds-confirmation-consent before using it

Submit a /funds-confirmations request with an amount and currency to receive a yes/no funds flag

GET STARTED

Start building with Confirmation of Funds API Specification API

Explore with Jentic

View OpenAPI Document

For Agents

Check whether a UK bank account has sufficient funds for a given amount via the regulated CBPII standard's 4 endpoints, with consent-scoped OAuth 2.0.

Use for: Create a funds confirmation consent, Check whether an account has enough funds for a payment, Retrieve the state of a funds confirmation consent, Revoke a funds confirmation consent

Not supported: Does not return balances, transactions, or initiate payments - use for yes/no funds availability checks (CBPII) only.

Use Cases

Patterns agents use Confirmation of Funds API Specification API for, with concrete tasks.

★ Card Pre-Authorisation

Card-based payment instrument issuers (CBPIIs) check whether a linked UK bank account holds enough funds before authorising a card transaction. After the PSU authorises the funds-confirmation-consent, the CBPII calls /funds-confirmations with the proposed amount and currency. The bank returns a yes/no flag rather than a balance, keeping disclosure minimal.

POST to /funds-confirmations with the consent ID, instructedAmount.amount='150.00', and instructedAmount.currency='GBP', then read the FundsAvailable boolean from the response.

Buy-Now-Pay-Later Eligibility

BNPL providers acting as CBPIIs validate that a customer's nominated UK bank account can fund the next instalment before approving a purchase. The standard returns only a yes/no funds flag, which satisfies regulator requirements for minimal data exposure while still letting the BNPL provider make a credible affordability decision in the moment.

Call POST /funds-confirmations with the BNPL instalment amount, capture FundsAvailable, and decline the application if the flag is false.

Consent Lifecycle for CBPII

Manage the lifecycle of funds-confirmation-consents from creation through revocation so the PSU stays in control. The agent creates a consent with POST /funds-confirmation-consents, stores the ConsentId, surfaces the consent in the user's settings, and revokes it via DELETE when the user opts out.

Create the consent with POST /funds-confirmation-consents, then on user opt-out call DELETE /funds-confirmation-consents/{ConsentId}.

AI Agent Funds Check Tool via Jentic

Equip an AI agent with a regulated funds-availability tool through Jentic. The agent searches Jentic by intent, loads the schema for /funds-confirmations, and executes the call with the PSU and CBPII tokens held in your Jentic One instance. The yes/no outcome makes the integration safe for downstream automated decisions.

Use Jentic search 'check whether a bank account has enough funds', load the POST /funds-confirmations schema, and execute with the consent ID, amount, and currency to receive the FundsAvailable flag.

Key Endpoints

4 endpoints — 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.

METHOD

PATH

DESCRIPTION

POST

/funds-confirmation-consents

Create a new funds-confirmation-consent

GET

/funds-confirmation-consents/{ConsentId}

Retrieve the state of a consent

DELETE

/funds-confirmation-consents/{ConsentId}

Revoke a funds-confirmation-consent

POST

/funds-confirmations

Submit a funds availability check

POST

/funds-confirmation-consents

Create a new funds-confirmation-consent

GET

/funds-confirmation-consents/{ConsentId}

Retrieve the state of a consent

DELETE

/funds-confirmation-consents/{ConsentId}

Revoke a funds-confirmation-consent

POST

/funds-confirmations

Submit a funds availability check

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your TPP client_credentials and PSU authorization_code OAuth tokens are stored once, encrypted, by your own Jentic One instance and the right token is selected per operation at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'check whether a bank account has enough funds' or 'set up a funds-confirmation consent', and Jentic returns the matching Confirmation of Funds operation with its ConsentId and amount schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Confirmation of Funds API Specification API through Jentic.

What authentication does the Open Banking CBPII API use?

Two OAuth 2.0 schemes. TPPOAuth2Security uses client_credentials and is what the CBPII uses to call the consent and funds-confirmation endpoints. PSUOAuth2Security uses authorization_code with strong customer authentication so the PSU can authorise the consent. Through Jentic both tokens live in the encrypted vault and are routed per-operation.

Can I check whether an account has enough funds for a £100 payment?

Yes. Once the PSU has authorised a funds-confirmation-consent, POST to /funds-confirmations with InstructedAmount.Amount='100.00' and InstructedAmount.Currency='GBP' along with the ConsentId. The response contains a FundsAvailable boolean - the actual balance is never returned.

What are the rate limits for the Open Banking CBPII API?

Rate limits are set per ASPSP rather than by the standard. Banks publish their CBPII limits in their developer portals; respect HTTP 429 with exponential back-off. Funds checks are typically rate-limited per consent and per minute.

How do I run a funds check through Jentic?

Run the Jentic search 'check whether a bank account has enough funds', select POST /funds-confirmations, load its schema, and execute with the ConsentId, instructedAmount.amount, and instructedAmount.currency. Jentic attaches the TPP token automatically.

Does this API return the account balance?

No. By design, Confirmation of Funds returns only a yes/no FundsAvailable flag. Use the AISP Account and Transaction API instead when the actual balance, transactions, or statements are needed.

How do I revoke a funds-confirmation-consent?

Call DELETE /funds-confirmation-consents/{ConsentId} with a valid TPPOAuth2Security token. The bank then rejects subsequent /funds-confirmations calls that reference that ConsentId.

Can I limit what my agent is allowed to do with the Confirmation of Funds API?

Yes. Because you run your own self-hosted Jentic One instance, your rules decide which operations and credentials the agent may use. This API carries the consent id in the URL path (/funds-confirmation-consents/{ConsentId}), so you can pin the agent to a single funds-confirmation consent and let it create the consent, read its state, and run the yes/no funds check against it. Since you choose the operations, deletion of a consent stays out of reach unless you explicitly allow it.

Openbanking Confirmation of Funds API Specification

Connect the Confirmation of Funds API Specification to your agent

Capabilities

Start building with Confirmation of Funds API Specification API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs