Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retirement date for Get Transaction Detail V1 #681

Open
nils-work opened this issue Jan 14, 2025 · 0 comments
Open

Retirement date for Get Transaction Detail V1 #681

nils-work opened this issue Jan 14, 2025 · 0 comments
Labels
Banking Banking domain APIs Non-breaking change A change that is not expected to result in a new endpoint version. Proposal made The DSB has proposed a specific change to the standards to address the change request

Comments

@nils-work
Copy link
Member

Description

As part of Maintenance Iteration 21, issue #664 delivered Get Transaction Detail V2 with the FDO Y25 #3 - 14th July 2025.
A retirement date for Get Transaction Detail V1 was not specified as part of the change.

Intention and Value of Change

To specify an appropriate retirement date for Get Transaction Detail V1.
The time between the Binding date of V2 and the Retirement date of V1 should allow Data Recipients to migrate to the new version, while minimising the time Data Holders must provide concurrent versions.

Area Affected

Banking APIs Endpoint version schedule.

Change Proposed

To specify the retirement date for Get Transaction Detail V1 as 10th November 2025 (Y25 #5).
Based on these dates, V1 and V2 should be available concurrently for at least four months.
The next option would be 16th March 2026 (Y26 #1) - eight months overlap.

@nils-work nils-work added the Banking Banking domain APIs label Jan 14, 2025
@nils-work nils-work added Proposal made The DSB has proposed a specific change to the standards to address the change request Non-breaking change A change that is not expected to result in a new endpoint version. labels Feb 10, 2025
@nils-work nils-work moved this from Full Backlog to Iteration Candidates in Data Standards Maintenance Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Banking Banking domain APIs Non-breaking change A change that is not expected to result in a new endpoint version. Proposal made The DSB has proposed a specific change to the standards to address the change request
Projects
Status: Iteration Candidates
Development

No branches or pull requests

1 participant