From 34c48589e4704647cfc3e7648c820085e2c07197 Mon Sep 17 00:00:00 2001 From: Ryan-Ozone Date: Mon, 8 Jun 2026 13:48:45 +0100 Subject: [PATCH 1/2] Document known issues for Model Bank Added a known issues list for Model Bank v3.1.11 / v4.0 --- README.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/README.md b/README.md index 32dacc8..78fdbb8 100644 --- a/README.md +++ b/README.md @@ -325,7 +325,22 @@ Once the PSU consent is successful, Ozone Bank will redirect back to the redirec ![Image 11.png](./attachments/4-11-Accounts.png) + + ### 7.2 Retrieve Transaction Data ![Image 12.png](./attachments/4-12-Balances.png) +# 8. Model Bank - Known Issues List + +- list of known reported issues with the Model Bank +- these issues are targeted to be addressed in the upcoming release of the v4.0.1 standards-conformant model bank + +| Issue number | Description | +|------------- | ----------- | +| 8.1 | Some issues with handling of detailed vs basic permissions for statements and transactions.
Some fields that should only be available with detailed permission can be accessed using a basic permission
e.g. Data.Statement.StatementAmount for statements APIs| +| 8.2 | On Model Bank v4.0, certain negative scenarios for /domestic-vrp-consents can generate non-conformant
error response payloads i.e. not 4-character enumerated error codes in the 3.1.x version-style | +| 8.3 | Mutually exclusive fields in standing order consents can be provided together and the request will succeed.
In version 4.0 you can provide FinalPaymentDateTime and CountPerPeriod and the
payload will succeed.| +| 8.4 | Sending a POST request with an incorrect Content-Type header will currently return a 500 error
whereas a 415 Unsupported Media Type error should be returned.| +| 8.5 | In VRP consents, the Data.Refund object is not provided in the consent response even when ReadRefundAccount is set to 'Yes' in the consent request | +| 8.6 | In VRP consents, the Data.DebtorAccount object is not provided in the consent response even when this information is known within the platform | From 6eec526757bf1c8c0a54392856573385168d2cf9 Mon Sep 17 00:00:00 2001 From: Peter Stanley <129527932+OBPeteS@users.noreply.github.com> Date: Thu, 11 Jun 2026 10:51:34 +0100 Subject: [PATCH 2/2] Update README.md Quick tweak to one issue to improve clarity --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 78fdbb8..8156973 100644 --- a/README.md +++ b/README.md @@ -339,7 +339,7 @@ Once the PSU consent is successful, Ozone Bank will redirect back to the redirec | Issue number | Description | |------------- | ----------- | | 8.1 | Some issues with handling of detailed vs basic permissions for statements and transactions.
Some fields that should only be available with detailed permission can be accessed using a basic permission
e.g. Data.Statement.StatementAmount for statements APIs| -| 8.2 | On Model Bank v4.0, certain negative scenarios for /domestic-vrp-consents can generate non-conformant
error response payloads i.e. not 4-character enumerated error codes in the 3.1.x version-style | +| 8.2 | On Model Bank v4.0, certain negative scenarios for /domestic-vrp-consents can generate non-conformant
error response payloads i.e. 3.1.x version-style code is returned instead of the 4 digit v4 value.| | 8.3 | Mutually exclusive fields in standing order consents can be provided together and the request will succeed.
In version 4.0 you can provide FinalPaymentDateTime and CountPerPeriod and the
payload will succeed.| | 8.4 | Sending a POST request with an incorrect Content-Type header will currently return a 500 error
whereas a 415 Unsupported Media Type error should be returned.| | 8.5 | In VRP consents, the Data.Refund object is not provided in the consent response even when ReadRefundAccount is set to 'Yes' in the consent request |