How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Vanquis Bank Confirmation of Funds API (CBPII)

Vanquis Bank's OBIE Read/Write Confirmation of Funds API (CBPII), conformant to the Open Banking Implementation Entity Read/Write API Standard v3.1.10. Allows authorised Card Based Payment Instrument Issuers to confirm the availability of funds on a customer account with consent, secured under the PSD2 / FAPI profile (OAuth2/OIDC, mutual-TLS, SCA). The production host is provisioned per TPP during Open Banking Directory onboarding and is not publicly published; the harvested OpenAPI is the shared OBIE standard contract, not a Vanquis proprietary document.

Vanquis Bank Confirmation of Funds API (CBPII) is one of 4 APIs that Vanquis Banking Group publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Confirmation of Funds, CBPII, and Open Banking. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 3 paths, and defines 9 schemas. It is described by OpenAPI 3.0.0, at version 3.1.10.

Requests are made against a single base URL, /open-banking/v3.1/cbpii.

4 operations 3 paths 9 schemas 1 DELETE1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
3.1.10
Server
/open-banking/v3.1/cbpii
Authentication
OAuth 2.0, OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 2

Vanquis Bank Confirmation of Funds API (CBPII) declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (TPPOAuth2Security) using the clientCredentials flow, exposing 1 scope. It supports OAuth 2.0 (PSUOAuth2Security) using the authorizationCode flow, exposing 1 scope.

  • TPPOAuth2Security — TPP client credential authorisation flow with the ASPSP
  • PSUOAuth2Security — OAuth flow, it is required when the PSU needs to perform SCA with the ASPSP when a TPP wants to access an ASPSP resource owned by the PSU

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Funds Confirmations 4
POST
/funds-confirmation-consents
Create Funds Confirmation Consent
CreateFundsConfirmationConsents 5 params body → 201400401403405406415429
GET
/funds-confirmation-consents/{ConsentId}
Get Funds Confirmation Consent
GetFundsConfirmationConsentsConsentId 6 params → 200400401403405406429500
DELETE
/funds-confirmation-consents/{ConsentId}
Delete Funds Confirmation Consent
DeleteFundsConfirmationConsentsConsentId 6 params → 204400401403405406429500
POST
/funds-confirmations
Create Funds Confirmation
CreateFundsConfirmations 5 params body → 201400401403405406415429

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Links (5 properties), OBErrorResponse1 (4 properties), OBError1 (4 properties), OBFundsConfirmationConsentResponse1 (3 properties). Each schema is shown below with its type and property counts.

ISODateTime
string
All dates in the JSON payloads are represented in ISO 8601 date-time format. All date-time fields in responses must include the timezone. An example is below:…
Links
object
Links relevant to the payload
5 properties 1 required
Meta
object
Meta Data relevant to the payload
3 properties
OBError1
object
4 properties 2 required
OBErrorResponse1
object
An array of detail error codes, and messages, and URLs to documentation to help remediation.
4 properties 3 required
OBFundsConfirmation1
object
1 property 1 required
OBFundsConfirmationConsent1
object
1 property 1 required
OBFundsConfirmationConsentResponse1
object
3 properties 1 required
OBFundsConfirmationResponse1
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

obie-confirmation-funds-openapi.yaml Raw ↑

Other APIs Vanquis Banking Group publishes across the network.

Vanquis Bank Account and Transaction API (AIS)
Vanquis Bank Payment Initiation API (PIS)
Vanquis Bank Dynamic Client Registration API
Where this information came from

This is an independent, third-party profile of Vanquis Bank Confirmation of Funds API (CBPII), published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.