The API endpoints described here allow a Card Based Payment Instrument Issuer ('CBPII') to:
- Register an intent to confirm funds by creating an "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, see https://www.openbanking.org.uk
API Information
| Title | Confirmation of Funds V3 Sandbox |
|---|---|
| Protocol | TLS-MA |
| Open Banking Specification Version | 3.1 |
| Access | Free to use but subscription is required |
Key Features:
- Registration of consent to allow CBPII to make requests for funds confirmation
- Processing of requests to confirm funds are available
- Process requests for revocation of a previously registered consent
| Attachment | Size |
|---|---|
 testdatatrackersandbox_cof_v3.1.xlsx | 0 bytes |
Support Mailbox
https://www.openbanking.org.uk/terms
production
https://openbanking-ma-sandbox.santander.co.uk/sanuk/external-sandbox
Santander Internal Release Version: 3.1.6
Paths
/funds-confirmation-consents
/funds-confirmation-consents/{ConsentId}
/funds-confirmations
post /funds-confirmations
Funds Confirmations
Create Funds Confirmation
PSUOAuth2Security
PSUOAuth2Security
(oauth2 accessCode)
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
Authorization URL
https://openbanking-sandbox.santander.co.uk/sanuk/external-sandbox/open-banking/openid-connect-provider/v1/oauth2/authorize
Token URL
https://openbanking-ma-sandbox.santander.co.uk/sanuk/external-sandbox/open-banking/openid-connect-provider/v1/oauth2/token
Scopes
fundsconfirmations
Funds confirmation entitlement
OBFundsConfirmation1Param
Required in body
Default
{
"schema": {
"type": "object",
"properties": {
"Data": {
"$ref": "#\/definitions\/OBFundsConfirmationData1"
}
},
"required": [
"Data"
],
"additionalProperties": false
}
}x-fapi-financial-id
Required in header
string
The unique id of the ASPSP to which the request is issued. The unique id will be issued by OB.
x-fapi-customer-last-logged-time
Optional in header
string
The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is below: Sun, 10 Sep 2017 19:43:31 UTC
{
"pattern": "^(Mon|Tue|Wed|Thu|Fri|Sat|Sun), \\d{2} (Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec) \\d{4} \\d{2}:\\d{2}:\\d{2} (GMT|UTC)$"
}x-fapi-customer-ip-address
Optional in header
string
The PSU's IP address if the PSU is currently logged in with the TPP.
x-fapi-interaction-id
Optional in header
string
An RFC4122 UID used as a correlation id.
Authorization
Required in header
string
An Authorisation Token as per https://tools.ietf.org/html/rfc6750
x-customer-user-agent
Optional in header
string
Indicates the user-agent that the PSU is using.
Content-Type
Optional in header
string
application/json
application/json; charset=utf-8
application/json; charset=utf-8
Accept
Optional in header
string
application/json
application/json; charset=utf-8
application/json; charset=utf-8
201
Attribute description not found
400
Attribute description not found
401
Attribute description not found
403
Attribute description not found
404
Attribute description not found
405
Attribute description not found
406
Attribute description not found
415
Attribute description not found
429
Attribute description not found
500
Attribute description not found
Example Request
Example Response
POST https://openbanking-ma-sandbox.santander.co.uk/sanuk/external-sandbox/open-banking/v3.1/cbpii/funds-confirmations
Try this operation
Definitions
A number of monetary units specified in an active currency where the unit of currency is explicit and compliant with ISO 4217.
{
"type": "string",
"pattern": "^\\d{1,13}\\.\\d{1,5}$"
}
Amount of money to be confirmed as available funds in the debtor account. Contains an Amount and a Currency.
{
"type": "object",
"properties": {
"Amount": {
"$ref": "#\/definitions\/OBActiveCurrencyAndAmount_SimpleType"
},
"Currency": {
"description": "A code allocated to a currency by a Maintenance Agency under an international identification scheme, as described in the latest edition of the international standard ISO 4217 \"Codes for the representation of currencies and funds\".",
"type": "string",
"pattern": "^[A-Z]{3,3}$"
}
},
"required": [
"Amount",
"Currency"
],
"additionalProperties": false
}
Unambiguous identification of the account of the debtor to which a confirmation of funds consent will be applied.
{
"type": "object",
"properties": {
"SchemeName": {
"$ref": "#\/definitions\/OBExternalAccountIdentification4Code"
},
"Identification": {
"description": "Identification assigned by an institution to identify an account. This identification is known by the account owner.",
"type": "string",
"minLength": 1,
"maxLength": 256
},
"Name": {
"description": "Name of the account, as assigned by the account servicing institution.\nUsage: The account name is the name or names of the account owner(s) represented at an account level. The account name is not the product name or the nickname of the account.",
"type": "string",
"minLength": 1,
"maxLength": 70
},
"SecondaryIdentification": {
"description": "This is secondary identification of the account, as assigned by the account servicing institution. \nThis can be used by building societies to additionally identify accounts with a roll number (in addition to a sort code and account number combination).",
"type": "string",
"minLength": 1,
"maxLength": 34
}
},
"required": [
"SchemeName",
"Identification"
],
"additionalProperties": false
}
Name of the identification scheme, in a coded form as published in an external list.
{
"type": "string",
"example": [
"UK.OBIE.BBAN",
"UK.OBIE.IBAN",
"UK.OBIE.PAN",
"UK.OBIE.Paym",
"UK.OBIE.SortCodeAccountNumber"
],
"minLength": 1,
"maxLength": 40
}
Specifies the status of consent resource in code form.
{
"type": "string",
"enum": [
"Authorised",
"AwaitingAuthorisation",
"Rejected",
"Revoked"
]
}
{
"type": "object",
"properties": {
"Data": {
"$ref": "#\/definitions\/OBFundsConfirmationData1"
}
},
"required": [
"Data"
],
"additionalProperties": false
}
{
"type": "object",
"properties": {
"Data": {
"$ref": "#\/definitions\/OBFundsConfirmationConsentData1"
}
},
"required": [
"Data"
],
"additionalProperties": false
}
{
"type": "object",
"properties": {
"ExpirationDateTime": {
"description": "Specified date and time the funds confirmation authorisation will expire.\n If this is not populated, the authorisation will be open ended.\nAll dates in the JSON payloads are represented in ISO 8601 date-time format. \nAll date-time fields in responses must include the timezone. An example is below:\n2017-04-05T10:43:07+00:00",
"type": "string",
"format": "date-time"
},
"DebtorAccount": {
"$ref": "#\/definitions\/OBCashAccountDebtor4"
}
},
"required": [
"DebtorAccount"
],
"additionalProperties": false
}
{
"type": "object",
"properties": {
"ConsentId": {
"description": "Unique identification as assigned to identify the funds confirmation consent resource.",
"type": "string",
"minLength": 1,
"maxLength": 128
},
"CreationDateTime": {
"description": "Date and time at which the resource was created.\nAll dates in the JSON payloads are represented in ISO 8601 date-time format. \nAll date-time fields in responses must include the timezone. An example is below:\n2017-04-05T10:43:07+00:00",
"type": "string",
"format": "date-time"
},
"Status": {
"$ref": "#\/definitions\/OBExternalRequestStatus1Code"
},
"StatusUpdateDateTime": {
"description": "Date and time at which the resource status was updated.\nAll dates in the JSON payloads are represented in ISO 8601 date-time format. \nAll date-time fields in responses must include the timezone. An example is below:\n2017-04-05T10:43:07+00:00",
"type": "string",
"format": "date-time"
},
"ExpirationDateTime": {
"description": "Specified date and time the funds confirmation authorisation will expire.\nIf this is not populated, the authorisation will be open ended.\nAll dates in the JSON payloads are represented in ISO 8601 date-time format. \nAll date-time fields in responses must include the timezone. An example is below:\n2017-04-05T10:43:07+00:00",
"type": "string",
"format": "date-time"
},
"DebtorAccount": {
"$ref": "#\/definitions\/OBCashAccountDebtor4"
}
},
"required": [
"ConsentId",
"CreationDateTime",
"Status",
"StatusUpdateDateTime",
"DebtorAccount"
],
"additionalProperties": false
}
{
"type": "object",
"properties": {
"Data": {
"$ref": "#\/definitions\/OBFundsConfirmationConsentDataResponse1"
},
"Links": {
"$ref": "#\/definitions\/Links"
},
"Meta": {
"$ref": "#\/definitions\/Meta"
}
},
"required": [
"Data",
"Links",
"Meta"
],
"additionalProperties": false
}
{
"type": "object",
"properties": {
"ConsentId": {
"description": "Unique identification as assigned by the ASPSP to uniquely identify the funds confirmation consent resource.",
"type": "string",
"minLength": 1,
"maxLength": 128
},
"Reference": {
"description": "Unique reference, as assigned by the CBPII, to unambiguously refer to the request related to the payment transaction.",
"type": "string",
"minLength": 1,
"maxLength": 35
},
"InstructedAmount": {
"$ref": "#\/definitions\/OBActiveOrHistoricCurrencyAndAmount"
}
},
"required": [
"ConsentId",
"Reference",
"InstructedAmount"
],
"additionalProperties": false
}
{
"type": "object",
"properties": {
"FundsConfirmationId": {
"description": "Unique identification as assigned by the ASPSP to uniquely identify the funds confirmation resource.",
"type": "string",
"minLength": 1,
"maxLength": 40
},
"ConsentId": {
"description": "Unique identification as assigned by the ASPSP to uniquely identify the funds confirmation consent resource.",
"type": "string",
"minLength": 1,
"maxLength": 128
},
"CreationDateTime": {
"description": "Date and time at which the resource was created.\nAll dates in the JSON payloads are represented in ISO 8601 date-time format. \nAll date-time fields in responses must include the timezone. An example is below:\n2017-04-05T10:43:07+00:00",
"type": "string",
"format": "date-time"
},
"FundsAvailable": {
"description": "Flag to indicate the result of a confirmation of funds check.",
"type": "boolean"
},
"Reference": {
"description": "Unique reference, as assigned by the CBPII, to unambiguously refer to the request related to the payment transaction.",
"type": "string",
"minLength": 1,
"maxLength": 35
},
"InstructedAmount": {
"$ref": "#\/definitions\/OBActiveOrHistoricCurrencyAndAmount"
}
},
"required": [
"FundsConfirmationId",
"ConsentId",
"CreationDateTime",
"FundsAvailable",
"Reference",
"InstructedAmount"
],
"additionalProperties": false
}
{
"type": "object",
"properties": {
"Data": {
"$ref": "#\/definitions\/OBFundsConfirmationDataResponse1"
},
"Links": {
"$ref": "#\/definitions\/Links"
},
"Meta": {
"$ref": "#\/definitions\/Meta"
}
},
"required": [
"Data",
"Links",
"Meta"
],
"additionalProperties": false
}
Links relevant to the payload
{
"type": "object",
"properties": {
"Self": {
"type": "string",
"format": "uri"
},
"First": {
"type": "string",
"format": "uri"
},
"Prev": {
"type": "string",
"format": "uri"
},
"Next": {
"type": "string",
"format": "uri"
},
"Last": {
"type": "string",
"format": "uri"
}
},
"additionalProperties": false,
"required": [
"Self"
]
}
Meta Data relevant to the payload
{
"title": "MetaData",
"type": "object",
"properties": {
"TotalPages": {
"type": "integer",
"format": "int32"
},
"FirstAvailableDateTime": {
"$ref": "#\/definitions\/ISODateTime"
},
"LastAvailableDateTime": {
"$ref": "#\/definitions\/ISODateTime"
}
},
"additionalProperties": false
}
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: 2017-04-05T10:43:07+00:00
{
"type": "string",
"format": "date-time"
}
{
"type": "object",
"properties": {
"ErrorCode": {
"description": "Low level textual error code, e.g., UK.OBIE.Field.Missing",
"type": "string",
"minLength": 1,
"maxLength": 128
},
"Message": {
"description": "A description of the error that occurred. e.g., 'A mandatory field isn't supplied' or 'RequestedExecutionDateTime must be in future'\nOBIE doesn't standardise this field",
"type": "string",
"minLength": 1,
"maxLength": 500
},
"Path": {
"description": "Recommended but optional reference to the JSON Path of the field with error, e.g., Data.Initiation.InstructedAmount.Currency",
"type": "string",
"minLength": 1,
"maxLength": 500
},
"Url": {
"description": "URL to help remediate the problem, or provide more information, or to API Reference, or help etc",
"type": "string"
}
},
"required": [
"ErrorCode",
"Message"
],
"additionalProperties": false,
"minProperties": 1
}
An array of detail error codes, and messages, and URLs to documentation to help remediation.
{
"type": "object",
"properties": {
"Code": {
"description": "High level textual error code, to help categorize the errors.",
"type": "string",
"minLength": 1,
"maxLength": 40
},
"Id": {
"description": "A unique reference for the error instance, for audit purposes, in case of unknown\/unclassified errors.",
"type": "string",
"minLength": 1,
"maxLength": 40
},
"Message": {
"description": "Brief Error message, e.g., 'There is something wrong with the request parameters provided'",
"type": "string",
"minLength": 1,
"maxLength": 500
},
"Errors": {
"items": {
"$ref": "#\/definitions\/OBError1"
},
"type": "array",
"minItems": 1
}
},
"required": [
"Code",
"Message",
"Errors"
],
"additionalProperties": false
}