Resources
Do you need CDR accreditation to use a banking API?
Compare representative and sponsored access to Australian open banking data, see which providers have acted as principals and check what your fintech needs before going live.
An Australian fintech can offer a service that uses customer banking data without holding unrestricted accreditation under the Consumer Data Right (CDR). If your app needs transaction data and your business wants to remain unaccredited, one route is to become a CDR representative. An unrestricted accredited business acts as your principal and supplies the data for the service you agree to provide. If you want your business to hold its own accreditation, sponsored accreditation is a separate option. ACCC accreditation guidelines
Fiskil, Basiq and Mastercard Asia/Pacific each identify representatives in their Australian CDR policies. Start with the role your product needs, then check the provider’s legal entity, public record and willingness to support that particular service.
Who collects the data under each route?
| What your fintech wants to do | Your fintech’s role | How data reaches the service |
|---|---|---|
| Offer its own budgeting app without becoming accredited | CDR representative under a written agreement with one unrestricted accredited principal | The customer consents to the principal collecting the data and the representative using it for the agreed service. The arrangement must appear on the CDR Register before the representative starts operating under it. |
| Hold its own accreditation and use a partner for collection | Affiliate with sponsored accreditation and a sponsorship arrangement | The affiliate can obtain data through its unrestricted sponsor, its sponsor’s outsourced service provider or another accredited person. Sponsored accreditation excludes direct collection from a bank as data holder. |
| Process transactions for another CDR business | Outsourced service provider (OSP) working under a CDR outsourcing arrangement | The OSP performs the agreed work for an accredited person or representative. An OSP may collect on behalf of an unrestricted accredited person. That contract alone gives the processor no independent right to use the feed for its own app. |
| Collect directly from participating banks for its own service | Unrestricted accredited person | The business obtains accreditation and completes technical onboarding. It can then request the customer data covered by the consumer’s consent and authorisation. |
The distinction matters when drawing your data flow. A bank may hold the accounts you need. Its consumer open banking page explains how customers share data, while the agreement with your principal or sponsor establishes who can collect it for your service. The ACCC compares these roles in sections 1, 2 and 9 of its guidelines. Rules 1.10, 1.10AA and 1.10D define the relevant arrangements. ACCC pathway comparison · CDR Rules
Does your app need a transaction feed?
Consider a budgeting app that lets customers browse and categorise individual transactions. Its principal needs to assess that ongoing use of transaction data. Now consider a merchant that only needs confirmation that a customer owns the account they nominated. A permitted CDR insight, disclosed with the customer’s specific consent, may answer that narrower question. The OAIC explains which verification purposes qualify and what information the result may contain. A full transaction history falls outside an insight disclosure. OAIC guidance on CDR insights
For a provider proposal described as “use consent” or “business consumer disclosure”, ask who receives the data, which consent covers the disclosure and whether the customer qualifies. These distinctions affect the design. For example, the ACCC’s representative fact sheet explains that a representative cannot disclose data under a business consumer disclosure consent. ACCC representative fact sheet
Which providers have acted as a CDR principal?
The CDR Register listed the following three legal entities as active at the unrestricted level on 19 November 2026. Their policies provide a second piece of evidence by naming a representative and describing the service. Search by accreditation number to check the current record. CDR Register of current providers
| Provider and accreditation number | Example in its CDR policy |
|---|---|
| Fiskil Pty Ltd · ADRBNK000246 | Fiskil lists Flagbase Pty Ltd, which operates BankSync, as a representative. Its service lets customers share account, balance and transaction information with tools they select. Fiskil CDR policy, representative arrangements |
| Basiq Pty Ltd · ADRBNK000208 | Basiq lists Achieve Moorr Pty Ltd, operator of the Moorr household finance and property planning app, among its representatives. Basiq CDR policy, representative arrangements |
| Mastercard Asia/Pacific Pte. Ltd. · ADR002024 | Mastercard names Now Finance Group Pty Ltd as a representative and describes its use of CDR data to verify a consumer’s financial position for a lending application. Mastercard CDR policy, section 9 |
Ask a prospective principal whether it will support your use case. If you intend to apply for sponsored accreditation, ask specifically whether the legal entity will sign a sponsorship arrangement. A provider’s existing representative agreement answers a different question.
What to agree before connecting real accounts
Give the provider a one-page description of the customer, the service, the data it needs and every system or organisation that will receive that data. Use it to agree on three things.
- The parties and the purpose. Record the legal entities, participation route, permitted use, account types and data fields. For a representative arrangement, identify the principal responsible for the representative’s handling of CDR data and confirm when the arrangement will appear on the Register. OAIC representative guidance
- What happens when sharing ends. Walk through a customer withdrawing consent. Agree who receives the withdrawal, stops collection, tells the app and deals with data already held. Record who handles complaints or incidents. Fiskil’s representative responsibility checklist
- What production approval requires. Fiskil’s Quick Start covers credentials, end users and auth sessions. Its Go Live Checklist covers the onboarding questionnaire, security and data management. Use the sandbox to test the customer journey, then confirm the agreement and production requirements with Fiskil before requesting live data. Quick Start · Go Live Checklist
If you’re considering Fiskil as your principal, bring that description to the first conversation. It gives both teams a concrete basis for deciding whether the arrangement fits your product. Discuss your use case with Fiskil


