Upgrade Notes Week 37

Response code alignment for API authentication methods

Who is affected	All clients integrating with the Banking API using either Bearer token or API key authentication methods.
What is changing	We are aligning and standardizing response codes across both Bearer token and API key authorization methods. Previously, inconsistencies were observed - for example, valid Bearer tokens returned a `404` for a missing client, while API keys returned a `401` in the same case. This update ensures consistent and accurate HTTP status codes that reflect the actual issue (e.g., unauthorized access or missing resource), regardless of the authorization method used. No changes are made to the format of successful responses or to the response structure of valid requests. However, if your integration logic depends on specific response codes, you may need to revise it.
Expected release	September 2025
Instructions	Review your existing error-handling logic in any custom-built clients or middleware. Ensure that response code expectations are updated where needed, especially in cases involving invalid or mismatched client IDs. Pay special attention if you previously used workarounds for handling unexpected `401` or `403` responses from the API.
Consequences	Failure to update your integration may result in incorrect error handling, potentially leading to failed request retries, misinterpretation of errors, or other disruptions in client workflows. We strongly recommend testing authorization scenarios using both Bearer tokens and API keys before deploying to production.