Wise AU connection shows “Unauthorized” immediately on initial Wise page load (Manager Cloud, Aussie Bank Feeds)

  • Edition/version: Manager Cloud (latest as of July 23, 2026)
  • Business: [your-cloud-subdomain].manager.io (redact if needed)
  • OS/browser: Windows 10/11; tested Chrome and Edge (both InPrivate), also tried Comet earlier
  • Bank: Wise Australia Pty Ltd (AU)
  • Flow: Bank & Cash Accounts → Aussie Bank Feeds → Connections → Add connection → select Wise (Australia)
  • Timestamp(s): [YYYY-MM-DD HH:MM local time, include timezone]
  • What happens:
    • The Wise authorization page loads and immediately displays “Unauthorized” before any email/password fields appear.
    • This occurs on first paint, not after any interaction.
    • Reproduces consistently across Chrome/Edge InPrivate with all extensions disabled and third‑party cookies allowed.
  • Technical observations:
    • Console only shows routine Next.js build warnings; no client-side JS error.
    • Network panel shows no failing API calls related to auth; the “Unauthorized” appears as part of the initial HTML response from Wise.
    • Behavior suggests a server-side rejection at Wise during the initial authorize flow (likely the request arriving from the data recipient).
  • Hypothesis:
    • The authorization request from the bank-feed provider (Aussie Bank Feeds/Basiq) to Wise AU is being rejected upstream (e.g., client_id/registration/accreditation for the requested scope is missing, expired, or misconfigured). Since the error occurs before login, it’s not credential-related.
  • What I’ve already tried:
    • Started the connection only from inside Manager Cloud (no reused tabs).
    • Cleared site data for wise.com, aussiebankfeeds.com, and basiq.manager.io.
    • Tested Chrome and Edge in InPrivate with all extensions off; same result.
  • Request:
    • Could Manager/Aussie Bank Feeds/Basiq please verify the Wise AU client registration/accreditation and configuration for this connection?
    • If helpful, I can supply exact request timestamps and redacted URLs shown at the time of failure.

Workaround in the meantime:

  • I’m importing statements from Wise (OFX/QIF/QBO/CSV) via Bank & Cash Accounts → Import bank statement and using Bank Rules.

Thanks! Let me know what additional diagnostics would help.

Anyone with any suggestions?