Banking APIOpen Banking NZ

CPDA Accredited Requestor Compliance for New Zealand Open Banking

Meet Customer and Product Data Act (CPDA) accredited requestor obligations with Fiskil. Integrate with Payments NZ API Centre v2.3.3 standards, manage consumer consent, and access designated customer data from NZ banks.

Dodo logo
Nissan logo
Light logo
Red Zed logo
Wage Tap logo
BDO logo
Adyen logo
Alex bank logo
AGL logo
Brighte logo
Data Zoo logo
Alinta logo
Tango logo
Dodo logo
Nissan logo
Light logo
Red Zed logo
Wage Tap logo
BDO logo
Adyen logo
Alex bank logo
AGL logo
Brighte logo
Data Zoo logo
Alinta logo
Tango logo

The Customer and Product Data Act (CPDA), which came into force in December 2025, establishes New Zealand's framework for open banking and consumer data portability. Accessing NZ banking data requires CPDA compliance — but you don't need to navigate this yourself. Sign up with Fiskil and we handle the accreditation, consent management, and bank connectivity so you can focus on building your product.

The Challenge

The CPDA introduces new accreditation requirements and technical standards that businesses must meet to access consumer banking data in New Zealand.

The Solution

Fiskil provides pre-built compliance tooling and API infrastructure aligned to CPDA requirements and Payments NZ API Centre v2.3.3 standards, so you can focus on building your product rather than compliance plumbing.

Capabilities

How Fiskil Helps

CPDA Consent Lifecycle Management

Full consent lifecycle handling including collection, storage, renewal, and revocation in accordance with CPDA requirements. Consent records are maintained with audit trails for regulatory review.

Payments NZ API Centre v2.3.3 Conformance

Pre-built integration layer conforming to Payments NZ Account Information API specifications, including correct error handling, pagination, and event notification subscription.

Security Profile Alignment

OAuth 2.0 with FAPI 1.0 Advanced security profile implementation as required by the Payments NZ trust framework, including MTLS client authentication and signed request objects.

Compliance Dashboard and Audit Logging

Monitor consent status, data access logs, and API call history through a compliance dashboard. Export audit records for regulatory reporting and accreditation reviews.

Implementation

How It Works

1

Sign Up with Fiskil

Create your Fiskil account and tell us you want to access New Zealand banking data. We handle the CPDA accredited requestor requirements on your behalf.

2

Integrate Our API

Use Fiskil's Banking API to connect to NZ banks. We provide SDKs, documentation, and sandbox environments to get you up and running quickly.

3

Fiskil Handles Consent and Compliance

Fiskil manages the CPDA consent flows, security profiles, and bank connectivity. Your users see a seamless consent experience — you don't need to build any of it.

4

Access Customer Data

Start accessing account details, balances, and transaction history from NZ banks through Fiskil's unified API.

In Practice

How Teams Use This

Neobank Launching in New Zealand

A digital-only bank used Fiskil's compliance tooling to achieve CPDA accreditation and access customer transaction data from incumbent NZ banks for account switching and onboarding.

Achieved accreditation 6 weeks faster than estimated by leveraging pre-built compliance infrastructure, and onboarded 8,000 customers in the first quarter with compliant data access.

Personal Finance App Expanding to NZ

An Australian PFM app already using Fiskil's CDR integration expanded into New Zealand by adding CPDA accredited requestor capabilities through the same platform.

Launched NZ operations within 4 weeks using shared infrastructure, maintaining consistent compliance posture across both AU and NZ markets.

Accounting SaaS for NZ SMEs

A cloud accounting platform integrated CPDA-compliant bank feeds to automatically reconcile transactions for small business customers across multiple NZ banks.

Reduced manual bank feed setup from 3 days to under 10 minutes per customer, with full audit trail for every data access event.

Technical Details

What You Integrate With

API endpoints

  • POST /v1/consents
  • GET /v1/consents/{consentId}
  • DELETE /v1/consents/{consentId}
  • GET /v1/accounts
  • GET /v1/accounts/{accountId}/transactions

Data returned

Consumer consent records

Account details and balances

Transaction history

Product reference data

Consent audit logs

Authorisation

OAuth 2.0 with FAPI 1.0 Advanced / MTLS

Scheduled or batch data access.

Ready to get started?

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

FAQs

Get started today

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

Fiskil logo

© Fiskil 2026. All rights reserved.