feat: Add Australian Bank Sync (Redbark)

[oscargws]

What

Adds Redbark as a native bank sync provider for Australian accounts. Redbark pulls AU bank data through the official open banking (CDR) framework via Fiskil, an accredited data recipient.

Worth explaining why an aggregator is involved at all: Australian open banking access is a lot more gated than most countries. There's no personal API tier, you need an Australian Pty Ltd company stood up, CDR compliance requirements met, penetration tests, security audits and so on before the banks will hand over data. That's not something a self hoster can do themselves, which is why Australians can't just plug into their banks directly the way Up or SimpleFin users can. Redbark is the accredited middle layer that makes AU bank data reachable with just an API key.

Right now Australians using Sure connect through sure-sync, a docker container I maintain that pulls transactions from Redbark and pushes them into Sure through Sure's REST api on a schedule. It's sitting at 7,000+ downloads with a couple hundred active users, and the most common request I get from them is native support, because nobody wants to run and schedule a second self hosted service just to feed their Sure instance. The container also means hand mapping account ids in env vars, transactions only (no balances or institution metadata), and one more thing to keep updated.

This makes it first class: paste a Redbark api key in settings -> providers and link accounts directly, no extra container to run.

How it works

Same shape as the Lunchflow/SimpleFin integrations:

• RedbarkItem (encrypted api key, syncable) + RedbarkAccount (encrypted raw payloads), with the usual importer / syncer / provided / unlinking split
• Provider::Redbark httparty sdk against api.redbark.com/v1, limit/offset pagination
• Registered via Provider::Factory, wired into family, the providers settings panel, and the account setup flow (Questrade style account type picker, skipped accounts persist an ignored flag)
• Amounts arrive CDR signed (positive = money in) so they get negated to Sure's convention
• Scope is banking connections only. Redbark also exposes brokerage connections, those are detected by category and skipped (different endpoint, not a fit for the transactions pipeline)

Credentials

Api key is a deterministic encrypted column (Encryptable), validated on every save. Rotating the key re-arms a requires_update item. Raw provider payloads are encrypted jsonb. The password field renders with value: nil so the key never round-trips to the browser.

Rate limits and failures

• 429 and 5xx retry with exponential backoff + jitter, capped at 30s
• Auth failures mark the item requires_update and surface a reconnect prompt
• Every sync failure goes through DebugLogEntry.capture so it shows in the super admin debug ui, no raw response bodies in logs or errors
• Balance batch calls exclude stale/non-banking accounts up front and fall back per account, so one bad id can't freeze balances for the rest
• Account pruning is guarded so a transient empty response can never wipe linked accounts, and nil balances never write a $0 anchor

Reconciliation

No parallel data path. Transactions flow through the existing Account::ProviderImportAdapter (dedupe on redbark_<id> + source), balances through Account::Processor via set_current_balance, merchants through ProviderMerchant. Pending transactions refresh to posted on later syncs.

Migrations

• create_redbark_items_and_accounts (Migration[7.2], NOT NULLs on lifecycle columns, unique item+account index)

Testing

bin/rails test: 5961 runs, 23886 assertions, 0 failures, 0 errors
redbark tests alone: 52 runs, 90 assertions, 0 failures, 0 errors, 0 skips
rubocop: 2156 files inspected, no offenses detected
brakeman: no warnings
erb_lint: no errors

Also ran end to end against my live Redbark account (mixed banking + brokerage connections). Explicitly tested:

• Account discovery and linking, including the skip/ignore flow
• 90 day initial backfill, then incremental sync with the 7 day lookback window
• Balance updates, including the per-account fallback when a batch is rejected
• Sign conventions verified against real salary and transfer data
• Pending -> posted transaction refresh
• Brokerage connections correctly excluded
• Key rotation, unlink, and item deletion