--- title: "Create a Funds Confirmation Request" method: POST path: "/funds-confirmations" tags: ["Funds Confirmations"] --- # Create a Funds Confirmation Request `POST /funds-confirmations` ## Request - Base URL: `/open-banking/v4.0/cbpii` (relative, and the document was published on a file host, not at the API’s origin) - URL: `/open-banking/v4.0/cbpii/funds-confirmations` - Auth: OAuth 2 - Authorization code: `https://authserver.example/authorization` - Token URL: `https://authserver.example/token` scopes: `fundsconfirmations` Enables a CBPII to check whether a PSU has sufficient available funds for a CBPII transaction. The request identifies the authorised funds-confirmation consent using `ConsentId`, provides a CBPII-assigned `Reference`, and specifies the `InstructedAmount` to check. On success (HTTP 201), the response contains a `FundsConfirmationId`, the related `ConsentId`, `CreationDateTime`, the boolean `FundsAvailable` result, the `Reference`, and the `InstructedAmount` checked. **Note:** This operation checks availability only; it does not reserve funds, move funds, or initiate a payment. ## Headers - `x-fapi-auth-date` string - `x-fapi-customer-ip-address` string - `x-fapi-interaction-id` string - `Authorization` string, required - `x-customer-user-agent` string - `x-jws-signature` string - `x-client-id` string ## Request body - OBFundsConfirmation1 - `Data` OBFundsConfirmationData1, required - `ConsentId` string, required: Unique identification as assigned by the ASPSP to uniquely identify the funds confirmation consent resource. - `Reference` string, required: Unique reference, as assigned by the CBPII, to unambiguously refer to the request related to the payment transaction. - `InstructedAmount` OBActiveOrHistoricCurrencyAndAmount, required: Amount of money to be confirmed as available funds in the debtor account. Contains an `Amount` and a `Currency`. - `Amount` string, required: A number of monetary units specified in an active currency where the unit of currency is explicit and compliant with ISO 4217. - `Currency` string, required: 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". ## Response `201` Funds Confirmation Created - OBFundsConfirmationResponse1 - `Data` OBFundsConfirmationDataResponse1, required - `FundsConfirmationId` string, required: Unique identification as assigned by the ASPSP to uniquely identify the funds confirmation resource. - `ConsentId` string, required: Unique identification as assigned by the ASPSP to uniquely identify the funds confirmation consent resource. - `CreationDateTime` string, date-time, required: Date and time at which the resource was created. 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` - `FundsAvailable` boolean, required: Flag to indicate the result of a confirmation of funds check. - `Reference` string, required: Unique reference, as assigned by the CBPII, to unambiguously refer to the request related to the payment transaction. - `InstructedAmount` OBActiveOrHistoricCurrencyAndAmount, required: Amount of money to be confirmed as available funds in the debtor account. Contains an `Amount` and a `Currency`. - `Amount` string, required: A number of monetary units specified in an active currency where the unit of currency is explicit and compliant with ISO 4217. - `Currency` string, required: 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". - `Links` Links: Links relevant to the payload - `Self` string, uri, required - `First` string, uri - `Prev` string, uri - `Next` string, uri - `Last` string, uri - `Meta` Meta: Meta Data relevant to the payload - `TotalPages` integer - `FirstAvailableDateTime` string, date-time: 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` - `LastAvailableDateTime` string, date-time: 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` ## Other responses - `400`: Bad request - `401`: Unauthorized - `403`: Forbidden - `405`: Method Not Allowed - `406`: Not Acceptable - `415`: Unsupported Media Type - `429`: Too Many Requests - `500`: Internal Server Error ## Changes - **2026-07-17** `2acd18792686`: 1 info - added the new optional `header` request parameter `x-jws-signature` - **2026-07-17** `ee60c3b2d7f5`: 10 warning - the optional response header `x-jws-signature` removed for the status `201` - the optional response header `x-jws-signature` removed for the status `400` - the optional response header `x-jws-signature` removed for the status `401` - the optional response header `x-jws-signature` removed for the status `403` - …6 more - **2026-07-15** `d219e803034a`: 1 info - added the new optional `header` request parameter `x-jws-signature` - **2026-07-15** `5ffc96fe3171`: 1 breaking - added the new required `header` request parameter `Authorization` - **2026-06-26** `cfe0fed461d0`: 1 warning - deleted the `header` request parameter `Authorization` [Operation history](https://skmtc.dev/openbankinguk/apis/confirmation-of-funds-api-specification/changes/funds-confirmations/post.md) --- [API](https://skmtc.dev/openbankinguk/apis/confirmation-of-funds-api-specification.md) - [All operations](https://skmtc.dev/openbankinguk/apis/confirmation-of-funds-api-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/openbankinguk/apis/confirmation-of-funds-api-specification/revisions/b3f67068dbfc?raw)