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

[Kalpesh Patel]

Quicken did change the authentication method to be secure web based - very
similar to the way Google implements for theirs; OAuth.

But that shouldn't matter for the perspective of supporting other software
if Boing CU chose to do so, but there isn't anything out there that is as
big as Quicken so they drive the norms to keep them business while others
folds.

Prime example is QFX. They took OFX standard, added their customization on
top and called it their own proprietary format. 

The 503 error is being done  -- at a much lower level -- even before their
backend system can decipher what the request is all about.

Ultimately, you will have to create a work around to that channel of imports
as it is likely not going to be available, likely ever. If you have OFX
download from their portal than that will be the next best option.

-----Original Message-----
From: John Vermeer <johnve at juno.com> 
Sent: Monday, May 04, 2026 10:44 AM
To: kalpesh.patel at usa.net
Cc: gnucash-user at gnucash.org
Subject: RE: [GNC] BECU Direct Connect / OFX permanently returning HTTP 503
- H as BECU mo ved to OAuth exclusively?


Kalpesh,

Thanks for the feedback. This is sort of what I expected. Although other
sources claim that Quicken switched to a "more secure" protocol.

John
---------- Original Message ----------
From: "Kalpesh Patel" <kalpesh.patel at usa.net>
To: "'John Vermeer'" <johnve at juno.com>, <gnucash-user at gnucash.org>
Subject: RE: [GNC] BECU Direct Connect / OFX permanently returning HTTP 503
-	Has BECU mo	ved to OAuth exclusively?
Date: Thu, 30 Apr 2026 15:38:15 -0400

That 503 error most likely means that Quicken paid them enough to succumb to
exclusivity ... for techies it means the WAF is blocking the request if it
doesn't originate from a whitelisted IP address(es). 

Only Boeing Employees Credit Union can tell you for sure by calling them up
but the support folks aren't likely to have the full picture of things and
will most likely read a pre-canned reply to get you off the phone as quickly
as possible. 


-----Original Message-----
From: John Vermeer <johnve at juno.com>
Sent: Wednesday, April 29, 2026 10:02 AM
To: gnucash-user at gnucash.org
Subject: [GNC] BECU Direct Connect / OFX permanently returning HTTP 503 -
Has BECU mo ved to OAuth exclusively?

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