Banking API — Cross-Tasman
Single API for 200+ Australian and New Zealand Provider Connections
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.
Fiskil's Data API supports 200+ banks, lenders and energy providers across Australia and New Zealand. With New Zealand's Customer and Product Data Act (CPDA) bringing the NZ market online, Fiskil extends the same API to cover New Zealand's Big 4 banks — ANZ NZ, ASB (CBA subsidiary), BNZ (NAB subsidiary), and Westpac NZ — plus Kiwibank. For fintechs already operating in Australia, this represents a 19% expansion in addressable market (NZ population ~5.3M vs AU ~27M) through the same integration they already have. No new API, no new codebase — just more institutions in the same connection list.
The Challenge
Expanding from Australia to New Zealand — or vice versa — traditionally requires building separate bank connectivity, maintaining parallel infrastructure, and managing distinct institution relationships.
The Solution
Fiskil's Data API supports 200+ banks, lenders and energy providers across Australia and New Zealand through a single integration point, with a unified data model that eliminates cross-market engineering effort.
Capabilities
How Fiskil Helps
Comprehensive AU Coverage
Connect to 200+ banks, lenders and energy providers across Australia and New Zealand, including the Big 4 (CBA, NAB, ANZ, Westpac), major regionals (Macquarie, Bendigo, ING, Suncorp), credit unions, building societies and non-bank lenders.
NZ Big 4 + Kiwibank Access
Access ANZ New Zealand, ASB Bank, Bank of New Zealand (BNZ), Westpac New Zealand, and Kiwibank (expected June 2026) through the same API. These five institutions cover approximately 90% of NZ retail banking.
Unified Data Model
Account, transaction, balance, and customer data from both markets follows a single normalised schema. AUD and NZD transactions coexist in the same data structures with consistent field names.
Institution Discovery
Query available institutions by market (AU, NZ, or both), filter by capabilities, and present users with a unified bank selection interface that covers both countries.
Implementation
How It Works
Review Institution Coverage
Query Fiskil's institution endpoint to see all available AU and NZ banks. Filter by market, account types supported, and API capabilities to understand coverage for your use case.
Update Bank Selection UI
Include NZ institutions in your bank selection interface. Fiskil provides institution metadata including name, logo, country, and supported features to populate selection screens.
Handle Multi-Currency Data
Ensure your application correctly handles both AUD and NZD transactions. Fiskil returns ISO 4217 currency codes with all monetary amounts — no currency assumption is needed.
Launch in New Zealand
With the same API key and endpoints, your product now serves NZ users. No separate deployment, infrastructure, or integration is required for the NZ market.
In Practice
How Teams Use This
Trans-Tasman Fintech
A personal finance app with 200,000 AU users expands to New Zealand using the same Fiskil integration. NZ bank connections are added to the existing bank selection screen.
Acquired 15,000 NZ users within 3 months of launch, with zero additional engineering effort for bank connectivity. NZ users connected an average of 1.8 accounts each.
Cross-Border Lending Platform
A lender serving Australians relocating to New Zealand uses multi-market integration to verify income from AU bank accounts while establishing NZ banking relationships.
Enabled income verification for cross-border applicants, opening a previously unserved market segment of 30,000+ annual AU-to-NZ migrants.
Regional Accounting Platform
An accounting platform serving SMEs with operations in both countries connects to AU and NZ bank accounts for unified cash flow management and reconciliation.
Reduced manual bank statement uploads by 90% for cross-Tasman businesses, saving an average of 4 hours per week per business in reconciliation time.
Technical Details
What You Integrate With
API endpoints
GET /v1/institutionsGET /v1/institutions?market=nzGET /v1/accountsGET /v1/accounts/{accountId}/transactions
Data returned
Institution directory (AU + NZ)
Account details (normalised)
Transaction history (multi-currency)
Balance data (AUD + NZD)
Institution metadata (market, capabilities)
Authorisation
OAuth 2.0 / CDR consent (AU) + CPDA consent (NZ)
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
Neobanks
Instant Onboarding
Onboard customers instantly using banking data verification. Verify identity, income, and account ownership in seconds instead of days.
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
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.
Get started today
Talk to us about what you're building and we'll show you how we can help.
