The API endpoints described here allow a Card Based Payment Instrument Issuer (CBPII) to: * Register an intent to confirm funds by creating a "funds confirmation consent" resource with an ASPSP, for agreement between the PSU and ASPSP. This consent is a long lived consent, and contains the length of time (expiration date) the customer (PSU) would like to provide to the CBPII, and subsequently make a request to confirm funds are available. * Funds can only be confirmed against the currency of the account. This API is developed according to the Open Banking Read/Write API Specifications and fulfils PSD2 regulation, see [https://www.openbanking.org.uk](https://www.openbanking.org.uk)

Dynamic Client Registration (DCR) API provides the ability for TPP to submit a Software Statement Assertion (SSA) to Santander for the purpose of registering and managing OAuth clients. The TPPs can use this API to * Register a new client * Retrieve the details for a client that has already been registered * Modify one or more attributes related to an existing client * Delete an existing client

This API provides the ability for approved/authorised Account Information Service Providers (AISPs) to access a customer's 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.

This API provides the ability for authorised payment initiation service providers (PISPs, TPPs - third party providers) to initiate and set up new domestic, international and file based payments. The TPPs will be able to initiate requests directly from the customer's (PSU - Payment Service User) current, personal or business - accounts, after being granted consent. Within Domestic Payments, Faster and CHAPS immediate payments can be initiated.

This API provides the ability for authorised payment initiation service providers (PISPs, TPPs - third party providers) to try out Open Banking Payment Initiation Service endpoints to sample responses for typical happy and unhappy path payment and consent scenarios. All OB PIS payment types and journeys are supported. Scenarios or predefined and responses are fixed based on set inputs. This API is developed according to the Open Banking Read/Write API Specifications and fulfils PSD2 regulation, see https://www.openbanking.org.uk

This API provides the ability for approved/authorised Account Information Service Providers (AISPs), Card Based Payment Instrument Issuers (CBPIIs) and Payment Initiation Service Providers (PISPs) to retrieve a list of all revoked or cancelled consents that have been made against the Account & Transactions APIs and/or the Confirmation of Funds APIs and/or the VariableRecurringPayment APIs. This API is developed according to the Open Banking Read/Write API Specifications and fulfils PSD2 regulation. See https://www.openbanking.org.uk