[GNC] BECU Direct Connect / OFX permanently returning HTTP 503 - Has BECU mo ved to OAuth exclusively?

[John Vermeer]

Hello everyone,

I am trying to determine if Boeing Employees Credit Union (BECU) has permanently shut down its OFX Direct Connect gateway for open-source tools.

The connection via AqBanking has been failing since late February 2026. On April 23, the Quicken community officially marked the BECU connection issue as "Resolved." However, GnuCash is still unable to connect.

Here are the specific technical details and troubleshooting steps I have taken:

The Error: I am consistently getting an "HTTP-Status: 503 (Service Unavailable)" error during the AqBanking sync.

The Endpoint: I am using the standard modern endpoint: https://onlinebanking.becu.org/ofx/ofxprocessor.asp

Browser Verification: To rule out GnuCash/AqBanking configuration issues, I navigated to that .asp URL directly in Microsoft Edge. It immediately returns a 503 Service Unavailable error, which suggests their Web Application Firewall (WAF) is intentionally blocking standard web requests to that gateway.

AqBanking Reset: I have completely deleted the user profile, generated a fresh UUID for the ClientUID (stripping the hyphens), and rebuilt the connection using FID 325081403, APPID QWIN, APPVER 3100, and Header 103. The 503 error persists.

Context that points to an API shift:
While OFX is completely dead for me, I noticed that BECU's connection to my Fidelity account (which uses Akoya/OAuth APIs) just started working again a few days ago. This strongly implies that Quicken�s "fix" was actually a migration to Express Web Connect+ (OAuth), and that BECU has intentionally left the legacy OFX gateway offline.

Has anyone in the community successfully connected GnuCash to BECU since the April 23rd Quicken fix? If not, is it safe to assume we are permanently locked out of direct OFX syncing for this institution?

Any insight would be greatly appreciated.

John Vermeer, USA