Banking API — Open Banking AU
Access CDR-Designated Banking Datasets in Australia
Retrieve CDR-designated banking data including accounts, transactions, balances, payees, and product reference data from all major Australian banks through Fiskil's Consumer Data Right API integration.
Australia's Consumer Data Right (CDR) designates specific banking datasets that accredited data recipients can access with consumer consent. These datasets cover account details, transaction history, balances, direct debits, scheduled payments, payees, and product reference data across all ADI (Authorised Deposit-taking Institution) data holders. Fiskil provides a unified API layer that simplifies access to these CDR-designated datasets, handling the technical complexity of FAPI 2.0 security profiles, consent token management, and data holder API variations.
The Challenge
While the CDR provides a legal right to access consumer banking data, the technical implementation involves significant complexity that slows time to market.
The Solution
Fiskil handles the CDR's technical complexity and presents CDR-designated banking data through a clean, developer-friendly API.
Capabilities
How Fiskil Helps
Full CDR Data Cluster Coverage
Access all CDR-designated banking data clusters: accounts, transactions, balances, direct debits, scheduled payments, payees, and product reference data through typed API endpoints.
FAPI 2.0 Security Handled
Fiskil manages the full FAPI 2.0 security stack including PAR, JAR, MTLS, and token management. Your application authenticates with Fiskil using standard OAuth 2.0.
Data Holder Abstraction
A single API call returns data regardless of which of the 100+ CDR data holders the account is held at. Fiskil normalises the response format and handles data holder-specific quirks.
Quarterly Standards Compliance
Fiskil maintains conformance with the latest Consumer Data Standards version, so your integration is never out of date when the ACCC publishes specification updates.
Implementation
How It Works
Establish Your Access Model
Determine your CDR access model: become an Accredited Data Recipient (ADR) directly, operate as a CDR Representative under a principal ADR, or use Fiskil's sponsored access model. Fiskil supports all three pathways.
Configure Data Cluster Scopes
Define which CDR data clusters your application needs (e.g., accounts + transactions, or balances only). Fiskil maps these to the correct Consumer Data Standards scopes for consent requests.
Initiate Consumer Consent
Use Fiskil's consent API to generate a consent request. The consumer is redirected to their bank to authorise data sharing for the specified clusters and duration (up to 12 months).
Retrieve and Use Banking Data
Call Fiskil's data endpoints to retrieve accounts, transactions, balances, and other designated data. Data is returned in a normalised JSON format with pagination support.
In Practice
How Teams Use This
Mortgage Broker Affordability Assessment
A mortgage aggregator platform used Fiskil's CDR integration to pull 12 months of transaction data from applicants' bank accounts for automated income verification and expense analysis.
Loan assessment time reduced from 5 business days to under 30 minutes, with more accurate affordability calculations based on actual banking data rather than self-reported figures.
BNPL Provider Risk Scoring
A buy-now-pay-later provider accessed CDR transaction data to assess customer repayment capacity before approving credit, supplementing traditional bureau checks.
Default rates reduced by 18% after incorporating CDR banking data into risk models, while maintaining approval rates by identifying creditworthy applicants missed by bureau-only assessment.
Government Benefit Eligibility Verification
A government services portal used CDR data access to verify applicants' financial circumstances for means-tested benefits, with consumer consent.
Processing time for benefit applications reduced by 70%, and fraud detection improved through real-time verification against actual bank account data.
Technical Details
What You Integrate With
API endpoints
GET /v1/accountsGET /v1/accounts/{accountId}/transactionsGET /v1/accounts/{accountId}/balanceGET /v1/accounts/{accountId}/direct-debitsGET /v1/products
Data returned
Account details and metadata
Transaction history (up to 7 years)
Current and available balances
Direct debits and scheduled payments
Product reference data (rates, fees, features)
Authorisation
OAuth 2.0 / FAPI 2.0 with PAR and JAR
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
Open Banking NZ
NZ Bank API Integration
Integrate with all major New Zealand bank APIs through a single connection. Fiskil provides unified access to ANZ NZ, ASB, BNZ, Westpac NZ, and Kiwibank via Payments NZ API Centre v2.3.3 standards.
Open Banking AU
CDR Accreditation
Navigate CDR accreditation pathways — ADR, CDR Representative, or Sponsored — with Fiskil. Meet ACCC requirements, implement FAPI 2.0 security, and get to market faster with pre-built compliance infrastructure.
Open Banking AU
CDR Consent Management
Manage the full CDR consent lifecycle including collection, amendment, renewal, and revocation. Fiskil's consent management API ensures compliant handling of consumer data sharing authorisations across all Australian banks.
Get started today
Talk to us about what you're building and we'll show you how we can help.
