Banking API — Cross-Tasman
CDR Data Standards vs Payments NZ API Centre: Unified Integration
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.
Australia's CDR Data Standards and New Zealand's Payments NZ API Centre (currently v2.3.3) both enable open banking, but they differ significantly in API design, data formats, security models, and endpoint structures. CDR Data Standards follow a prescriptive, government-mandated specification with detailed payload schemas. Payments NZ API Centre draws on UK Open Banking origins with its own adaptations for the New Zealand market. For fintechs building across both markets, these differences mean duplicate integration effort, separate testing regimes, and ongoing maintenance of two codebases. Fiskil eliminates this by normalising both standards into a single, consistent API.
The Challenge
CDR Data Standards and Payments NZ API Centre v2.3.3 solve similar problems but differ in API design, data formats, security, and error handling — creating engineering overhead for cross-market products.
The Solution
Fiskil maintains full implementations of both CDR Data Standards and Payments NZ API Centre v2.3.3 and presents a unified API to clients, handling all translation and normalisation internally.
Capabilities
How Fiskil Helps
Unified Data Model
Fiskil maps CDR and Payments NZ data schemas to a single normalised model. Account types, transaction categories, balance representations, and metadata fields are standardised regardless of source.
Security Profile Abstraction
Handle FAPI 1.0 Advanced (CDR) and Payments NZ OAuth security profiles through Fiskil's single authentication layer. Client applications authenticate once; Fiskil manages the downstream security negotiation per institution.
Error Normalisation
CDR and Payments NZ error responses are translated into a consistent error schema. Your application handles one set of error codes regardless of which standard the underlying institution uses.
Version Management
Fiskil tracks version changes in both CDR Data Standards and Payments NZ API Centre, migrating to new versions as they are released without requiring client-side changes.
Implementation
How It Works
Integrate with Fiskil API
Implement against Fiskil's unified Banking API specification. The API follows a consistent design regardless of underlying standard — you don't need to learn CDR Data Standards or Payments NZ API Centre separately.
Test Against Both Markets
Use Fiskil's sandbox environment, which provides test institutions for both Australian (CDR) and New Zealand (Payments NZ) banks. Verify that your application handles data from both markets correctly.
Handle Normalised Responses
Process account, transaction, and balance data using Fiskil's normalised schema. Currency (AUD/NZD), date formats, and institution-specific fields are standardised in every response.
Deploy to Production
Go live with access to 200+ banks, lenders and energy providers across Australia and New Zealand through the same production API endpoint.
In Practice
How Teams Use This
Accounting Software Provider
An accounting platform serving AU and NZ small businesses uses Fiskil's unified API to pull bank feeds from both markets, replacing separate integrations with each standard.
Reduced bank feed integration code by 55% and eliminated the need for separate AU/NZ engineering teams for banking connectivity.
Personal Finance App
A budgeting app available in both countries uses Fiskil to aggregate accounts from Australian and New Zealand banks into a single user view.
Shipped NZ support in 2 weeks using the existing AU integration, versus the 3-month estimate for a direct Payments NZ API Centre implementation.
Compliance Analytics Platform
A regtech provider analyses transaction data from both markets for AML/CTF compliance, using Fiskil's normalised data model to apply consistent rules across jurisdictions.
Deployed consistent transaction monitoring rules across both markets without jurisdiction-specific data transformation logic.
Technical Details
What You Integrate With
API endpoints
GET /v1/accountsGET /v1/accounts/{accountId}/transactionsGET /v1/accounts/{accountId}/balanceGET /v1/institutions
Data returned
Normalised account schema
Normalised transaction schema
Institution metadata (jurisdiction, standard version)
Multi-currency balances (AUD, NZD)
Unified error responses
Authorisation
OAuth 2.0 (abstracted FAPI 1.0 Advanced + Payments NZ profile)
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.
Cross-Tasman
Dual Compliance
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.
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.
Get started today
Talk to us about what you're building and we'll show you how we can help.
