Skip to main content
Start with the symptom you can see. Each guide explains what Redbark controls, what your bank or destination controls, and what to try next.

Transactions are late or missing

Check posting status, bank data availability, and the latest sync run.

A connection needs attention

Understand Disconnected, Fetching, Stuck, and consent-related states.

An account is missing

Check whether the account was selected and made available by your bank.

Connect a business bank account

Set up the sharing authority required by your bank.

Pending transactions

Learn why Redbark waits for transactions to settle by default.

Duplicate transactions

Check pending settings and other import paths before contacting support.

​
Destinations and API

Map YNAB categories

Choose how bank categories arrive in your YNAB budget.

Configure YNAB Payee and Memo

Control which Redbark fields populate each YNAB field.

Fix webhook deliveries

Diagnose response codes, timeouts, public reachability, and auto-disable.

Verify webhook signatures

Validate HMAC signatures against the raw request body.

Replay webhook data

Choose between Hard resync and Replay everything.

Fix API authentication

Check the host, Bearer header, key status, version, and plan access.

​
Frequently asked questions

Most posted transactions appear within a few hours to around 18 hours. Your bank or connection provider controls when new data becomes available. Check a delayed transaction.
Redbark excludes pending transactions by default because banks can change their ID, amount, or description when they settle. Learn about pending transactions.
Yes, when your bank has enabled Open Banking sharing for the business profile and you have the required authority. Set up a business account.
Redbark can only show accounts your bank or connection provider made available and that you selected during connection. Check a missing account.
No. Refresh starts the Redbark syncs that use the connection, but Redbark can only pull data already published by your bank or connection provider.
Not yet. Australian Amex support depends on American Express completing its Consumer Data Right enrolment. Read the availability guide.
No. Redbark and its API are for the account holder’s own financial data. They are not a B2B, embedded, white-label, or hosted-consent service. Read the permitted-use guide.
Yes. Category mappings live on the sync’s Categories tab. Payee and Memo source fields are configured on the YNAB destination. See YNAB category mapping and YNAB Payee and Memo.
Redbark disables a webhook destination after a delivery batch fails. Open the sync’s Deliveries tab to see the response code or network error before re-enabling it. Troubleshoot webhook delivery.
A 401 means the key is missing or invalid. A 403 usually means the plan or key scope does not permit the request. Check API authentication.

​
Still need help?

Open Support in the Redbark app. Include what you expected, what happened, the affected bank or destination, and when you last saw a successful sync. Do not include passwords, access tokens, or full account numbers.