-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: list of minimum feature when setting up Plaid dev account #67
Comments
Hm, I thought I had more time before they did the cutover. The website still shows the "free" plan as an option; did that not work for you? I believe all you should need is the "Transactions" product. This connector does not call the "Recurring Transactions" or "Transactions Refresh" endpoints. Let me know if that works for you. Probably time for me to upgrade to production as well. I'll update the README when someone has confirmed that those selections work. |
Thanks for the quick reply,
I agree on the |
How do you figure? At $.30/account/month, you'd be looking at $1.50/month, which is substantially less than the commercial options I'm aware of. |
I was thinking of a weekly balance pull on top of transaction so around $2 for me to track my saving, when minium of rocket money (also based on plaid) around $4 per month. Feels a little bit overkill working through all trouble setting firefly up just for that end point security or just saving that bit each month(well this thought might be reason why I need a tool to monitor my spending lol) |
Hm, yeah, that's valid. I am definitely disappointed by the paid cutover mandate after putting all the work into this connector, although I can't really blame Plaid for charging for use of their service. Fundamentally I tend to blame this all on the financial institutions for not establishing standard APIs or making them available to their actual customers. I've considered building an integration for SimpleFIN, which appears to be a bit more predictable in pricing (and generally cheaper) but haven't yet seen enough evidence to convince me it's worth it to migrate. I'm definitely open to other suggestions as well. |
I can confirm that I had not read this thread and enabled I also have opened a support ticket with them for what their site means by still having free accounts in prod.. My guess is that this may mean that we get 100 free accounts in prod but that obviously may change at some point in the future. |
So update from Plaid support on how the change over to no dev will work:
So basically don't enable anything in prod June 20th, or at least don't do anything billable in prod until the 20th. Kinda rip for me, I should have just waited to get any of this setup until then but whatever, as mentioned it'll be like $1-3 which is not the worst i guess. Their message didn't give a number to how many "limited number of free API requests" would be, so idk if the setting up of |
I believe the |
Thanks, that's super useful information. I'll add that to the readme shortly. |
@Kvan7 I've finished my own migration to the production environment, which was driven by most of my institutions (US oauth) no longer working in dev. There's a decent chance you'd have had the same problem in "limited Production," so I wouldn't sweat moving over early. |
Closing this as I've migrated to production successfully and updated the readme accordingly. Feel free to reach out with any additional questions. |
Opening plaid account now require to chose features under
Pick your Plaid products
, and without fully understanding the code I found it hard to move forward (maybe just select as much as possible since it charge by trigger anyway?)Above seems the widest combination for
Pay-as-you-go plan
. Would be greate to have a "minimum requirement" list of things for tis connector to function.The text was updated successfully, but these errors were encountered: