I read that disclaimer. It says to keep the token secure and yes, the bearer of that token gets access. As they said: "The access token generated by using this tool is sensitive material as it grants access to your accounts. It should be handled with care and protected from unauthorized access. You must be sure to store it in such a way that makes it impossible for others to gain access. The creators and maintainers of Plaid2QIF are in no way responsible if you mishandle your access token."
GIving Plaid2QIF this token is no different than me giving a username and password to AQBanking, except that Plaid has a chance of working. I don't like having an intermediary, in this case Plaid and Plaid2QIF, but OFX is unusable, and at the moment, AQBanking isn't even showing the list of banks anymore. Does anyone know of a US bank or credit union that uses a modern REST based API that they actually share with developers? Regards, Ben On 2/22/23 23:08, john wrote: On Feb 22, 2023, at 2:01 PM, Ben Pracht <ben.pracht.n...@gmail.com> <ben.pracht.n...@gmail.com> wrote: I'd like to use Plaid with GnuCash. There is a plaid2qif project that claims to have been extensively tested with GnuCash and Plaid. However, when I created the Plaid account, it asks for either a limited developer account or a production account with a compliance audit. What account type should I use? Anything else helpful to know? Neither. See https://github.com/ebridges/plaid2qif/blob/master/gen-access-token/README.md , Pay particular attention to the disclaimer at the bottom of that page. Regards, John Ralls _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
