Akahu is free for consumers.
Our indicative pricing for developers is described below. Once you know the functionality that you need and your expected volumes, we can confirm the pricing that we can offer.
If you simply want API access to your personal data, check out how to create a Personal App. We don't charge fees for accessing your own data.
If you require a custom terms, please contact our team for custom pricing.
Our standard terms support transparent pay-as-you-go pricing.
$0.15 per successful payment request.
This fee only applies if the payment is initiated successfully by the relevant bank.
If you're requesting one-off data connectivity from your users, our fees are based on specific actions. The most common examples are below.
Loan applications and other financial applications: $5.00 per application. (Where relevant, an application includes multiple applicants, multiple data connections, PDF extraction, and data enrichment.)
Identity and bank account verification: $1.00 per successful request.
Most apps prefer a fixed monthly user fee (rather than variable API query fees) in order to have certainty of their unit economics.
We can confirm our monthly user fees once we understand the functionality that you require.
Typically between $0.50-$2.50 per user per month.
(Where relevant, the monthly user fee includes multiple connections, data refreshes, and data enrichment.)
Our standard terms support transparent pay-as-you-go pricing.
$5.00 per application.
(Where relevant, an application includes multiple applicants, multiple data connections, PDF extraction, and data enrichment.)
Once we understand the functionality you need, we’ll set you up with API credentials to build and test with our API free of charge.
The Customer and Product Data Act 2025 requires New Zealand's largest five banks to provide open banking APIs to "accredited requestors".
There are two options for you to access these regulated open banking APIs - become an "accredited requestor" yourself, or use an intermediary service like Akahu.
This section describes the key factors that you may want to consider when assessing these two options.
Direct participants will incur an initial accreditation fee, annual accreditation fees, and annual levies. These fees are described by MBIE on this page.
You'll need to purchase and maintain certificates that are required as part of the authentication process when accessing regulated open banking APIs with each bank.
Direct participants are required to meet insurance and security requirements. These requirements are described by MBIE on this page.
You'll need to develop and maintain integrations with each bank, including upgrading to new API versions that are released over time.
You'll need to ensure that consent information meets the prescribed disclosure requirements.
If you're requesting ongoing connectivity, you'll need to provide an interface for users to view and revoke any ongoing consents. And you'll need to ensure that users are notified about ongoing consents in accordance with the regulation.
You'll need to retain specified records about each request.
You'll need to provide a complaints management process that meets the regulatory requirements.
If you access regulated open banking APIs via Akahu, you will not need to incur the direct and indirect costs that are described above.
Akahu will deliver all of these operational requirements described above, meaning that it would be optional for you to replicate any of those services within your product.
The regulated open banking system provides coverage for consumers who hold accounts with ANZ, ASB, BNZ, and Westpac. Kiwibank will join this group by the end of 2026. If your product requires broader coverage, such as coverage of the smaller banks, non-bank card issuers, KiwiSaver providers, investment platforms, or fintechs, then Akahu can provide that additional coverage.
The raw data available via regulated open banking APIs typically requires significant extra processing before it becomes useful for use cases such as loan applications, accounting and tax solutions, and personal financial management tools. Akahu transforms the raw data into a consistent format across all connected accounts, classifies transfers within the dataset for a relevant user, and categorises income and expenses. For example, Akahu automatically categorises over 90% of transactions processed via card scheme, EFTPOS, and direct debit.
You'll be assigned a senior member of our team to support your ongoing use of our API.
We love hearing about your ideas and requirements. If you want us to extend or modify our API, just ask and we promise a fast response so you're not left wondering.
Join our Slack workspace for developers that are working with our API. Get support from the community and our team.
