Version control
# V4.0.1 - 2026-03-12
# Added
# Changed
- What error code should be used if a TPP repeats an Idempotency ID within 24 hours? - Updated answer with details of expected behaviour and new HTTP code introduced in v4.0.1
- Is the Data.DebtorAccount block to be provided by the ASPSP in the response block optional? - Amended response for additional clarity
- Can an ASPSP ask the PSU to re-authenticate if the trusted beneficiary was removed and need to be added back to the PSU’s trusted list? - Added sentence to clarify usage of Event Notifications.
# Fixed
- Fixed some minor formatting issues (marking must & should in bold, removing superfluous
**from some questions) to improve readability.
# v4.0.1 - 2025-11-20
# Added
- How should ASPSPs handle VRP payment consents created in v3 when ASPSP is now on v4?
- How do ASPSPs apply payment value limits to their online channels, and does this apply to open banking (including VRP) initiated payments?
- Which payment status codes can be considered as a final status?
- What error code should be used if a TPP repeats an Idempotency ID within 24 hours?
- Payload Validation
- Does the PointInTime field support negative values?
- Should TPPs include LEI when initiating FI-FI CHAPS payments?
# Changed
# v4.0.1 - 2025-02-11
# Fixed
- Fixed several broken links in R/W, CEG, OG, VRP FAQs, along with very minor typos