Skip to main content
A connection is a link to your bank. Each connection can include multiple accounts, for example a transaction account and a savings account at the same bank.

Connection types

Australian banks

Connect via Fiskil (CDR). Used for syncing transactions.

New Zealand banks

Connect via Akahu, NZ’s open banking platform. Used for syncing transactions.

United States banks

Connect via Plaid. Used for syncing transactions.

Brokerages

Connect brokerage accounts to sync holdings and trades. Available on the Professional plan (and during your trial).

Connections list

Connections are grouped by institution. Each group has a header row with the institution logo, name, status pill, account count, last synced date, and a three-dot menu. Below the header, a table lists each account on the connection with its name, masked number, type (Transaction, Savings, Credit Card, Loan, Investment, or Term Deposit), and per-account status. Select the pencil beside a bank or brokerage account name to give it a nickname. Nicknames can be up to 80 characters and appear anywhere Redbark shows that account. Leave the nickname blank to restore the name supplied by the provider.

Statuses

Supported institutions

Australian banks

Redbark connects to Australian banks through the Consumer Data Right (CDR / Open Banking) framework. Any bank or Authorised Deposit-taking Institution (ADI) that participates in the CDR is supported. This includes all major banks (CBA, Westpac, NAB, ANZ) and most smaller banks, credit unions, and building societies.

New Zealand banks

Redbark connects to New Zealand banks through Akahu, New Zealand’s open banking platform. Supported banks:
  • ANZ New Zealand
  • ASB
  • BNZ
  • The Co-operative Bank
  • Heartland Bank
  • Kiwibank
  • Rabobank New Zealand
  • SBS Bank
  • TSB
  • Westpac New Zealand
New Zealand does not have a legislated regime like Australia’s CDR; Akahu fills that role as the standard open finance platform used by NZ apps. Access is read-only and amounts come through in NZD.

United States banks

Redbark connects to US banks and credit unions through Plaid, the connectivity platform most US finance apps use. Plaid covers the large national banks, regional banks, credit unions, and most US credit card issuers. This includes Bank of America, Chase, Wells Fargo, Capital One, U.S. Bank, PNC Bank, Truist, TD Bank, and many more. Access is read-only and amounts come through in USD. The United States has no legislated open banking regime like Australia’s CDR, so US connections are not CDR connections and are not covered by CDR consent rules.

American Express in Australia

Australian American Express cards are not yet supported through the CDR. The framework initially only covered traditional banks and ADIs. Because Amex operates as a credit card issuer rather than a bank, they were outside that scope. The Australian Government updated the CDR rules in March 2025 to bring non-bank lenders like Amex into the framework. That rollout begins in tranches from July 2026. Once Amex completes its Australian enrolment, Redbark will be able to access its data immediately.
Australian Amex support depends on American Express meeting the government’s CDR enrolment timeline. Exact availability is not yet confirmed.

Brokerages

Brokerage connections are available on the Professional plan (and during your trial). These connect through SnapTrade and support Australian and international brokerages.

Adding a connection

Click Add Connection. The picker offers four options:
  • AU Banks — Australian bank accounts via Fiskil
  • NZ Banks — New Zealand bank accounts via Akahu
  • US Banks — United States bank accounts via Plaid
  • Brokerage — investment accounts via SnapTrade (Professional plan, and during your trial)

Australian bank

Opens the Fiskil consent flow. Select your bank, log in, and grant consent through the Consumer Data Right (CDR). Your accounts sync automatically once consent is granted.
Australian bank connections use the Consumer Data Right framework. Your bank credentials are handled by Fiskil and are never stored on Redbark servers. CDR consents expire after 12 months. See Consents for details.

Business bank accounts

Your bank decides whether a business profile is eligible for Open Banking data sharing. Before contacting Redbark support:
  1. Contact your bank and ask it to enable Open Banking data sharing for the business profile.
  2. Complete any authority setup the bank requires, such as becoming a sharing delegate or nominated representative.
  3. Ask the bank to confirm that the specific business profile is enabled, then try connecting it again in Redbark.
If the bank’s connection flow still says the profile is ineligible, contact the bank’s Open Banking support team. Redbark cannot change eligibility or delegation settings held by your bank.

New Zealand bank

Opens the Akahu authorisation flow. You are redirected to Akahu, choose your bank, log in with your bank, and pick which accounts to share. Akahu hands Redbark a read-only token for those accounts, and you land back in Redbark with the connection ready. Your accounts sync automatically once the connection is established. A single Akahu authorisation covers every account you chose to share, and you can add more accounts later by connecting again. Access is strictly read-only: Redbark can read balances and transactions but can never move money or make changes at your bank.
Your bank credentials are handled by your bank and Akahu, and are never seen or stored by Redbark. You can withdraw access at any time by deleting the connection in Redbark or revoking it from your Akahu account; either way the tokens are revoked and the connection’s data is deleted on both sides.

United States bank

Opens Plaid Link, a secure modal that runs inside Redbark. Search for your bank, log in, and pick which accounts to share. Some banks hand you off to their own login page and send you straight back to Redbark when you are done. Your accounts sync automatically once the connection is established. Access is strictly read-only: Redbark can read balances and transactions but can never move money or make changes at your bank.
Your bank credentials are handled by your bank and Plaid, and are never seen or stored by Redbark. If your bank later asks you to log in again, the connection shows as Disconnected and a Reconnect action reopens Plaid Link. Reconnecting repairs the existing connection, so your accounts and syncs stay as they are.

How quickly do transactions appear?

For Australian connections, transaction data is made available by your bank through the CDR framework, not by Redbark. How quickly new transactions appear depends on your bank and connection provider.
  • Some banks make data available every few hours. Others update once a day.
  • There is no consistent pattern across banks, and the CDR rules do not specify how frequently banks must publish new data.
  • In practice, most transactions appear within a few hours to around 18 hours after they post at your bank.
Redbark syncs the latest data your bank or connection provider has published. If a transaction has posted at your bank but hasn’t appeared in Redbark yet, it has not yet been made available to Redbark. The same applies outside Australia. NZ connections depend on Akahu’s refresh cadence and US connections on Plaid’s, and in both cases Redbark syncs whatever the provider has already collected from your bank.
Only posted (settled) transactions are synced by default. Pending transactions are excluded to avoid duplicates when they later post with updated details. If you need earlier visibility, you can enable pending transactions per sync as an experimental setting.

Refreshing a connection

Use the Refresh button on the connections page to re-trigger the syncs that depend on your connections. Refresh runs the per-destination sync tasks with a short debounce and an idempotency window, so back-to-back clicks coalesce into a single run. It does not call your bank directly — Redbark pulls whatever data your bank or connection provider has already made available.

Deleting a connection

Select Delete from the three-dot menu to remove a connection. Any syncs that depend on accounts from this connection are immediately disabled, and the accounts, tokens, and connection row are queued for deletion in the background.