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

Cashplus Bank Standing Orders API

The Standing Orders API from Cashplus Bank — 2 operation(s) for standing orders.

Cashplus Bank Standing Orders API is one of 28 APIs that Cashplus Bank publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Standing Orders. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 31 schemas. It is described by OpenAPI 3.2.0, at version 3.1.11.

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

2 operations 2 paths 31 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.1.11
Server
/open-banking/v3.1/aisp
Authentication
OAuth 2.0, OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 2

Cashplus Bank Standing Orders API 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 2

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

Standing Orders 2
GET
/accounts/{AccountId}/standing-orders
Get Standing Orders
GetAccountsAccountIdStandingOrders 6 params → 200400401403404405406429
GET
/standing-orders
Get Standing Orders
GetStandingOrders 5 params → 200400401403404405406429

Schemas 31

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

NextPaymentDateTime
string
The date on which the next payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. All…
LastPaymentDateTime
string
The date on which the last (most recent) payment for a Standing Order schedule was made.All dates in the JSON payloads are represented in ISO 8601 date-time fo…
AccountId
string
A unique and immutable identifier used to identify the account resource. This identifier has no meaning to the account owner.
OBActiveCurrencyAndAmount_SimpleType
string
A number of monetary units specified in an active currency where the unit of currency is explicit and compliant with ISO 4217.
OBSupplementaryData1
object
Additional information that can not be captured in the structured fields and/or any other specific block.
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:…
OBReadStandingOrder6
object
3 properties 1 required
Reference
string
Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. Usage: If available, the initiating party should provide this…
Name_0
string
The account name is the name or names of the account owner(s) represented at an account level, as displayed by the ASPSP's online channels. Note, the account n…
OBBranchAndFinancialInstitutionIdentification5_1
object
Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on t…
2 properties 2 required
OBError1
object
4 properties 2 required
Meta
object
Meta Data relevant to the payload
3 properties
FirstPaymentDateTime
string
The date on which the first payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. All…
SecondaryIdentification
string
This is secondary identification of the account, as assigned by the account servicing institution. This can be used by building societies to additionally ident…
OBActiveOrHistoricCurrencyAndAmount_2
object
The amount of the first Standing Order
2 properties 2 required
Links
object
Links relevant to the payload
5 properties 1 required
Identification_1
string
Unique and unambiguous identification of the servicing institution.
StandingOrderId
string
A unique and immutable identifier used to identify the standing order resource. This identifier has no meaning to the account owner.
OBActiveOrHistoricCurrencyAndAmount_11
object
The amount of the last (most recent) Standing Order instruction.
2 properties 2 required
OBActiveOrHistoricCurrencyAndAmount_4
object
The amount of the final Standing Order
2 properties 2 required
OBStandingOrder6
object
17 properties 2 required
ActiveOrHistoricCurrencyCode_1
string
A code allocated to a currency by a Maintenance Agency under an international identification scheme, as described in the latest edition of the international st…
OBErrorResponse1
object
An array of detail error codes, and messages, and URLs to documentation to help remediation.
4 properties 3 required
FinalPaymentDateTime
string
The date on which the final payment for a Standing Order schedule will be made.All dates in the JSON payloads are represented in ISO 8601 date-time format. All…
OBExternalStandingOrderStatus1Code
string
Specifies the status of the standing order in code form.
OBActiveOrHistoricCurrencyAndAmount_3
object
The amount of the next Standing Order.
2 properties 2 required
NumberOfPayments
string
Number of the payments that will be made in completing this frequency sequence including any executed since the sequence start date.
OBExternalFinancialInstitutionIdentification4Code
string
Name of the identification scheme, in a coded form as published in an external list.
Frequency_1
string
Individual Definitions: NotKnown - Not Known EvryDay - Every day EvryWorkgDay - Every working day IntrvlDay - An interval specified in number of calendar days…
OBExternalAccountIdentification4Code
string
Name of the identification scheme, in a coded form as published in an external list.
OBCashAccount5_1
object
Provides the details to identify the beneficiary account.
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cashplus-standing-orders-api-openapi.yml Raw ↑

Other APIs Cashplus Bank publishes across the network.

Cashplus Identity API
Cashplus Accounts API
Cashplus Applications API
Cashplus Eligibility API
Cashplus Payments API
Cashplus Products API
Cashplus Transactions API
Cashplus Bank Account Access API
Cashplus Bank Accounts API
Cashplus Bank Balances API
Cashplus Bank Beneficiaries API
Cashplus Bank Direct Debits API
Where this information came from

This is an independent, third-party profile of Cashplus Bank Standing Orders API, 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.