APIs

  • Account and Transaction Information API

    • Original

      The API endpoints described here allow an Account Information Service Provider ('AISP') to: Register an intent to retrieve account information by creating an "account access consent". This registers the data "permissions", expiration and historical period allowed for transactions / statements - that the customer (PSU) has consented to provide to the AISP; and Subsequently, retrieve account and transaction data.

  • Confirmation of Funds API

    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.

  • Open Data API

    The Open Data API allow API providers (e.g. banks, building societies and ATM providers) to develop API endpoints which can then be accessed by API users (e.g. third party developers) to build mobile and web applications for banking customers. The API allow providers to supply up to date, standardised, information about the latest available products and services.

  • Payment Services API

    The API endpoints described here allow a PISP to: Register an intent to stage a payment-order consent. Optionally confirm available funds for a payment-order (domestic and international immediate payments only). Subsequently submit the payment-order for processing. Optionally retrieve the status of a payment-order consent or payment-order resource.