Open banking took the best part of a decade to build. The Data (Use and Access) Act now lets the government mandate the same pattern in energy, finance and half a dozen other sectors — and the firms that treat each scheme as a separate build will pay for the same plumbing several times over.
Most coverage of Smart Data reads like a policy briefing: the sectors, the timelines, the promise of innovation. That is not the useful frame for a technology function. The useful frame is that Part 1 of the Data (Use and Access) Act 2025 gives ministers a reusable legal instrument, and the schemes it produces will demand a reusable technical one. If your organisation is a likely data holder — an energy supplier, a lender, a telecoms operator — the question is not whether a scheme will land, but whether you build the consent and API layer once or rebuild it under deadline pressure each time a new sector goes live.
What the Act actually grants
The Data (Use and Access) Act received Royal Assent on 19 June 2025. Part 1, titled “Access to customer data and business data”, is the Smart Data engine. It does not itself create any scheme. It hands the Secretary of State and the Treasury a power to make regulations that compel data holders to share two categories of data: customer data — information about the goods, services and digital content supplied to a specific customer — and business data, which covers pricing, performance and usage information about what a trader offers more generally.
Free · 4 minutes
Do you know where AI is already being used in your business — and what it can see?
Fourteen questions on shadow AI, data exposure, oversight, and governance debt — the gap between how fast AI is arriving and how much control you have over it. Banded finding on screen, full sheet by email.
The distinction matters for how you build. Customer data moves on the customer’s authority, through an accredited third party the Act frames as an authorised person. Business data can be required to be published or shared without an individual customer’s consent at all. A single scheme will typically touch both. That means your architecture needs a consent-and-authorisation path and a bulk-disclosure path, and it needs to keep them cleanly separated so that the lawful basis for each flow is never in doubt.
This is the same shape as open banking, which is exactly the point. Open banking is the working proof: on the Open Banking Implementation Entity’s own figures it passed 17 million active users in early 2026 and processes more than two billion API calls a month. The government’s stated ambition, set out in its 2026 Smart Data Strategy, is 20 or more interoperable schemes by 2035. What was a one-off regulatory project for payments is becoming a repeatable pattern.
What is actually coming, and when
The sequencing is public and worth reading against your own sector. Banking and finance move first: open banking is transitioning to Financial Conduct Authority oversight, with an Open Finance roadmap expected in 2026. Energy is the next serious candidate, with a consultation signalled for 2026 and scheme regulations anticipated around 2027 to 2028. Road fuels, transport, retail, telecoms, property and agrifood sit further back, some at the call-for-evidence stage. A cross-sector Smart Data guidebook is expected in early 2027.
Treat those dates as directional, not fixed — they are policy intentions, and enabling powers have a way of slipping. The strategic read does not depend on the exact month. It depends on this: the first scheme to reach you sets your baseline cost, and every scheme after that is either cheap or expensive depending on how much of the first build you can reuse. The progression from open banking into open finance and embedded services shows the direction of travel; Smart Data simply widens it beyond financial services.
The reusable core: three components
Strip away the sector specifics and every Smart Data scheme needs the same three things from a data holder.
- Permission and consent management. A record of who authorised what, for which data, to which accredited third party, for how long, and whether it has been revoked. Consent under these schemes is time-bound and revocable by design, which means it is a stateful system, not a checkbox. Build it as a first-class service with its own audit trail, not as a column on an account record.
- Standardised data-access APIs. A contract that exposes customer and business data on request, authenticated against the scheme’s accreditation model. The schema differs by sector; the mechanics — resource endpoints, scoped tokens, pagination, error semantics — do not. Design the contract so the sector-specific payload is a swappable schema behind a stable envelope.
- Data-quality and lineage controls. Once data leaves your estate under a legal mandate, its accuracy is a regulatory exposure, not an internal nuisance. Schemes will expect you to produce, correct and retain data to a defined standard. The controls that satisfy that are the same across sectors: validation at the boundary, provenance you can evidence, and a correction path that propagates.
None of this is novel engineering. It is the same portability-and-access plumbing that other regimes are converging on from different directions — the same discipline that makes a standing data-export API worth building ahead of a portability mandate rather than in a scramble afterwards. Build it as scheme-agnostic infrastructure and each new sector scheme becomes a configuration exercise.
A consent-grant contract you can reuse
Here is the shape of a sector-agnostic consent grant and the access call it authorises, as an OpenAPI fragment. The sector lives in a field, not in the structure — the same contract serves energy, finance or telecoms by changing the scheme and the payload schema behind resource.
# Sector-agnostic Smart Data consent grant + access contract
openapi: 3.1.0
info:
title: Smart Data Access API
version: "1.0"
paths:
/consents:
post:
summary: Record a customer authorisation for an accredited third party
requestBody:
required: true
content:
application/json:
schema: { $ref: "#/components/schemas/ConsentGrant" }
responses:
"201": { description: Consent recorded; returns a scoped grant id }
/consents/{grantId}:
delete:
summary: Revoke a live consent (customer or authorised person)
responses:
"204": { description: Revoked; downstream access must stop }
/data/{resource}:
get:
summary: Return customer or business data under a live grant
security: [ { bearerAuth: [] } ] # token scoped to grantId
parameters:
- name: resource
in: path
required: true
schema: { type: string } # e.g. accounts, tariffs, usage
responses:
"200": { description: Data payload (schema varies by scheme) }
"403": { description: No live grant, or scope not authorised }
components:
securitySchemes:
bearerAuth: { type: http, scheme: bearer }
schemas:
ConsentGrant:
type: object
required: [scheme, customerId, thirdPartyId, scopes, expiresAt]
properties:
scheme: { type: string } # energy | banking | telecoms
customerId: { type: string }
thirdPartyId: { type: string } # accredited recipient
scopes: { type: array, items: { type: string } }
expiresAt: { type: string, format: date-time } # time-bound
The detail that separates a real implementation from a demo is that revocation has to be enforced, not merely recorded. A deleted grant must stop live access immediately — which means access tokens are short-lived and checked against grant state on every call, not issued once and trusted. That is the single design decision most retrofits get wrong.
Consent is where the lawful basis lives
One caution before anyone treats this as a pure integration problem. Smart Data consent is not the same construct as a data-protection lawful basis, and the two have to be reconciled deliberately. The scheme authorisation says a customer permitted this third party to receive this data; your obligations under the reformed data-protection regime still govern how you process it. Getting the interaction right is its own piece of engineering — the kind of question the recognised legitimate interests provisions under the same Act force you to answer explicitly rather than assume.
Firms that have already stood up open banking, or an equivalent framework, have most of this. The technology-readiness discipline behind those frameworks transfers almost wholesale. The gap is usually organisational: the open banking stack sits inside the payments team and was scoped to payments, so the energy or telecoms scheme gets built again from scratch by a different team who never saw the first one.
The government has handed itself a reusable power. The sensible response is to hand yourself a reusable platform — before the first scheme regulation names your sector and turns a design choice into a delivery deadline.
Free interactive tool
Website compliance checklist
What your site has to do, based on what it actually does
Answer as much or as little as you like — the list builds as you go. Nothing is stored against your name and no email is required.
Everything that applies
Ordered by what to do first: legal requirements you can close quickly, then larger pieces of work, then what is expected rather than required. Not exhaustive, and not a legal audit.
Dated PDF, yours to keep or circulate.
Can you trust the architecture you have?
Architecture diagrams rarely show the reality of how systems actually operate. An independent review establishes what is really there.