When you connect a bank through Open Banking, you don't hand over blanket access. You choose which accounts and which categories of data to share — and it's all read-only. Here's what's actually on offer under the Consumer Data Right (CDR).
You choose what to share
On the consent screen you select the specific accounts you want to connect, then the categories of data to share for them. The categories you'll typically see include:
- Account name, type and balance
- Account numbers and features
- Transaction details (dates, amounts, descriptions)
- Regular payments, such as direct debits and scheduled payments
You can share as little or as much as you like, and you can connect some accounts while leaving others out entirely.
What Redbark requests
Redbark only needs to read your accounts and transactions so it can sync them to your chosen destination. So that's all we ask for: read-only access to your account details and transactions. You pick the exact accounts and categories on Fiskil's consent screen, and you can change or revoke them at any time — see consent duration.
Open Banking is read-only
This is worth being clear about: the CDR data-sharing right is read-only. It lets an app read your accounts, balances and transactions — it cannot move money, make payments, or change your accounts. (Initiating payments is a separate, future part of the CDR called action initiation, which Redbark does not use.)
Nothing is stored
Even the data you do share isn't warehoused by Redbark. Transactions are proxied live from your bank to your destination at sync time; we keep consent records, encrypted tokens and minimal account metadata, never your transaction amounts, descriptions or balances. There's more detail on our Compliance page.
See where your data can go in bank-to-destination flows, or browse the banks we support.