-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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
refactor: plaid connection #42962
base: develop
Are you sure you want to change the base?
refactor: plaid connection #42962
Conversation
This pull request has been automatically marked as inactive because it has not had recent activity. It will be closed within 3 days if no further activity occurs, but it only takes a comment to keep a contribution alive :) Also, even if it is closed, you can always reopen the PR when you're ready. Thank you for contributing. |
Can I get a review please? |
@ankush, @deepeshgarg007, @casesolved-co-uk, any comments to help this move forward? |
|
Thanks for the review @casesolved-co-uk. Re:
I think you might be misunderstanding Plaid's new fee structure. At least here in the US, they're charging $0.3/account/mo for production access to Transaction Sync.
Plaid doesn't always return a bank account from |
I guess their UK offering is different to the US then. |
This makes the plaid bank connector much more performant and less error-prone.
plaid_access_token
is updated in the database directly viafrappe.db.set_value
instead of attempting to loading and save the Bank doc.add_institution
is expanded to include all updates to theplaid_access_token
, to catch any errors related to the givenbank_name
add_institution
is refactored to return just thebank_name
instead of the bank doc, since only thebank_name
is used in the subsequentadd_bank_accounts
function.bank_name
is not returned in the Plaid response.