Version control

V4.0.1 - 2026-06-22

Added

• New FAQs relating to revised Rate Limiting Guidance of June 2026.

Changed

• Corrected two instance of 'an' being used instead of 'a' ('an PISP' becoming 'a PISP' and 'an CBPII' becoming 'a CBPII')

Deleted

• Previous FAQ relating to Rate Limiting Guidance, as superceded by new guidance

V4.0.1 - 2026-04-21

Added

• New FAQ relating to the usage of free format AddressLines in PostalAddress object, giving usage guidance ahead of an ISO change in Nov 2026.

Changed

• Amended Message Signing FAQs, fixing a typo re how iss is formed, applying bold font to must/should etc., and fixing some grammatical errors to improve readability.

V4.0.1 - 2026-04-08

Changed

• Updated a number of FAQs related to VRP; fixing typos and poor language, making words like 'must' bold.
• Updated FAQ re Standing Order Frequencies (per CDRW-5042) to correct examples that previous answer gave incorrect information for.

Deleted

• A number of duplicated FAQs related to VRP.
• A number of FAQs that are better answered by the publication of new Sweeping guidance (opens new window).

V4.0.1 - 2026-03-12

Added

• Why do PCC enums BillPayment, EcommerceGoods, EcommerceServices, PartyToParty, PispPayee and Other appear in the OpenAPI files as part of OBInternalPaymentContext1Code but not the codeset repo?

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

• Is the Data.DebtorAccount block to be provided by the ASPSP in the response block optional?

v4.0.1 - 2025-02-11

Fixed

• Fixed several broken links in R/W, CEG, OG, VRP FAQs, along with very minor typos