Do I need separate accreditation in both Australia and New Zealand?

Integrating through Fiskil can simplify accreditation requirements. For CDR, Fiskil supports sponsored accreditation under our principal ADR status. For CPDA, the accreditation model is being finalised by MBIE, and Fiskil will support the equivalent pathway as it becomes available.

How do the consent models differ between CDR and CPDA?

CDR consent is based on data clusters defined in the CDR Rules, with specific duration limits and granular scope. CPDA consent operates under New Zealand's Privacy Act 2020 framework with different scope definitions. Fiskil abstracts these differences so your application uses a unified consent interface.

Are the API responses identical for AU and NZ institutions?

Fiskil normalises responses into a unified data model. Account and transaction data follow the same schema regardless of whether the source is an Australian CDR data holder or a New Zealand CPDA participant.

What happens when regulations change in one jurisdiction?

Fiskil monitors both regulatory environments continuously. When changes occur, Fiskil updates the platform to maintain compliance and notifies affected clients with impact assessments and any required action items.

Which regulator handles complaints — ACCC or MBIE?

Complaints are handled by the regulator in the jurisdiction where the data holder operates. For Australian institutions, the ACCC and OAIC have oversight. For New Zealand institutions, MBIE and the NZ Privacy Commissioner have jurisdiction. Fiskil's compliance layer routes obligations to the correct regulator.

Banking API — Cross-Tasman

CDR and CPDA Dual Compliance for Australia and New Zealand

Implement compliant open banking across both Australia and New Zealand from a single platform. Fiskil handles the differences between CDR (ACCC-regulated) and CPDA (MBIE-regulated) accreditation, consent, and data standards.

Expanding open banking operations across the Tasman means complying with two distinct regulatory frameworks: Australia's Consumer Data Right (CDR), regulated by the ACCC and OAIC, and New Zealand's Customer and Product Data Act (CPDA), overseen by MBIE. These frameworks share philosophical alignment but differ materially in accreditation models, consent requirements, data holder obligations, and enforcement mechanisms. Fiskil provides a single integration layer that abstracts these differences, enabling fintechs and data recipients to operate in both markets without building and maintaining separate compliance infrastructure.

The Challenge

Operating across Australia and New Zealand requires navigating parallel but different open data regimes, each with its own regulator, accreditation process, and technical requirements.

The Solution

Fiskil abstracts the differences between CDR and CPDA into a single API, handling jurisdiction-specific consent, accreditation requirements, and data formatting transparently.

Capabilities

How Fiskil Helps

Jurisdiction-Aware Consent Management

Automatically apply the correct consent model based on the data holder's jurisdiction. CDR data cluster consents for Australian institutions; CPDA-compliant consent scopes for New Zealand institutions.

Dual Accreditation Support

Fiskil maintains accreditation under both frameworks, so clients integrating through Fiskil can access both markets via sponsored or principal accreditation paths without managing dual registrations independently.

Unified Security Model

Implement FAPI 1.0 Advanced (CDR requirement) and Payments NZ security profiles through a single authentication flow. Token management, MTLS, and PKCE are handled per-jurisdiction automatically.

Regulatory Change Monitoring

Fiskil tracks rule changes in both CDR (ACCC rule amendments) and CPDA (MBIE regulatory updates) and updates the platform to maintain compliance, insulating clients from regulatory maintenance.

Implementation

How It Works

Single API Integration

Integrate with Fiskil's Banking API once. The API interface is identical for both markets — you don't build separate integrations for AU and NZ.

Configure Jurisdictional Settings

Set your compliance parameters for each market. Fiskil's dashboard allows configuration of consent durations, data retention policies, and notification preferences per jurisdiction.

Route Connections by Market

When a user connects a bank account, Fiskil automatically detects the institution's jurisdiction and applies the correct regulatory framework — CDR for Australian banks, CPDA for New Zealand banks.

Monitor Compliance Dashboard

Track consent status, data access logs, and compliance metrics for both markets in a unified dashboard. Generate jurisdiction-specific compliance reports for audits.

In Practice

How Teams Use This

Trans-Tasman Neobank

A neobank operating in both Australia and New Zealand uses Fiskil's dual compliance layer to offer account aggregation across both markets without maintaining two separate compliance teams.

Reduced compliance infrastructure cost by 60% compared to maintaining separate AU and NZ data access systems, while passing regulatory audits in both jurisdictions.

Lending Platform Expansion

An Australian lending platform expands to New Zealand, using Fiskil to handle CPDA accreditation and compliance while retaining their existing CDR integration.

Launched NZ operations in 8 weeks instead of the estimated 6 months, with zero compliance incidents in the first year.

Wealth Management Firm

A wealth management firm serves clients with assets in both countries and uses Fiskil to aggregate financial data across AU and NZ institutions under compliant consent.

Provided unified cross-border financial views to 3,000+ clients, improving adviser productivity by 40% through elimination of manual data collection.

Technical Details

What You Integrate With

API endpoints

GET /v1/accounts
GET /v1/accounts/{accountId}/transactions
POST /v1/consent/create
GET /v1/compliance/status

Data returned

Account details (AU + NZ formats)

Transaction history

Consent records

Compliance status per jurisdiction

Regulatory audit logs

Authorisation

OAuth 2.0 / FAPI 1.0 Advanced (CDR) + Payments NZ security profile (CPDA)

Real-time data access.

Ready to get started?

Get your API keys today and start building with Fiskil's Banking API.

FAQs

Related Use Cases

Fintech

Account Aggregation

Enable users to connect and view all their bank accounts in one place. Fiskil's account aggregation API provides real-time access to accounts, balances, and transactions from 200+ banks, lenders and energy providers across Australia and New Zealand.

Learn more

Cross-Tasman

Data Standards Comparison

Navigate the technical differences between Australian CDR Data Standards and New Zealand's Payments NZ API Centre v2.3.3. Fiskil normalises both standards into a single API, eliminating the need to implement and maintain two separate integrations.

Learn more

Cross-Tasman

Multi-Market Integration

Connect to 200+ banks, lenders and energy providers across Australia and New Zealand through one API. Fiskil's multi-market integration provides a unified data model and 19% addressable market expansion for trans-Tasman products.

Learn more

Get started today

Talk to us about what you're building and we'll show you how we can help.

Speak with a Fiskil integration expert today