[GNC] AQBanking OFX DirectConnect

David Carlson david.carlson.417 at gmail.com
Sun Mar 15 18:30:16 EDT 2020


OFX direct connect is not the same as plain OFX, which is easier to use.  I
didn't have a good experience when I tried OFX D C with my banks long ago.

On Sun, Mar 15, 2020, 5:18 PM chris graves <mohavebaked at gmail.com> wrote:

> Not that it matters, but I concur with John.  I also have been using AQB
> OFX successfully for ~8 years, thanks to you devs!
>
> I continue successfully to use the AQB provided with GnuCash 3.7.
>
> Thanks for your support!
> Chris
>
> > On Mar 15, 2020, at 1:21 PM, John Ralls <jralls at ceridwen.us> wrote:
> >
> >
> >> On Mar 15, 2020, at 12:47 PM, Martin Preuss <martin at aqbanking.de>
> wrote:
> >>
> >> Hi,
> >>
> >> Am 15.03.20 um 20:17 schrieb John Ralls:
> >>> I just made a MacOS build with the latest AQBanking so I could test it
> with my bank (USAA). No go, and a bit of troubleshooting reveals that it's
> because AQBanking now uses the XML-based OFX V2. AFAIK that's not supported
> by any US bank.
> >> [...]
> >>
> >> OFX2 is the only version I could get access to a test server for, so
> >> thats what I implemented so far.
> >>
> >> However, since the OFX spec state that banks should also accept XML like
> >> OFX requests (i.e. OFX files with closing XML elements) the code might
> >> be adjustable for this...
> >>
> >> I will try to add a mode in which the plugin sends the headers
> >> previously used for OFX1 and still send requests with closing XML
> >> elements, at least according to the specs I read that should work...
> >>
> >> Anyway, as I wrote before I can't test it myself. There is only person -
> >> so far - I heard of from the US who tested the latest code with a real
> >> server and I really appreciate his help, but he seems to be using the
> >> prebuilt Windows version which makes the debug process... well...
> difficult.
> >>
> >> It would be extremely helpfull to have someone who could compile and
> >> test a version from GIT, but given the different timezones the possible
> >> OFX users and I live in that might be time consuming for both sides...
> >
> > Martin,
> >
> > As I said here and in my bug report, AQB 5's OFX backend works well and
> has done for many years. If you just update it for the new AQB6 and Gwen5
> API it has a good chance of working.
> >
> > I can build from git and test. So far there's no need for debugging,
> simply comparing the OFX from 5.8 and 6.1 showed me the problem: OFX
> DirectConnect servers using V1 can't parse the XML you send in the request
> and 400, see the transcripts in the bug report.
> >
> > The current OFX spec doesn't matter if the bank is using software
> written for OFX V1 as nearly all in the US do.
> >
> > Regards,
> > John Ralls
> >
> >
> > _______________________________________________
> > gnucash-user mailing list
> > gnucash-user at gnucash.org
> > To update your subscription preferences or to unsubscribe:
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> > -----
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
>
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>


More information about the gnucash-user mailing list