A 30-minute call with our team covers your current API setup, exactly what OBL 4.0 requires for your specific platform, and a realistic timeline to go live.
Commercial VRP is moving from pilot to live market in 2026. To participate, your open banking APIs need to be on a recent version of the UK Open Banking standard, such as version 4.0. Ozone API handles the full technical uplift in 8–10 weeks, built and maintained by the original architects of the UK Open Banking standard.
A real commercial opportunity, unlocked by one technical requirement.
What is the technical requirement for cVRP?
There is one technical requirement to get you there. Your open banking APIs need to be upgraded to support VRP, for example OBL 4.0.
Only the CMA9 are mandated to make this upgrade. Every other institution has a choice, and a window.
The UK Payments Initiative is operational. Visa A2A is onboarding its first wave of financial institution partners this year. Payment flows that have run through direct debit and card-on-file for decades are starting to shift and they will go to whichever institution is ready to receive them.
cVRP is what makes this possible. For your customers, it means real-time control over recurring payments: what they pay, when, and to whom. For your institution, it means capturing those payment flows before your peers do.
Why banks choose Ozone API for OBL 4.0 and VRP.
For an internal team building from scratch, this is a 6–12 month programme. It requires deep standards expertise, a significant engineering commitment, and an ongoing obligation to keep pace as OBL continues to evolve.
Ozone API is the complete OBL 4.0 implementation — already built, already compliant, and ready to deploy in 8–10 weeks.
What does the upgrade to OBL 4.0 actually involve?
OBL v4.0 is a major standards upgrade which enhances payload definitions across a range of Open Banking use cases, and formally introduces a commercial VRP (cVRP) specification.
In order to offer commercial VRP it is likely that you will need to support OBL v4.0 across your wider Open Banking API channel.
Commercial VRP follows the same underlying security principles, data standards and high-level consent model as compliance-driven Open Banking, with some additional data on the underlying use cases.
VRP does support a new consent structure giving customers granular control over payment parameters — including maximum payment amounts, frequency limits, and validity periods.
If you don’t currently support VRP in your Open Banking API, supporting it does not require a complete redesign of your Open Banking implementation, but it does make it important to upgrade to v4.0 so that the same technical standard is supported across all your APIs.
What your institution can offer once you're on OBL 4.0.
Commercial Variable Recurring Payments replaces direct debit and card-on-file with a bank-to-bank payment method that gives customers real-time visibility and control.
These are commercial use cases with payment volume attached. The institutions that offer them first build customer loyalty and payment flow capture that competitors will find very hard to replicate later.
The live use cases in 2026 and 2027:
Subscription management
Replace expiring card-on-file with a bank account-linked consent that never expires and can be paused or cancelled in-app at any point
Utility bill payments
Customers pay for actual usage rather than a fixed monthly estimate with a maximum payment limit they set, so unexpectedly high bills do not go through automatically.
Flexible loan repayments
Repay as salary arrives, within limits the customer defines; better outcomes for borrowers and better arrears performance for the institution
Tax and local authority payments
Flexible amounts paid to HMRC or councils, without the rigidity of a standing order
One-click checkout
Faster than cards, with consent set once and reused — rolling out to e-commerce from 2027 in line with the NPV roadmap
From your current APIs to OBL 4.0 in 8–10 weeks
Ozone API delivers a complete, OBL 4.0-compliant open banking platform. We do not consult on the build — we are the build. Deployed across 100+ financial institutions globally, across every major technology stack, including legacy core banking infrastructure.
What the uplift includes:
- All VRP API endpoints, built and maintained to OBL 4.0 specification
- FAPI 1.0 Advanced security profile with FAPI 1.0 backward compatibility
- OAuth 2.0 and OpenID Connect, fully configured
- Automated consent management with granular customer controls and full audit logging
- Ozone Connect: integration layer that adapts to your existing technology stack — no rip-and-replace required
- Multi-environment developer sandbox with synthetic data for TPP and fintech testing
- Cloud SaaS or on-premise deployment
- Certificate and credential management, handled for you
- Ongoing standards maintenance as the UK open banking standard evolves evolves — no internal standards
- ISO 27001:2022 and SOC 2 Type 2 certified
No internal build. No standards team to hire.
No gap between what you are running and what the standard requires.
Why Ozone API
Built by the people who wrote the standard.
Ozone API was founded by the original architects of the UK Open Banking standard. We did not learn open banking from the outside, we helped design it from within. That gives us a level of technical depth, regulatory credibility, and implementation speed that no other provider can offer.
100+ financial institutions live globally
Reference implementation for UK Open Banking standards
Trusted by banks, digital challengers, and global banking technology partners
Standards updated automatically as OBL evolves
100+ financial institutions live globally
Reference implementation for UK Open Banking standards
Trusted by banks, digital challengers, and global banking technology partners
Standards updated automatically as OBL evolves
Find out how quickly you can be cVRP-ready
No obligation. Just a clear picture of what cVRP readiness looks like for your institution.
How can we help you?
Complete the form and one of our open banking experts will get back to you soon.
Ozone API in partnership with Smart Data Foundry
