Open Banking in Australia: CDR Obligations, Platform Costs and Timelines for Banks
What Australian ADIs must build to meet Consumer Data Right obligations, what hosted versus in-house platforms typically cost, and which rules have moved since your last compliance review.
What a CDR data holder must run, endpoint by endpoint
If you run an authorised deposit-taking institution (ADI) in Australia, the Consumer Data Right isn't optional and it isn't a one-off project. It's a standing set of production systems that must answer accredited third parties around the clock, meet published performance thresholds, and report to regulators. For most smaller banks, mutuals and credit unions the question isn't whether to comply. It's whether to keep a self-built stack, move to a hosted data holder service, or take the module your core banking provider offers. Choosing an open banking platform Australia's regulators will accept starts with knowing what the platform actually has to do.
The legal framework sits in Part IVD of the Competition and Consumer Act 2010, the CDR Rules, and the Consumer Data Standards set by the Data Standards Body within Treasury. The ACCC runs the CDR Register and accreditation and enforces the Rules. The OAIC enforces the privacy safeguards. Treasury owns policy. That split matters in practice, because a single incident can draw interest from more than one regulator.
A banking data holder's obligations fall into five build areas:
- Product reference data (PRD). Public, unauthenticated APIs (Get Products and Get Product Detail) publishing rates, fees, features, eligibility and constraints for publicly offered products. They must stay in sync with your website and product disclosure documents, which makes PRD as much a product-governance problem as a technical one.
- Consumer data APIs. Authenticated endpoints covering accounts, balances, transactions, direct debits, scheduled payments, payees and customer details, for the product categories the Rules have phased in.
- Authorisation and identity. An authorisation server that implements the CDR security profile, which is based on the OpenID Foundation's Financial-grade API (FAPI) specifications. It must also support one-time-password authentication and handle authorisations for joint accounts, secondary users and business-customer nominated representatives.
- Consumer dashboard. Inside online or mobile banking, customers must be able to see each active authorisation, what data it covers and for how long, and withdraw it. A withdrawal has to reach the recipient through the CDR revocation mechanism.
- Operations and reporting. Registration on the CDR Register, conformance testing during onboarding, a Get Metrics endpoint that reports availability and performance, record keeping, internal dispute handling, and periodic reports to the ACCC and OAIC.
The non-functional requirements in the Standards include a monthly availability target (99.5% at the time of writing, with planned outages excluded), response-time thresholds that vary by endpoint tier, and traffic levels below which you can't throttle legitimate requests. Your metrics endpoint publishes how you perform against them. Regulators and recipients both read those figures, so confirm the current thresholds in the Standards before you write them into a contract.
Accredited data recipient duties and the consent layer
The other side of the market is the accredited data recipient: the fintech, lender, accounting platform or bank that receives CDR data with the consumer's consent. Many ADIs end up on both sides, holding data as a data holder and receiving it to speed up lending decisions or account switching. The recipient obligations are different, and in some ways heavier.
Unrestricted accreditation requires an information security program that meets Schedule 2 of the Rules, an independent assurance report at accreditation and on a recurring cycle after that, fit-and-proper checks, adequate insurance, internal dispute resolution, and membership of a recognised external dispute resolution scheme (AFCA for banking). Lighter routes exist. Sponsored accreditation, and operating as a CDR representative of an accredited principal, reduce the assurance burden. The trade-off is reliance on a sponsor or principal whose controls and commercial terms you then depend on.
Consent management is where recipients spend the most product effort. The Rules require consents to be specific, time-limited (currently up to 12 months), and limited to the data actually needed, with plain-language flows and a recipient-side dashboard that mirrors the data holder's. Recipients also need workflows for:
- Deleting or de-identifying data when consent expires or is withdrawn, under the recipient's stated policy.
- Ongoing notifications to consumers about active consents.
- Disclosures to trusted advisers, CDR insights, and outsourced service providers, each with its own conditions.
- Record keeping detailed enough to answer a regulator's question about any single consent, months later.
Rule amendments in recent years simplified parts of the consent model, including how some consents can be bundled and how certain choices are presented. Many recipients designed their flows under the older, stricter rules and haven't revisited them. A review is worth the effort because simpler flows tend to lift completion rates. Check the current compiled Rules and the Standards' consumer experience guidelines first, not a vendor's summary.
For most mid-sized lenders, using an accredited intermediary (Basiq, Frollo, Adatree and Fiskil are among the names in this space, as are the CDR services of larger aggregators) makes more sense than seeking unrestricted accreditation directly. You get to market faster, you avoid building connectivity to every data holder yourself, and the assurance burden falls on a specialist. Verify each provider's current accreditation status and model before shortlisting. Go direct only if CDR data is central to your product and your volumes justify a dedicated security and compliance team.
Build versus buy for a smaller ADI: where the money goes
Major banks built in-house because they had the engineering depth and were first in line. Smaller ADIs, whose entire technology teams can be smaller than a major bank's CDR squad, face a different calculation. Ongoing cost is driven less by the initial build than by keeping pace with Standards changes. The Data Standards Body publishes regular version updates with mandatory obsolescence dates, and every one needs analysis, development, testing and a release.
The ranges below are typical 2026 market ranges for an ADI serving roughly 20,000 to 300,000 customers. They're shown in USD for comparison, vary widely by contract, scope and core banking platform, and should be confirmed with vendors. Australian contracts are usually priced in AUD.
| Approach | Typical upfront cost | Typical annual run cost | Best fit | Main risk |
|---|---|---|---|---|
| In-house build on own cloud | $1.5M–$5M | $500k–$1.5M (team, hosting, security testing, Standards upgrades) | ADIs with strong API engineering and plans to reuse the stack for a broader API strategy | Key-person dependency; falling behind on Standards versions |
| Hosted data holder service (specialists such as Biza.io and similar) | $100k–$400k integration | $150k–$500k subscription, often tiered by customer count or API volume | Most small and mid-sized ADIs | Integration to core and online banking still sits with you; check who carries an outage |
| Core or processing provider module (offerings from payments, processing and core vendors; check with your own provider) | $50k–$250k configuration | $80k–$350k, sometimes bundled into core fees | Mutuals and credit unions already on that provider | Roadmap tied to the provider's priorities; less control over consent dashboard UX |
| Recipient access via accredited intermediary | $10k–$75k integration | $20k–$250k: platform minimums plus per-connection or per-call fees | Lenders and ADIs using CDR data for origination and onboarding | Unit costs at scale; dependence on the intermediary's accreditation |
Hypothetical worked example: say a mutual bank with 80,000 customers runs a self-built data holder stack maintained by three engineers and a part-time compliance analyst. Fully loaded, that's plausibly $600k to $900k a year before hosting, penetration testing and Standards upgrades. A hosted service at $250k a year plus $200k of one-off integration would cost around $450k in year one and about $250k a year after. The saving shows up quickly, and the team is freed for other work. The calculation reverses if the same APIs also power the bank's broker channel or partner integrations, because then the in-house stack is doing more than compliance work.
Price these hidden drivers explicitly: PRD maintenance; joint-account and secondary-user logic, which depends heavily on how clean your core customer data is; 24/7 incident response against the availability target; and the security profile upgrade path as the ecosystem moves toward FAPI 2.0.
Timelines, and the obligations that have shifted
Banking was the first CDR sector. The four major banks went live first, with non-major ADIs following in phases over the next couple of years and product categories added along the way. Newly authorised ADIs get deferred commencement dates under the Rules, and each obligation has its own clock. If you're applying for an ADI licence, or acquired one recently, map those dates on day one rather than assuming a single deadline.
Several parts of the regime have moved since many ADIs last reviewed their compliance position, and some are still moving. Verify each of these against the current Rules, Standards and regulator guidance:
- Joint accounts. Sharing on joint accounts moved to a pre-approval default, so data holders need to support it without requiring every holder to opt in first.
- Consent and operational amendments. Recent rule changes simplified consent, adjusted some business-consumer arrangements and altered certain data holder obligations. Check which ones reduce your scope as well as which add to it.
- Non-bank lenders. The non-bank lending sector has been designated, but what it must actually do depends on rules being made and on their commencement dates. For recipients, it widens the pool of data holders you can reach. For non-ADI lenders, it creates new obligations.
- Expansion pause and review. The Government has slowed expansion to further sectors and reviewed the regime's costs and benefits. Don't fund work for open finance or other sector extensions until rules are actually made.
- Action initiation. Payment and action initiation through the CDR has been the subject of legislation and consultation. Don't assume a delivery date, and watch for final rules and standards before committing budget.
- Security profile. Migration toward FAPI 2.0 will bring transition windows during which both versions may need support.
A realistic implementation timeline for a smaller ADI moving to a hosted platform looks like this:
| Phase | Typical duration | Key outputs |
|---|---|---|
| Gap assessment and vendor selection | 6–10 weeks | Obligation map against current Rules and Standards version; shortlist; reference calls |
| Contracting and security due diligence | 4–8 weeks | SLA, data residency and outsourcing terms; APRA CPS 230 and CPS 234 alignment |
| Integration to core and digital banking | 12–24 weeks | Data mapping, authentication flows, consent dashboard in app and web |
| Conformance testing and register onboarding | 4–8 weeks | Conformance Test Suite passed; Register details updated |
| Parallel run and cutover | 4–6 weeks | Metrics verified against thresholds; incident runbooks live |
Allow roughly seven to thirteen months end to end. Migrations from an existing in-house stack can move faster on integration, but live authorisations must survive the switch, and that needs careful handling.
Red flags when shortlisting a CDR platform, and a decision rule
Most vendor demos look alike. The differences show up in operations, contracts and how fast the vendor ships Standards upgrades. When evaluating an open banking platform Australia-regulated ADIs will depend on, press on these points:
- Standards currency. Ask which Consumer Data Standards version the platform runs in production today, and how long after each obsolescence date its customers have historically been compliant. Vague answers are a red flag.
- Availability accountability. The availability target applies to you, not the vendor. Make sure the SLA matches or beats it, excludes nothing you can't exclude yourself, and carries meaningful service credits.
- Metrics transparency. You should see the same Get Metrics data regulators see, in near real time, without raising a ticket.
- Joint and business account handling. Ask for a live walkthrough of joint-account pre-approval, secondary users and nominated representatives against your own data model.
- APRA outsourcing fit. The arrangement has to sit inside your CPS 230 operational risk and CPS 234 information security frameworks, with audit rights, data location clarity and exit provisions.
- Exit and portability. Confirm that active authorisations, consent records and audit logs can be migrated if you leave.
Overseas platforms built for the UK, EU or Brazilian open banking regimes often pitch into Australia. The underlying patterns are similar, but the CDR's consent rules, security profile and data clusters are distinct. Ask for named Australian production deployments and speak to those customers, rather than assuming international experience will carry over.
Because CDR obligations combine competition law, privacy law and prudential requirements, have your legal and compliance advisers confirm your obligation map before signing.
The decision rule: if your ADI has fewer than about 300,000 customers and doesn't plan to reuse its CDR APIs for wider partner integrations, buy a hosted data holder service or your core provider's module, and put the savings into consent UX and PRD governance. Build or keep an in-house stack only if your API platform serves several channels and you can staff at least two engineers dedicated to Standards changes year-round.
Questions buyers ask
Do smaller ADIs have the same CDR data holder obligations as the major banks?
Broadly yes. Non-major ADIs share the same core data sets, consumer dashboard, security profile and performance standards. They got later commencement dates, and newly authorised ADIs get deferred timelines under the Rules. Check the current compiled Rules for your exact dates and any exemptions that apply to you.
Can a lender use CDR data without becoming an accredited data recipient?
Yes, through the lighter pathways. It can act as a CDR representative of an accredited principal, take sponsored accreditation, or receive certain outputs as a trusted adviser or through CDR insights where the Rules allow. Each route has its own conditions and leaves you reliant on another party's accreditation. Have your compliance advisers confirm which route fits your use case.
How much does a hosted CDR data holder platform typically cost?
For a small to mid-sized ADI, typical 2026 market ranges run from about $100k to $400k in USD for integration, plus $150k to $500k a year in subscription fees, often tiered by customer numbers or API volume. Your own internal integration effort and PRD maintenance come on top. Pricing varies by contract and is usually quoted in AUD, so confirm current figures with vendors directly.
Written by the Apex Hub Pulse editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.