Is Plaid Available in Australia? Coverage and the CDR

No. Plaid's API covers 20 countries and Australia isn't one of them. Here's how Australian bank data reaches your code through the CDR instead.

Oscar Watson-Smith
Oscar Watson-Smith

No. Plaid doesn't connect to Australian banks. Its API accepts 20 country codes, and Australia isn't one of them. In Australia, bank data moves through the Consumer Data Right (CDR), the government's open banking scheme, so getting your own CommBank or ANZ transactions into code means going through an accredited CDR provider. If you only want your own data, you don't need to become one, and that's what Redbark is for. (If you were looking for PLAID, the smartcard protocol from Services Australia, that's a different thing with the same name.)

Plaid's supported countries

Here's the full list of country codes Plaid's API accepts: US, GB, ES, NL, FR, IE, CA, DE, IT, PL, DK, NO, SE, EE, LT, LV, PT, BE, AT and FI. That's the United States, Canada, the UK and 17 European countries.

You may have read that Plaid and Basiq, an Australian data platform, announced a partnership in November 2020 to link Australian open banking with North America and Europe. Six years on, Australia still isn't on Plaid's list.

How Australian bank connections work: the CDR

Australia built its own route instead. The CDR lets you share your bank data with accredited third parties, starting with the four major banks in July 2020. Only providers accredited by the ACCC can offer services under it.

Your bankCommBank, NAB, ANZ, Westpac
Your consentYou choose what to share, under the CDR
Accredited data recipientFiskil, Basiq and others
Your app or codeDirectly, or as a CDR representative

How your bank data reaches an app under the CDR.

The accredited step is why there's no "Plaid for Australia" you can sign up to in an afternoon. Someone in the chain has to be an accredited data recipient.

Australian open banking API providers and CDR accreditation

The closest thing to Plaid depends on whose data you're reading: yours, or your customers'.

RouteWho it's forWhat you signWhat you get
A personal API (Redbark)A developer reading their own accountsA Redbark account, 7-day free trialAn API key for your own bank data, plus webhooks and MCP
An enterprise accredited data recipient (Basiq, Fiskil)A business serving its own customersA commercial contract, and usually a CDR representative arrangementA data platform to build a product on
CDR representativeA business that wants CDR data without its own accreditationA written contract with an accredited principal, who answers for your conductAccess under the principal's accreditation
Become accreditedA business that wants to hold accreditation itselfAn application to the ACCCDirect access, once you pass register onboarding

Accreditation is a real project. The ACCC runs it through the CDR Participant Portal, and you have to show you protect data, hold adequate insurance and have dispute resolution in place. Then you pass the register's onboarding, which includes conformance testing, before you can receive any data. Becoming a CDR representative skips it, but it's still a business contract. Neither suits someone building a dashboard for themselves.

A Plaid alternative for your own Australian bank data

We're a CDR representative of Fiskil. Fiskil holds the accreditation and we hold the contract, so you don't need either. You sign up, connect your bank, create an API key and call it:

curl -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Redbark-Version: 2026-10-01.wattle" \
  "https://api.redbark.com/v2/transactions?account=YOUR_ACCOUNT_ID&from=2026-11-01"

It's a normal REST API with bearer auth, JSON and an OpenAPI 3.1 spec. The developer guide walks through accounts, transactions and webhooks.

If you already use Plaid for US accounts, this is the part Plaid can't do. Redbark reads US banks through Plaid, Australian banks through the CDR and New Zealand banks through Akahu, all under one key. A Chase account and a CommBank account come back from the same endpoint in the same shape.

We don't store your transactions or balances. Data passes through to you. The API, webhooks and MCP server come with the Developer plan and up.

Australian bank coverage: the banks people connect most

Redbark connects to 100+ Australian banks and institutions. Here's where people actually point it.

CommBank
27.5%
NAB
12.4%
ANZ
10.0%
Westpac
9.7%
Macquarie Bank
8.5%
ING
8.3%

Share of active Redbark connections at the 17 Australian banks with 50 or more, 20 November 2026. Redbark data.

The big four plus Macquarie hold about 68% of those connections.

Connecting Australian banks to YNAB, Google Sheets or ChatGPT

Plenty of people searching for Plaid in Australia don't want an API at all. They want their transactions in the tool they already use. Redbark does that without code:

  • YNAB: native sync from Australian banks into your budget.
  • Google Sheets: transactions added to a sheet you choose.
  • ChatGPT and Claude: read-only access to your accounts through the MCP server, so you can ask questions about your spending.

Each one runs on the same CDR connection as the API, so you connect your bank once and pick where the data goes.

Want to try it with your own bank? Start with the bank API, or see the developer docs.

Oscar Watson-Smith

About the author

Oscar Watson-Smith

Founder, Redbark

Oscar started his career at Macquarie Group on the engineering side of the Commodities & FX team. Since then, he’s worked in payments, security and infrastructure engineering for Australian startups and global tech organisations such as Datadog, Figma and Vanta. He loves personal finance and wants to make managing money easier for every Aussie.

Oscar on GitHub