When the VoP scheme went live in October 2025, the first rulebook could not anticipate every real-world case. Six months of production traffic across thousands of PSPs revealed inconsistencies — ambiguous error responses, edge cases in message handling. The EPC's answer was rulebook version 1.1, published on 16 March 2026 and effective from 20 September 2026.
What v1.1 addresses
- Standardised error and response handling, so ambiguous outcomes behave consistently between PSPs.
- Clarified timing and timestamp attributes around the maximum execution time.
- Refinements to edge-case message handling identified during live operation.
And v2.0 is already coming
The scheme keeps evolving. A public consultation on change requests for rulebook v2.0 ran in 2026, with publication expected at the end of November 2026. In other words, VoP compliance is a moving target — what you build has to keep pace with rulebook versions.
- 1 Map your implementation against the v1.1 changes before the 20 September 2026 effective date.
- 2 Watch the v2.0 consultation and publication so you are not surprised later.
- 3 Decide whether to track rulebook versions yourself, or let a provider keep you current.
Compliance is continuous
A VoP integration that was correct in 2025 can drift out of step as the rulebook evolves. Staying current is part of the cost of running it yourself.
RoxPay tracks rulebook versions and rolls changes into its service, so your integration stays compliant through v1.1, v2.0 and beyond — without you re-reading every EPC update.